- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2023 10:28 PM
Hii Everyone,
1.Trying to Integrate ServiceNow with SCCM SQL Database using Service graph connector for SCCM Plugin.
2.I have Installed Mid Server in SCCM Host Machine and Validate the Mid server in serviceNow Successfully.
3.Configure Connection and Credentials successfully.
4. when i try to test load record from data source i am getting this error.
5.Anyone have any suggestion or solution to resolve this.
ERROR Getting:
MID Server reported error: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'D04\TL24RS'. ClientConnectionId:2d67796e-32bb-458c-8d8b-6aefa8af99ef
com.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)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2488)
com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2142)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1993)
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1164)
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:760)
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
java.sql/java.sql.DriverManager.getConnection(DriverManager.java:189)
com.service_now.mid.connections.jdbc.JDBCConnection.establishConnection(JDBCConnection.java:116)
com.service_now.mid.connections.jdbc.JDBCConnection.lambda$connect$0(JDBCConnection.java:86)
com.glide.util.LogContext$Frame.run(LogContext.java:212)
com.service_now.mid.connections.jdbc.JDBCConnection.connect(JDBCConnection.java:84)
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:831)
com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:141)
com.service_now.mid.probe.AProbe.process(AProbe.java:106)
com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:128)
com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:649)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base/java.lang.Thread.run(Thread.java:829)
at com.service_now.mid.probe.JDBCProbe.getJDBCConnection(JDBCProbe.java:835)
at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:141)
at com.service_now.mid.probe.AProbe.process(AProbe.java:106)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:128)
at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
at com.service_now.mid.threadpool.ResourceUserQueue$RunnableProxy.run(ResourceUserQueue.java:649)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2023 03:24 AM
Hi @krishna kumar t ,
There could be several reasons why this login attempt failed:
Incorrect credentials: Ensure that the username and password used to connect to the SQL database are correct. Double-check that you have entered the correct credentials for the user 'D04\TL24RS'.
Permission issues: The user 'D04\TL24RS' may not have the necessary permissions to connect to the SQL database. Check that this user has the appropriate permissions in the SCCM SQL database to connect and retrieve data.
Firewall or network issues: The connection may be blocked by a firewall or other network issue. Make sure that the necessary ports are open and that the network is functioning correctly.
SQL server instance name issue: Ensure that you have correctly specified the SQL server instance name and that it is accessible from the ServiceNow MID Server.
You can try the following steps to troubleshoot this issue:
Check the username and password for correctness and make sure they have the necessary permissions.
Check if the SQL Server is running and the correct instance is specified.
Check if the firewall is blocking the connection.
Try connecting to the SQL database using a different tool or method to validate the credentials and connection.
If my response helps you to resolve the issue close the question by ✅Accepting solution and hit 👍thumb icon. From Correct answers others will get benefited in future.
Thanks,
Ratnakar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2023 07:28 AM
Hi, I believe your mid-server installation looks the hosted machine credentials (try to tag the admin role initially for that account) when you are installing. Is that account configured correctly?
Suresh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2023 03:24 AM
Hi @krishna kumar t ,
There could be several reasons why this login attempt failed:
Incorrect credentials: Ensure that the username and password used to connect to the SQL database are correct. Double-check that you have entered the correct credentials for the user 'D04\TL24RS'.
Permission issues: The user 'D04\TL24RS' may not have the necessary permissions to connect to the SQL database. Check that this user has the appropriate permissions in the SCCM SQL database to connect and retrieve data.
Firewall or network issues: The connection may be blocked by a firewall or other network issue. Make sure that the necessary ports are open and that the network is functioning correctly.
SQL server instance name issue: Ensure that you have correctly specified the SQL server instance name and that it is accessible from the ServiceNow MID Server.
You can try the following steps to troubleshoot this issue:
Check the username and password for correctness and make sure they have the necessary permissions.
Check if the SQL Server is running and the correct instance is specified.
Check if the firewall is blocking the connection.
Try connecting to the SQL database using a different tool or method to validate the credentials and connection.
If my response helps you to resolve the issue close the question by ✅Accepting solution and hit 👍thumb icon. From Correct answers others will get benefited in future.
Thanks,
Ratnakar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-26-2023 09:22 PM
Thank you Ratnakar
My issue is Resolved.The username and password are correct only but this issue is due to not providing proper access to that user for connecting to other server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-16-2023 09:01 AM
Hi @krishna kumar t
Did you use Cyberark integration to rotate the credentials / are you using credential rotation for sccm user ?
Regards,
Pranav Patil