question New MID Server service won't start in ITOM forum

New MID Server service won't start

David Casper — Mon, 14 Feb 2022 20:25:53 GMT

On a new install I'm configuring in our lab environment I keep seeing the following error in the wrapper log after attempting to start the service.

[Fatal Error] :32:78: The character reference must end with the ';' delimiter.

This is on Windows 2016 using a domain service (non-admin per doc) account as the service account. Any suggestions are greatly welcome. 🙂

Re: New MID Server service won't start

Logan Poynter — Mon, 14 Feb 2022 20:38:18 GMT

Hello David,

Check your config.xml in service-now\<mid server name>\agent folder. Sounds like a misconfiguration issue.

Please mark my answer as correct/helpful if it has helped you.

Thanks,
Logan

Re: New MID Server service won't start

David Casper — Mon, 14 Feb 2022 20:56:49 GMT

Not seeing any issues in the config file. Instance URL and creds are all correct.

Domain service account is a local admin. Only thing I can think of is trying to make it a domain admin. If I open a cmd prompt as the service account, change to the agent dir and try to run the start.bat I receive a 'StartService: OpenService FAILED 5:' error.

Re: New MID Server service won't start

_raj_esh — Mon, 14 Feb 2022 21:12:36 GMT

Hi David,

Can you please try the following steps and see if it helps?

Open the wrapper-override.conf file in the MID Server installation folder.
Change the wrapper.name and wrapper.displayname parameters to the service name that you want to keep.
Start the MID Server.

Also, please check the KB0539821

Thanks,

Raj

Re: New MID Server service won't start

Logan Poynter — Mon, 14 Feb 2022 21:14:49 GMT

Hello David,

Per the install prereqs: "The user cannot be a local system or an administrator level account (local admin, domain admin, etc.)" - of course, you can do whatever in a lab environment you want to. ????

Have you already validated Local GPO that it (the account you're trying to use) can log on as a service?

Please mark my answer as correct/helpful if it has helped you.

Thanks,
Logan

Re: New MID Server service won't start

David Casper — Mon, 14 Feb 2022 21:42:01 GMT

They are already set to the service name and display name that I set during the install. I have to be missing something.

@Logan Poynter I removed the local admin priv for the user. I had uninstalled and tried from scratch and it did throw the 'user must not be admin' error. Once I removed local admin rights it installed fine. However the service still will not stay started.

The delimiter error continues to be the last thing logged, then the wrapper stops.

Re: New MID Server service won't start

David Casper — Mon, 14 Feb 2022 22:14:59 GMT

I was able to get the service to start. Turned out the issue was with the password. However the MID server was not showing in the instance. So I tested trying to access the agent folder through cmd by opening cmdb with the service account user. It says access is denied. I tried restarting the service through Windows service and it is now also giving me permission issues. I don't remember configuring the initial mid server taking so long and having so many issues.

Re: New MID Server service won't start

David Casper — Mon, 14 Feb 2022 22:19:20 GMT

I had to manually give the service account permission to the agent folder. Now waiting for the MID server to show up in the instance. Not holding my breath though as it usually doesn't take this long.

Re: New MID Server service won't start

David Casper — Mon, 14 Feb 2022 22:32:40 GMT

So after I added the service account to the agent folder permissions, they were removed automatically. Saw a warning message in the wrapper service that pointed me to it.
If the service account isn't supposed to have any admin priv , how are you supposed to get this to work then?

Re: New MID Server service won't start

_raj_esh — Tue, 15 Feb 2022 13:11:59 GMT

Hi David,

Can you check Service permissions on mid server if this helps?

Thanks,

Raj

Re: New MID Server service won't start

David Casper — Wed, 16 Feb 2022 18:54:21 GMT

This was resolved by assigning the service account ownership on the agent folder and allowing inheritance. I tried multiple troubleshooting steps, unsuccessfully, with SNOW support before coming to this workaround.

Not sure why this setup was so difficult, but appears to not be a common issue.

Re: New MID Server service won't start

sun1305 — Tue, 09 Jul 2024 00:38:29 GMT

Hello All,

Please try this solution when you're installing a mid_server if you're getting this below error:

Step1- windows and search for command prompt or use shortcut Win+r >cmd > right click Run as administrator

Step1_ Run as Adminstrator

Step2: Copy the Path of the Mid Sever Agent file location

Eg: C:\Users\YOUR PATH LOCATION\Downloads\mid.washingtondc-12-20-2023__patch3-hotfix1-05-12-2024_05-16-2024_0813.windows.x86-64\agent

Step3: Start.bat

Step4: please check your PDI and refresh the mid-server

Hope this helps!

Thank you all

Regards

Sunil Sharma

Re: New MID Server service won't start

MattSN — Wed, 10 Jul 2024 11:12:12 GMT

I've seen this before as well. Temporarily assigning the Windows administrator role to the service account and starting the service will allow it to fix the folder permissions. Afterwards remove the service account from Windows administrator and restart the service.