MID Server Installer (ZIP) log shows "access restricted" for instance details values, and fails to authenticate the user


When attempting to set up a new MID Server using install.bat, the user may fail to authenticate.

mid_installer_log.txt will show something like the following:

Setting basic authentication with user mid_server_user
DEBUG: HTTPClient.registerOtherProtocols() starting on Thread Thread[Thread-28,6,main].
Successfully connected to instance:
  Install name: access restricted << Instance details should be shown here.
 Instance name: access restricted
          Node: access restricted
    Build date: access restricted
     Build tag: access restricted
   Instance ID: access restricted
     System ID: access restricted
   Instance IP: access restricted
   MID buildstamp: orlando-12-11-2019__patch7-08-19-2020_08-28-2020_1009
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><roles xsi:type="xsd:string">mid_server,soap,soap_script,soap_query,soap_create,soap_delete,soap_ecc,soap_script,soap_update</roles></m:execute></SOAP-ENV:Body></SOAP-ENV:Envelope>
SEVERE *** ERROR *** SOAP Response: Status code=401, Response body=<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>User Not Authenticated</faultcode><faultstring>User Not Authenticated</faultstring><detail>Erreur d&#39;ex�cution d&#39;une demande SOAP</detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
WARNING *** WARNING *** Could not authenticate user 'mid_server_user' on the ServiceNow instance

The access restricted for the various instance attribute values is the clue.


The user "soap.guest" may be inactive or locked out. It is important that this user is active, and has Web services access only ticked.

This is the user specified in the com.glide.soap.guest_user Web Services system property for "If unauthenticated, SOAP requests will execute on behalf of this user ID. Set roles for this user and use ACL to manage this user's access.", which is how the installer is requesting the InstanceInfo SOAP page, and so needs to be active.

Additional Information

A similar error has been seen due to folder permissions being messed up after an upgrade of a MID Server that was previously working:
KB0858646 / PRB1396279 File permissions enforcement removes permissions of the windows service's log on as user, when computer or domain name has lowercase letters, leaving MID Server down