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
01-09-2025 05:55 PM
I just used a different mid-server, and it started working. So it's confirmed that the JDBC connection is not an issue. It's a mid-server issue. In my previous midserver, the below issues were there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2025 08:31 AM
On my end, after importing my Data source from Dev to Prod. I was receiving the same error....
I had to re-put the password of the account back when in the Prod instance and it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2025 12:21 PM
We had this issue and it turns out that when we copied the Data Source, it didn't include the Connection URL. It's not on the form, but can be added to the list view and edited from there. Adding the value to our new Data Source resolved this issue for us.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2025 04:12 AM - edited 03-05-2025 04:13 AM
We had this issue because our SQL query was exceeding the maximum payload size.
Look into the error logs and you will see what your issue is (go to All > System Logs > System Log > Errors)
Payload size of 21045428 bytes exceeded maximum of 20000000 bytes.
Contents of the original payload were moved to D:MIDServer-XXXXXXServiceNow MID Server XXXXXXXagentworkmonitorsECCSenderoutput_oversizeecc_queue.XXXXXXXXX.xml on the MID server.
Maximum payload size can be set with mid config parameter: mid.eccq.max_payload_size
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 02:08 PM
I had this issue when importing my data source from XML. I re-typed the credentials for the data source and then it started working again.