Users in table hpmxUsers, but can't log in

[Horst Hinz_1]

I'm still having the issue of not being able to log into SIM 4.2 after an upgrade from 4.1. I checked SQL and all the users are listed in the SQL table hpmxUsers,but I can't log in. HP Tech support was unable to help me at all. I've got 160+ servers in SIM that I need to monitor including a number of old IBM and Dell servers that I manually entered, I really don't want to have to blow this all away and start over. Anyone able to help?

[Joel Rubenstein]

To view the current users configured in SIM open a command prompt on the SIM server and type "mxuser -lt"

This command can also be used to add new SIM users which must first be added as Windows users.

mxuser -a username -p full

where username = domain\username if adding a domain user.

[Horst Hinz_1]

Thanks for the reply, it mxuser -It doesn't work. It says -I is an invalid option.

Running just mxuser says "an error occured while attemtping to establish a connection to the repository". I'm running a remote SQL server and I've manually created the ODBC connection to the database already (HP tech support got me to do this, it was missing).

Are there specific names that SIM is looking for in the ODBC connection and maybe those are wrong?

[Joel Rubenstein]

If you look in the file c:\program files\hp\systems insight manager\config\database.props file

You will see entries like

hp.Database.databaseName=Insight_v42_0_144947271
hp.Database.dsn=Insight_v42_0

The first is the name of the SIM database and the second is the actual ODBC system dsn that must be configured.

However if SIM actually starts up and displays the login page then your ODBC configuration is probably correct.

The file c:\program files\hp\systems insight manager\logs\domainmanager.xxxx.out.log where xxxx is the current PID of the mxdomainmanager process is an ASCII log file containing all the SIM startup messages. When SIM starts up correctly you should see a line at the end of the file like.

OK - waiting for events primary

[Horst Hinz_1]

The ODBC connections look correct based on the database config file, and I do get the correct entry at the end of the domainManager.xxx.log file, however at the beginning of the log file there are errors that look like:
error loading view for user 2ex com.hp.mx.core.nodegroupmanager.MxNodeGroupPersistenceException: An error occurred while attempting to establish a connection to the repository.

There is also a domainmanager.xxx.err.log file and it contains a number of lines as well, including:
com.hp.mx.core.nodegroupmanager.MxNodeGroupPersistenceException: An error occurred while attempting to establish a connection to the repository.

Running mxuser still comes back with the same error messages.

[Joel Rubenstein · Accepted solution]

It would seem that your database was somehow corrupted during the upgrade.

To attempt to fix the database you could open a command prompt on the SIM server and type "mxconfigrepo -f".

If this does not correct the problem then your only alternatives would be to uninstall SIM and reinstall SIM 4.2 starting over or if you have a good backup of your SIM 4.1 database and of the c:\program files\hp\systems insight manager\config directories, uninstall SIM 4.2, install SIM 4.1, restore the 4.1 database and config files and edit the ODBC System DSN entry to point to the restored 4.1 database. Then you should have a functional SIM 4.1 install again.

[Horst Hinz_1]

I ran the mxconfigrepo -f as you suggested. The following is the result:

ERROR: TABLE hpmxNodeGroupObjects KEY NodeID may contains 1 entries not in table devices KEY mxGUID
Completed database checking with errors, CMS may not be able to run.

It then goes onto say "fixing possible database corruption..." and Completed repository corruption fix.

2nd run had NO errors.... and then I'M ABLE TO LOG IN!!!!!!!

Thank you SO MUCH for your help!

[Horst Hinz_1]

Quickly realized almost all of my systems have disappeared from SIM now though. Guess my only option is to restore the database back to 4.1 or is there anything else I can check?

[Joel Rubenstein]

Have you tried to rediscover the missing systems. I would try that before downgrading SIM.

[Horst Hinz_1]

I had manually added a bunch of legacy HP gear, some Dell and IBM systems manually, will SIM discovery those?

[Joel Rubenstein]

It depends on how you have your discovery filters configured.

[Horst Hinz_1]

Thanks, I'll look into doing the discovery again on those systems. Thanks again for all your help.

[Horst Hinz_1]

It looks like the problems on this SIM installation are bigger than just not being able to log in. Manual discovery of systems does not add systems, I still can't click on servernames and get the the server's page, auto discovery doesn't run properly.

I'm going to do a clean 4.2 installation and if that doesn't fix my problems then I'll have to restore my 4.1.