New MID Server service won't start

[David Casper]

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. 🙂

[David Casper]

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.

[David Casper]

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. 

[David Casper]

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. 

[David Casper]

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?

[Raj_Esh]

Hi David,

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

Thanks,

Raj