I can see our MID Server, but can't perform any of the tasks we need it to

[ewilks]

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?

[prdelong · Accepted solution]

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.

[ewilks]

Thank you.

[Jacob_Andersen]

In ServiceNow, whever you see a reference field and hover over the reference icon, if the result is 'Record not found', then that means that the record has a sys_id for a related record that does not exist in your system.   If you click on that icon, you'll also be taken to a record not found page.

To remedy this, you need to fix the reference value to point to a valid record.   In this case, your new mid server.

As a side note, I'm guessing this occurred as part of your cloning process.   Keep this in mind as you may want to setup a data preserver or a after clone script to make sure that this doesn't happen again in the future.

[ewilks]

Thanks.   Yes it did occur as part of a cloning process.   I don't need the data as much as wanting to make sure all of it worked.