chrisfendya
Contributor
Contributor

I have been on client site and ran into this similar issue. Like most, I attempted all things stated here without resolution. The fix was shortly determined to be ensuring the service account's (AD User) default database was set to the Update Manager database within SQL. I did NOT need to change the Update Manager service to run under the service account's ID. Setting the service account to run under the service account only made the service fail to start.

It should probably be noted that after I made the SQL changes I did remove and reinstall Update Manager along with resetup the DSN. During the reinstall of Update Manager, I utilized the service account ID/PW during the entire install process.

Good luck and hope this helps everyone going forward!

Reply
0 Kudos