MID Script Include 'xxx' does not exist. Marking it to prevent future queriesIssue MID Server code may fail with a "MID Script Include 'XXXX' does not exist. Marking it to prevent future queries." error, seen in the log, ecc_queue result or MID Server Agent log. Example 1: Running a custom JavascriptProbe 2020-03-22 20:58:52 (541) Worker-Standard:JavascriptProbe-d3fc349cdbffc85044abb1b23996190f Worker starting: JavascriptProbe2020-03-22 20:58:53 (229) Worker-Standard:JavascriptProbe-d3fc349cdbffc85044abb1b23996190f WARNING *** WARNING *** MID Script Include 'Class' does not exist. Marking it to prevent future queries.2020-03-22 20:58:53 (229) Worker-Standard:JavascriptProbe-d3fc349cdbffc85044abb1b23996190f WARNING *** WARNING *** org.mozilla.javascript.EcmaError: "Class" is not defined.Caused by error in MID Server script include 'FileExport' at line 1==> 1: var FileExport = Class.create();2: FileExport.prototype = {3: initialize : function() {4: ms.log("===>>> FileExport ==>>> "); The same seen in the ECC Queue input Payload, but without the missing Class shown as the cause: <results error="Caused by error in JavaScript probe 'FileExport' at line 1 ==> 1: var req = new FileExport(); req.fileMoveTOTarget() " probe_time="736" result_code="900000"><result error="Caused by error in JavaScript probe 'FileExport' at line 1 ==> 1: var req = new FileExport(); req.fileMoveTOTarget() "><output>Evaluation error: Caused by error in JavaScript probe 'FileExport' at line 1 ==> 1: var req = new FileExport(); req.fileMoveTOTarget()</output></result> Example 2: Starting an Event Management Collector Worker-Interactive:ConnectorProbe-72746fd1dbd388909c13f3de3b96199e Worker starting: ConnectorProbe source: Solarwinds Connector Instance Worker-Interactive:ConnectorProbe-72746fd1dbd388909c13f3de3b96199e Credentials from instance loaded Worker-Interactive:ConnectorProbe-72746fd1dbd388909c13f3de3b96199e WARNING *** WARNING *** MID Script Include 'Class' does not exist. Marking it to prevent future queries. Worker-Interactive:ConnectorProbe-72746fd1dbd388909c13f3de3b96199e WARNING *** WARNING *** org.mozilla.javascript.EcmaError: "Class" is not defined.ReleaseAny. Most likely to be seen on a sub-production instance that has recently been the target of a Clone.CauseThis is usually caused by some unwise Clone Exclude and Preserver settings. MID Servers are generally instance specific, and some tables and records do need excluding/preserving in clones, but these settings should never include tables that contain out-of-the box code, such as the MID Server Script Includes, Script Files and JAR files.ResolutionCheck the production instance, which is usually the source for clones, and so will not have been affected.Find the MID Server Script Include mentioned in the error. In the above examples, that is "Class":https://<instance_name>.service-now.com/ecc_agent_script_include.do?sys_id=bb6e3cd3c0a8020100823824cbacec99 Export that file as XML, and import it into the instance that is missing it.To avoid breaking instances after future clones, please remove any custom setting specific to MID Servers that include code.