Service Graph Connector for Microsoft SCCM - JDBC TCP Connection issuesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Service Graph Connector for Microsoft SCCM encounters the following JDBC error during testing: "The TCP/IP connection to the host abc123.xxx.net, port 1433 has failed. Error: "null." Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall." Additionally, the logs show that a different MID Server was used, and it wasn't initially chosen during setup. MID Server reported error: SQLState: nulljava.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'PNCQA\WITM217A$'. ClientConnectionId:07dd5bde-05ca-447b-bcd5-4774fff13863com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:283)com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:129)com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37)com.microsoft.sqlserver.jdbc.SQLServerConnection$1LogonProcessor.complete(SQLServerConnection.java:4786)com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5068)com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3731)com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:94)com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3675)com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7194)com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2979) Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All the supported versions of Service Graph Connector for Microsoft SCCM Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The reported issue can occur if the MID server used by the connection is invalid or nonoperational, or if the MID server referenced by the data source does not exist in the instance, which could have been removed after an instance clone or due to reconfiguration of the MID server. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Ensure to have a valid and active MID server is set up and running in the instance without any issues and has access to the SCCM database as referred in the documentation below Configure Service Graph Connector for Microsoft SCCM using SGC Central 2. Update the impacted SCCM data source with the active MID server 3. Verify if the MID server field in the table below for the Service Graph Connector for Microsoft SCCM record is updated with an active MID server, ensuring it isn't replaced or reset after the scheduled import. https://<instance>.service-now.com/sn_sccm_integrate_instance_list.do Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } ☞ Additional Information: If you would like to understand how the MID server value is set and how SQL statements are updated, review the scripts in the links below used in the scheduled import. updateDatasource: function(grDatasource, connectionAliasSysId, instancePrefix)getExecutionTimeSqlStatement_setConnectionDetails: function(grDatasource, connectionAliasSysId, midServer)getSQLStatement: function(connectionAliasSysId) https://<instance>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=174a7a0153f0301095e2ddeeff7b12aehttps://<instance>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=1a0ce7d973d11010e279b41afaf6a7cf