mxpassword.exe process CPU at 100%

[Igor Bekker_3]

After changing the SQL password I ran the mxpassword command.


- mxpassword is clocking 100% on CPU

- I get the this error message:
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.


- Login failed for user 'sa'.
- Login failed for user ''. The user is not associated with a trusted SQL Server connection.
- SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed.

Any one have a similar problem?

Thank you,
Igor

[Doug Hafley · Accepted solution]

It sounds like you don't have a good connection to your SQL server. Could you try and create an ODBC connection to the database with your SA credentials to validate that it works?

[Igor Bekker_3]

I checked all the ODBC connections and they TEST fine.

SQLServer service starts. I can open the Home page of SIM, but I have thousands of Login Failed Authentication errors

Igor

[Doug Hafley]

I had this issue when upgraded to the latest SIM. The problem was that when I installed it, I let it install several items that I didn't need nor pay for. I ended up disabling those services and everything worked fine. The biggest culprit was HP Performance Management Pack. Set that to manual, disable it, and restart. See what errors you get then.

[Igor Bekker_3]

still same problem.

I changed the service account that starts the app and the DB. I used the hp tools and changed the config files.

I can now start SIM, but still tons of error messages as described above

[David Claypool]

Igor: HP SIM only uses NT authentication for MSDE and/or SQL Server. If you changed the password for the 'sa' account and then told HP SIM to use it, that's your problem. You need to tell HP SIM about an NT account that has privileges...

[Igor Bekker_3]

how do I tell SIM about the NT account? and are you saying I should use the NT account for DB instead of the SQL sa?

[Doug Hafley]

I seem to remember that I had to run a utility under \program files\hp\systemsinsightmanager\bin in that folder there are a lot of powerful utilities that can set the SA account connections. I had to do something like this before and I ended up using this link to resolve my issue: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1068939

If all else fails, consult HP. The people that work with SIM at HP are very knowledgable about how to utilize the command utilities to fix these issues.

[Daniel Leblanc]

You should try disabling PMP and VMM to see if that stop the problem!

Dan