I got an error msg when I deploy an update set from "PLAY" instance to "DEV" instance. error msg : "Could not find a record in ecc_agent referenced in this update" This update set has a "mid-server". I am import data from external db table into SN ta

[dilini]

This update set used a "mid-server". I am importing data from an external db table into SN table using JDBC type. The Play and Dev instance have different mid servers. I am planing to point/change Dev instance's mid server after the update set is deployed into Dev. Anybody thinks this mid server mismatch cause the "ecc_agen" error or something else cause the error.

error:

Missing Item Table - ecc agent

Description - Could not find a record in ecc_agent referenced in this update

[Slava Savitsky]

I think you can ignore the error, accept the remote update and update the reference to the MID server manually afterwards.

[valeriemorris]

Thanks, Slava! I also got this error and your suggestion worked fine.

[doormat18]

Slava, your suggestion makes sense. Though, I wonder if there is better way to do this? If you define data sources with references to environment-specific MID servers, how do you best capture and migrate that?

Tangentially, is it advisable to have a separate MID server for each environment?

[Slava Savitsky]

I am afraid I am not aware of a better alternative.

As for your other question, you have to have a separate MID server installation for each instance. However, you can install multiple MID servers (even servicing different ServiceNow instances) on the same host, which can be a physical or a virtual machine. Nevertheless, I would recommend hosting your PROD MID server separately from the ones for non-PROD instances for performance reasons.