- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2018 07:15 PM
Hi all,
We are attempting to configure the Integration - SCCM 2012 v2 application.
We're hitting a wall early on. When using the 'Test data source connections error' on the Setup form the below error is thrown during the Testing JDBCProbes stage (also attached a pic):
Data source: SCCM 2012 v2 Computer Identity
Error: java.lang.NullPointerException
at com.service_now.mid.queue_worker.JDBCWorker.hidePassword(JDBCWorker.java:78)
at com.service_now.mid.probe.JDBCProbe.setConnectionStringFromDataSource(JDBCProbe.java:714)
at com.service_now.mid.probe.JDBCProbe.initTry(JDBCProbe.java:599)
at com.service_now.mid.probe.AbstractImportExportProbe.init(AbstractImportExportProbe.java:39)
at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:105)
at com.service_now.mid.probe.AProbe.process(AProbe.java:84)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:125)
at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748):
It throws nine of these errors, one for each of the data sources.
We haven't made any changes to the data sources, just provided the required setup info where necessary (database name, database server etc).
Can anyone shed some light on where we are going wrong?
Cheers,
Ryan
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2018 10:52 PM
Check if there is an ACL that is restricting the user with mid_server role to access fields from data source, this is usually the root cause of this issue.
https://<instance>.service-now.com/nav_to.do?uri=%2Fsys_security_acl_list.do%3Fsysparm_query%3DnameLIKEsys_data%255Ename%253Dsys_data_source.*%26sysparm_first_row%3D1%26sysparm_view%3D

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2018 07:45 PM
can you share screenshot of configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2018 09:19 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2018 07:48 AM
Check if you have access to SQL server from Mid server. Make sure port for SQL server is open.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2018 10:52 PM
Check if there is an ACL that is restricting the user with mid_server role to access fields from data source, this is usually the root cause of this issue.
https://<instance>.service-now.com/nav_to.do?uri=%2Fsys_security_acl_list.do%3Fsysparm_query%3DnameLIKEsys_data%255Ename%253Dsys_data_source.*%26sysparm_first_row%3D1%26sysparm_view%3D