Mid server having special characters in name will cause issues ensure proper formatting for the MID ServerIssue The mid server having special characters in name or folder structure will cause issues to ensure proper formatting for the MID Server nameCauseThis is caused because the mid server name or directory/folder has special characters. 01/19/21 14:39:49 (259) StartupSequencer SEVERE *** ERROR *** 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.VM Production 1 ñ pdydalmidp201</agent><purpose xsi:type="xsd:string">UpdateQueueFromProcessingToReady</purpose></m:execute></SOAP-ENV:Body></SOAP-ENV:Envelope>01/19/21 14:39:49 (259) StartupSequencer SEVERE *** ERROR *** 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>01/19/21 14:39:49 (259) StartupSequencer WARNING *** WARNING *** UpdateQueueFromProcessingToReady: request failed - null waiting 10 seconds to retryResolutionMID Server name or the directory/folder name having special characters will cause issues with the mid server.It is always recommended to follow the standard naming convention while designing the folder structure and mid server name. Make sure you do not have any special characters in the mid server folder structure or mid server name