Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

When installing a mid SericeNow server we get 'Invalid service Account' error, but have verified we have a correct service accout/passord

Bill Emmons
Tera Contributor

When installing a mid SericeNow server we get 'Invalid service Account' error, but have verified we have a correct service accout/passord, but get an error during providing the service account. We get through the error that requires the account to be 'Run as a Service '.

9 REPLIES 9

Hi @ParkHyunSun 

 

Please follow below links to solve this :

https://www.servicenow.com/community/developer-forum/mid-server-install-fails-logon-as-service-right...

https://www.servicenow.com/community/itom-forum/service-account-does-not-have-the-quot-log-on-as-a-s...

https://www.servicenow.com/community/cmdb-forum/service-account-for-mid-server-install/m-p/235044/pa...

 

 It could be an issue created by Windows UAC also. May be the account is not getting created with enough privileges if the installer is not launched "as administrator" so try launching the installer as administrator and see if it helps.

 

Please try the above recommendations and see if anything helps.

 

Thanks & Regards

Amit Verma

Thanks and Regards
Amit Verma

Hi, none of them helped.

I just manually installed MID server, and check the Service Tool of Windows.

 

chrohm
Tera Contributor

Do an interactive logon in Windows with the service account once before running the MID server installation

Glenn
Tera Contributor

This worked for us. Thank you!

dougw
Tera Expert

I realize this is 4 years later but I just ran into this exact problem and got past it, I'm posting for any others landing here.  No solution offered in this thread helped.

 

The solution for me was to set the Windows service account password to something without any special characters.  It was also much shorter than what i was originally trying to use so it's possible it's a length issue.  For what it's worth, the password I was trying to use, that didn't work,  was this:  +RfoY]1[]7/TKGpeu+!wVDilX7Bo+=j(fn)vQ]fBQU-zbO8u7f+:4tVc/vqj]yU