A MID Server with an ampersand character "&" in the Name will go Down after failing GetMIDInfo.do requests for ECCSenderCacheDescriptionA MID Server with an ampersand character "&" in the Name will go Down after failing GetMIDInfo.do requests for ECCSenderCacheSteps to Reproduce Add an ampersand character to a MID Server name, either in config.xml before first startup, or by adding an & to the value in the name parameter of an existing MID Server.Start/Restart the MID Server.It will stay up for a while and work up to a point where the following error will be seen:2026-04-10T11:57:40.196+0200 ERROR (StartupSequencer) [InstanceSOAPClient:168] SOAP Request: <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.service-now.com/GetMIDInfo" xmlns:m="http://www.service-now.com" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><m:execute><agent xsi:type="xsd:string">mid.server.R&D MID Server</agent><field xsi:type="xsd:string"></field><purpose xsi:type="xsd:string">GetAgentAggregate</purpose><query xsi:type="xsd:string">queue=output^state=processing^sys_created_on>=2026-04-10 07:40:04</query><table xsi:type="xsd:string">ecc_queue</table><aggregate xsi:type="xsd:string">COUNT</aggregate></m:execute></SOAP-ENV:Body></SOAP-ENV:Envelope>2026-04-10T11:57:40.197+0200 ERROR (StartupSequencer) [InstanceSOAPClient:168] SOAP Response: Status code=500, Response body=<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Unable to parse SOAP document</faultstring><detail>Error completing SOAP request</detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>2026-04-10T11:57:40.198+0200 WARN (StartupSequencer) [MIDServerInfoRemote:182] GetAgentAggregate: request failed, waiting 10 seconds to retry (clientError=null)followed later by2026-04-10T12:02:53.649+0200 ERROR (StartupSequencer) [StartupSequencer:191] StartupSequencer threw exception, unable to perform proper startup, shutting downcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) [Guice/ErrorInCustomProvider]: RuntimeException: Failure creating instance of ECCSenderCache, unable to continue...2026-04-10T12:02:54.668+0200 INFO (Wrapper-Stopper) [Main:389] Stopping MID serverWorkaroundThis problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available. The workaround is to remove the ampersand from the name: On the MID Server Host Stop the MID ServerEdit the config.xml file to remove the & from the name parameter In the instance Edit the ecc_agent record Name fieldEdit the Name configuration parameter Start the MID Server againRelated Problem: PRB2011944