Notifications

15 views

Description

Testing SCCM connectivity using a fresh London MID server installation will throw an exception: 

MID Server reported error: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:f5905e6e-13c1-48da-85ef-fe1bd7e0a57d 
com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667) 
com.microsoft.sqlserver.jdbc.AuthenticationJNI.(AuthenticationJNI.java:60) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:2229) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41) 
com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:2220) 
com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1326) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991) 
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827) 
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012) 
java.sql.DriverManager.getConnection(Unknown Source) 
java.sql.DriverManager.getConnection(Unknown Source) 
com.service_now.mid.connections.jdbc.JDBCConnection.establishConnection(JDBCConnection.java:102) 
com.service_now.mid.connections.jdbc.JDBCConnection.connect(JDBCConnection.java:74) 
com.service_now.mid.connections.jdbc.JDBCConnectionFactory.create(JDBCConnectionFactory.java:65) 
com.service_now.mid.connections.ConnectionCachePool.getAvailableConnection(ConnectionCachePool.java:82) 
com.service_now.mid.connections.ConnectionCache.get(ConnectionCache.java:94) 
com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:768) 
com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:116) 
com.service_now.mid.probe.AProbe.process(AProbe.java:96) 
com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:125) 
com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) 
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 
java.lang.Thread.run(Unknown Source) 

In London, the MID server does not come with a bundled JRE, the "wrapper-jvm.conf" file is not part of the mid-installation package. Missing this file and its content is causing the SCCM Integration to fail.

Steps to Reproduce

Not applicable

Workaround

This issue has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

If you are still affected by this issue, these steps might provide relief:

  1. Create a file with name "wrapper-jvm.conf" under <MID INSTALLATION DIRECTORY>/conf
  2. Based on the OS type, update the file with one of these lines:
    • set.SNC_JVM_ARCH=x86-64
    • or
    • set.SNC_JVM_ARCH=x86-32

Related Problem: PRB1315736

Seen In

There is no data to report.

Fixed In

London Patch 5

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-07-10 05:59:18
Published:2019-07-10