Problem with MID Server Installation - start.bat ending before launching the serviceIssue Customer was experiencing problems with the MID Server installation file that are caused by a failing condition in a batch file. The batch file is “start.bat” which should normally be run automatically when using the installer.bat file, as described in the ServiceNow documentary. A new windows service for the MID server is not created and cannot be started. The installer shows “installation successful” but the MID Server is actually not started.CauseThe start.bat file was being run by an administrator user but not 'run as administrator' and would just close immediately when being run from the command line.ResolutionThe start.bat command works when run from an elevated shell (run as administrator) When running command 'net session', there was an 'error 5' shown. Running a command prompt as administrator gave the expected output - 'There are no entries on the list' If running the .bat files to install a MID server, these must be run from an elevated command line - Right clicking on the cmd icon allows it to be run as an administrator with elevated permissions