That would do it!
These keys get created during installation and if those have been deleted, you are NOT going to be able to start the service.
Did these get mistakenly deleted somehow?
Sounds like something came in and deleted them.
OK, please send a email to www.solarwinds.com/customerportal and we will schedule a online meeting to get you back in business.
It seems that every time I run updates on my Eminentware server I have to go through the process of clearing the two keys in the registry, changing the password on the ewdgssvc-9862 userid, change the password on the Eminentware Data Grid Service set for automatic startup, and then reenter the passwords for the credentials. Then every thing works till the next windows update.
I have had to do this 3 times since upgrading to the latest version. Is this just a coincidence or did something change with the latest update?
the passwords for credentials are encrypted using the DPAPI.
This is tied to the EminentWare Server service account.
Has the service account been changed to have an expiring password?
The only time this should happen is if the password for the service account is somehow being changed?
Specifically, how often is this happening?
Every 3 months?
We would need to look at the security settings on the server to see if there is a setting that is causing this issue.
It is certainly not normal.
Please send a email to www.solarwinds.com/customerportal with your availability and we will schedule a online meeting.
I think I fixed the problem. Seems the locally created id on the eminentware server did not have permission to logon as a service. After adding the local id to our default domain policy in GPO as an id with permission to logon as a service everything seems to be working fine.
I've seen another that caused the error 1064 which i'll post for other users that may find this thread:
If something has changed permission to DCOM on the EminentWare server, the 1064 error can be encountered when the EminentWare Data Grid Service service attempts to start. (If the Console is started when this error is present, it may show as an RPC connection error and the console will not fully start.)
- Launch DCOMCNFG.exe
- browse to 'Console Root -> Component Services -> Computers -> My Computer' and get Properties
- Go to 'COM Security' tab
- Under 'Launch and Activation Permissions', click 'Edit Default'
- Verify that SERVICE has 'Allow' permission to 'Local Activation'
Another possible cause of this error is if something has deleted or renamed the EWLICENSE.LIC file under \Program Files\EminentWare\Server. If that file is missing on your server, please contact firstname.lastname@example.org.