- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2014 12:11 PM
We are part way through an upgrade form Berlin to Dublin. We have set up a MID server to allow us to test every part of the system, prior to upgrading production. From the ServiceNow Test instance the MID server shows as being UP, but none of the scheduled import jobs we run via the MID server work. On the import log I see a Message that reads "MID server not found: e204bdb0c42c4100c5de2507254e976e ( scheduled import job: Import job name printed here)". What am I missing with this MID server thing? I thought it was basically a conduit to get data from other places. Are there other settings I need to consider beyond connecting to the MID server?
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2014 12:59 PM
Try removing the MID server from the data source, saving, and then adding it back. I suspect that sys_id will match the PROD MID server, not the TEST one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2014 03:13 PM
To Jacob's point, you can exclude the data sources table from the cloning process, which pre-empts the need to fix it after every cloning process. The MID server table is already included OOB.
