Restarting MxDomainManager Event

[Richard Ward_6]

Ever since The C drive got filled up (now corrected in SQL 2000) I can not get into SIM 4.2. I get repeated messages that SIM restart was successful event id 3 and restarting MxDomainManager warning event ID 2 in the logs. Is there a fix for this or must I reinstall SIM 4.2 from scratch? Running W2003 server with SP1 & SIM 4.2 SP1.

Richard

[Jason Hindson]

I've never heard of this issue, but you may consider installing SP2 for HP SIM before you try a complete reinstall. The problem may be resolved by SP2. Best of luck.

[Richard Ward_6]

I did the upgrade and had the same problem. I just finished redoing the whole server (W2003 Std with SP1) and installed the SIM 4.2 SP1. Running Discovery now to rebuild the database. So far so good.

[Andreas Suether]

Hi,

we have the same problem with our SIM 4.2 SP2.
MXDomainManager stops and restarts every Minute.

Stopping HP SIM Service for a moment and starting it again manual solves the problem for a short time.

Diskspace is not too small.
Memory seems also fine.

How can I solve this?

[Darrin Rawls]

Sounds like the SIM service is having a hard time connecting to the SQL service. Is there relevant NT/SQL Event logs logged for SQL? My guess is that something is going on in SQL-land...

[Andreas Suether]

Hi,

SQL Server is running on the same Server and is working well without entrys in eventlog.

I wonder if there are troubles with Multihomed hosts?

[Darrin Rawls]

No, we do that in the lab all the time...

[Marc Hewitt]

Im getting this also..

Just installed :
HP SIM 5.0
Windows2003 SP1
MSDE 2000 with SP3a (installed via the SIM package)

approx Every 1 minute getting "Restarting MxDomainManager" in the Application log.

Web interface wont open

No errors from SQL in either System or Application log.

Any Ideas ?

[Marc Hewitt]

Tried the installation on another server..

Running SQL 2000 with SP3a instead of MSDE;

Getting same problem with "Restaring MXDomainManger"

SQL is logging the following in the Application log;

EventID = 17052
Error: 15457, Severity: 0, State: 1
Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

[Marc Hewitt]

Also..

There are lots of MxInventory processes running.. see attached

Cheers

[Phil Gillespie]

I gave up with this. The event logs filled up with Restarting and the interface wouldn't work.

Since this was just a standalone SBS2003 server I un-installed the software and haven't tried to reinstall since.

[Marc Hewitt]

As I thought..

One MXInventory.exe process for each Restart MXDomainManager event in the Application log..

[samuel_34]

I had the same problem a while ago - if I remember rightly it was caused by my ODBC configuration - you could try connecting to the DB via Access or similar to check the ODBC settings out?

I also seem to remember that the rights to the DB were set using the account that Insight was installed with - you might want to check that the account that you're using has rights to the DB?

Just a few thoughts - hope they're of help.

All the best,

Sam

[Marc Hewitt]

well I got it...

The customer has a customised build.. process.. they disable the "SNMP Trap Service" as part of the build.

set the service back to automatic... bingo. problems gone.

Thanks for the suggestions guys.

Cheers

[Matthew Hoffman]

I just installed SIMv5 on an XP machine.

I have 2GB of ram and the new install is launching and relaunching mxinventory.exe. This application is a total dud. I can't open anything.

I try opening systems insight manager and a "Checking HTTP server status" window appears. It's been there for 14+ minutes and how 1.4GB of my ram is eaten up by multiple mxinventory.exe instances.

Does anyone know what the issue is? There's nothing particular in the event log. This program is so frustrating...

[Todd Lowery]

I found this online and it worked for resolving these issue for me:

Anonymous (Last update 4/23/2007):
This can happen when you change the password for the account that the HP SIM services are running under. In addition, if you are using SQL for the back-end (instead of MSDE), you will want to make sure that your SQL account is what you expect it to be. Our system had a service account for the actual services, but it was using the Domain Administratorâ s logon for SQL access. This can be changed in "%programfiles%\HP\Systems Insight Manager\Config\database.props". We just changed it to our service account (after granting correct rights on the SQL side of course). If you need to change the password, use:
mxpassword -m â x MxDBUserPassword="newpassword" (without the single quotes) from a command prompt.

Mihai Andrei (Last update 2/10/2006):
From a newsgroup post: "HP Sim uses the local admin account to run the service and connect to the SQL Server's database (on remote server). That was changed to use Local System (as we change passwords quarterly). Resetting it back to local admin worked for us".

[Todd Lowery]

The command did not come over formated correctly here is is again:

mxpassword -m -x MxDBUserPassword=newpassword

[Tom Rynaarts]

I had the same problem. I changed the config of HP sim (Globalsettings.props, to resolve another problem). When I restarted the HP SIM service I got the same problem. The web interface would not come up and every minute the MXdomainManager.
I restarted the SNMP service and then found in the evenviewe that SQL had fixed a number of entries.
After that al starte dok and the web interface was back. Hope that this might help.