- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2024 07:48 AM
When we upgraded to Washington DC, the import of SCCM data stopped working. We are still using the legacy plugin. We are receiving the following error:
Cannot invoke "java.util.Map.keySet()" because "this.fImportSourceFields" is null
From what I've read, this message is returned for any SQL error encountered. I did a test load of 20 records on one of the data sources and saw the following in the import log:
I have asked the database and network folks to verify that everything is set up correctly and that the mid server can connect to the SCCM database using the SQL credentials that are defined in ServiceNow. I am told that is all configured correctly and that the credentials are valid.
We are using SQL authentication to connect to the SCCM database. Our mid server is in the DMZ. It can’t use integrated authentication to connect to our internal databases because our DMZ server isn’t connected to active directory in order to leverage windows authentication.
Is SQL authentication still a valid option here? I haven't run across anything in the documentation that indicates it is not.
At one point, I installed the ServiceGraph Connector for SCCM in our development instance, set up a data source and did a test load of 20 records. I received the same error that we are receiving in our production instance with the legacy plugin. We have since cloned production to development so I need to install the replacement plugin in development again.
Any suggestions on how to troubleshoot this would be greatly appreciated. We would like to get this working in production again before we upgrade to the replacement plugin.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 03:15 AM
This has been resolved. Apparently, after upgrading to Washington DC the encryption keys for the MID server were not matching. Everything started working again once they were rekeyed.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 03:15 AM
This has been resolved. Apparently, after upgrading to Washington DC the encryption keys for the MID server were not matching. Everything started working again once they were rekeyed.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2024 03:31 AM
@mah1 (they means who? ) -- Servicenow team or Mid server team has to rekeyed? Whats the input we have to share with respective team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2024 03:45 AM
The encryption keys were rekeyed by someone on our internal ServiceNow team by navigating to MID --> Servers then opening the server record and clicking the Rekey option under Related Links.