- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2020 06:44 AM
Hello everyone,
I have an issue with MID Server installation after Orlando upgrade.I want to install mid server on my laptop.(on new york release everything went good).
I have downloaded orlando version mid server.Installed it.everything went well.no errors.
username created with mid_server role. config.xml file checked everything is correct (username password instance url)
System log->All there is an error :Basic authentication failed for user: midserver but all credentials are correct.
during installation there is an error: Required credentials not available for BASIC <any realm>Instance_number
i have checked Mid server logs :D:\MidServer\MidServer1\agent\start.bat
May 01, 2020 3:44:53 PM com.service_now.mid.installer.OutputHandler info
INFO: Only one wrapper service is allowed for a MID server. Make sure that there is not another service under a different name for this MID server.
***UPDATE***
Another log from agent/logs:
WARNING *** WARNING *** Configuration file not found, using defaults: D:\MidServer\MidServer1\agent\config.xml
05/01/20 17:30:54 (818) Thread-3 [0:00:04.578] HostUtil.getHostname: MY_DESKTOP_HOSTNAME
05/01/20 17:30:59 (755) Thread-3 Setting basic authentication with user midserver
05/01/20 17:31:01 (366) Thread-3 Successfully connected to instance:
...
here logs about my instance details
...
05/01/20 17:31:01 (741) Thread-3 SOAP basic authentication is enabled
05/01/20 17:31:01 (741) Thread-3 SOAP strict security is enabled
05/01/20 17:31:01 (741) Thread-3 User midserver has all necessary roles
Please help
Solved! Go to Solution.
- Labels:
-
Event Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-01-2020 07:28 AM
Hi - based on msg in log, "Only one wrapper service is allowed for a MID server. ", I'm guessing you might be naming the windows service the exact same name as your prior install (you mentioned a previous install). Be sure the name you give the installer a unique name for the WINDOWS SERVICE - NOT the MID server name.
While you can install multiple MID instances per windows box, each windows service must have an unique name. During the install, there is place to enter this but its not clear in the installer that they are talking about the windows service. In fact, its vague as @#$%^& ... poorly conveyed in the UI.. but its the screen that is talking about the wrapper. (same screen where you name the MID server name as it shows up within the instance -- but I'm referring to a different field on that install screen)
Hope this helps?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-04-2022 02:28 AM
- Log in to the host machine as a privileged user.
- Start the Services console (Start > Run > services. msc).
- Right-click on the service name (by default it starts with ServiceNow MID Server) and select Start from the context menu.
Regards,
Peter