Error 'Cannot invoke "java.util.Map.keySet()" because "this.fImportSourceFields" is null' in SN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 05:18 AM
Hi All,
i am getting the 'Cannot invoke "java.util.Map.keySet()" because "this.fImportSourceFields" is null' error in the data source.
Could you please help me with this? I am not sure if it is something related to SN or not and what I need to do here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2024 10:49 PM
Was seeing the same issue as OP, and while OPs might be something else, in our case, it was a permission issue.
1. Getting a domain account to connect to the SCCM database through the Graph connector is a no go. Nothing I have learned in my 20 years a sys.admin helped. Everything works when connecting through SSMS or ODBC connections in Windows. Just not through the Graph connector.
2. Changing the MID Server Service account to run as a domain user and then using Integrated Authentication do work.
3. I ended up creating a local account on the SQL server itself. Since it's very much read only, it can be shared between the different ServiceNow instances (incl. my PDI)
BR, Steffen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2024 09:08 AM
Hello,
I was having also the error "Cannot invoke "java.util.Map.keySet()" because "this.fImportSourceFields" is null"
After looking at other community messages, I tried revalidate the mid, rekey etc but it was not working.
Finally, after looking at the MID server logs, I could see an SQL error due to a table used in the SQL query not available for my SCCM user. Usually, these errors are visible in the ServiceNow console and in the progress worker but here strangely, it was not visible.
Fixing the SQL query fixed the issue for me.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2024 03:47 AM
We had the same error, turns out to be missing rule in the firewall from the MID server to the database.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2024 07:35 AM
Hi Guys
I managed to resolve it by updatind my script with the DBA team, and the pemissions of the account used for connection were also redone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2024 07:53 AM
can you please tell me, how you resolved this issue in detail?