Active MID Server post-cloning credential issues

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Active MID Server Post-Cloning Credential Issues

    This content outlines the processes and implications of credential issues for MID Servers following an instance cloning in ServiceNow. It highlights the automatic detection of potential credential problems and the actions taken by the system to notify users of these issues.

    Show full answer Show less

    Key Features

    • The system automatically detects and notifies users of MID Server credential issues post-cloning.
    • The eccagentissue table tracks active MID Server issues, showing their current states and evaluation times.
    • A cleanup script runs after cloning to identify any MID Servers that might be down due to credential issues.
    • A business rule monitors the transition of MID Servers from Down to Up and updates the issue status accordingly.

    Key Outcomes

    After cloning, if a MID Server is down due to bad credentials, users will receive notifications and can find issue details in the eccagentissue table. It is important to verify and correct the credentials associated with the affected MID Server user. If the issue persists after confirming credentials, further troubleshooting may be necessary by consulting the Knowledge Base.

    The system provides automatic processes to detect and notify you of possible MID Server credential issues after instance cloning.

    During an instance clone, the MID Server [ecc_agent] table is not copied from the source instance, but the User [sys_user] table is copied. As a result, the source MID Server user credentials copied into the target instance might not match those used by the existing set of MID Servers used by the target. Bad credentials can cause those MID Servers to be down for the target instance. Processes on the instance notify you if a MID Server is down from suspected bad credentials following an instance clone.

    Table for post-cloning credential issues

    The MID Server Issue [ecc_agent_issue] table stores active MID Server issues after an instance clone. Records in this table show a MID Server's current state, evaluation times, and the Issue source. For cases in which a MID Server for a cloned instance is down because of possible bad credentials, the Issue source is InstanceClone. Data from the MID Server Issue [ecc_agent_issue] table are displayed in a related list on a MID Server record. Records in this table are removed if they have not been detected for 30 days. Ongoing issues reappear as they occur.

    Post-cloning cleanup script and scheduled jobs

    A cleanup script called Bad MID Server credentials after clone runs on the target instance after cloning and calls a script include called BadMIDCredentialAfterClone. This script include schedules the execution of the following jobs on the Schedule Item [sys_trigger] table:
    • BadMIDCredentialAfterClone-1: Runs 15 minutes after clone execution.
    • BadMIDCredentialAfterClone-2: Runs 75 minutes after clone execution.
    These jobs log to the MID Server Issue [ecc_agent_issue] table any MID Servers that existed on the target instance prior to the clone that are in the Down state. These MID Servers are not ready for normal processing and might be down due to invalid credentials resulting from the cloning process. The state of MID Servers added to the target instance after the clone is not evaluated.
    Note:
    The MID Server log shows that the MID Server user associated with the target instance could not be authenticated or was missing the proper role.

    Business rule that checks for bad credentials

    The Check for bad MID credential after clone business rule monitors the MID Server [ecc_agent] table for MID Servers that are transitioning from Down to Up. If the business rule finds a MID Server making that transition, the rule attempts to find a matching MID Server in the MID Server Issue [ecc_agent_issue] table that has an issue source of InstanceClone and a state other than Resolved. If a match is found, the business rule updates the state of the MID Server in the [ecc_agent_issue] table to Resolved.

    Resolving MID Server issues

    The error message in the MID Server Issue [ecc_agent_issue] table names the affected MID Server user. This message appears each time the business rule runs and finds a MID Server that is down from suspected bad credentials:MID Server not operational (status: Down), possibly due to recent clone. Verify credentials for logged in User 'local-midserver'.

    Attempt to resolve the issue first by comparing the user's credentials with the credentials that the affected MID Server is expecting. If the credentials are incorrect, fix the problem and check the MID Server status again. If the credentials are correct, but the MID Server remains down, check the Knowledge Base for other possible causes.