VMM Problem after password change

[Rob Buxton]

Probably related to the password change that Joel provided the solution for.
The VMM (2.0) Service starts, but as soon as I try and use it the Service stops and I get a message in HPSIM, VMM Service not available.

I've looked at the mxpassword man pages, discovered the nice and easy to use mxpassword -g option. But there's no passsword to change for VMM.
Does VMM use a password to the remote database or is this something else?

[Rob Buxton]

As an update, I removed and reinstalled VMM 2.0. The problem remains. The installation appeared to complete okay and I entered the updated password credentials.

I only get a Green Indicator in the VM column for the VM Host. Although identified as VM Servers by HPSIM, the VM column for all of the VM Guests is blank.

I keep finding the VMM Service is stopped on the HPSIM Server. If I restart it, it runs until I initiate a VMM type request from the HPSIM Management page, e.g. expand the VM details.

[Rob Buxton]

And another update in case anyone is reading this.
I no longer think it was the password change, but the installation of the MS iSCSI Initiator that caused the problems.
I removed VMM and deleted its associated databases.
I also removed the iSCSI Initiator that seems to be required by VMM.
I then rebooted the Server, reinstalled VMM 2.0 and it is now working.
If anyone from HP is looking at this thread I'd be grateful for any feedback.

[Brent Neste]

I'm seeing something like this as well. I started with a clean install of SIM 5.0 and the required MSDE database. I needed to reinstall the VMM components and that went fine. But, after running for maybe two minutes the VMM service stops. I noticed a DrWatson error in the Windows application log... I'll sum it up:
Source: DrWatson
Event ID: 4097
Description (partial): The application, , generated an application error...

The data contains some info about the error and then the general system info dump. The notable info from the data is "Application exception ocurred" and "Access Violation". I know that this is related to the problem because the user account listed in the error is the account which my VMM service runs with. I've checked all the permissions and everything... can't seem to figure it out. I thought this info might help in troubleshooting your problem.

One last thing... I do not believe the VMM was working before I reinstalled it. I just never looked at the application log at that point.

[Rob Buxton]

Brent,
I did not get any Dr Watsons.
VMM is now working for me and the service has not stopped since the removal of the iSCSI Initiator and reboot of the Server.
Are you using VMM 2.0 or 1.11?
Are you running the VMM Service from a separate account than the HPSIM service?

[Brent Neste]

I'm running the latest, so 2.0. It is in fact using the same account that SIM does. I did my VMM reinstall while logged in as the account I was using during the SIM install.

It may be that the VMM service is failing shortly after I start the SIM service. I am going to stop SIM, and only restart VMM to see if it stays running or stops after a short time. I'll post back when I have info. Thanks!

-Brent

[Brent Neste]

Ok - I have verified that the service fails after running for about 2 minutes, regardless of state of the SIM service.

[Rob Buxton]

About the only difference I see is that you're using MSDE, I'm using SQLServer.
For the cleanest reinstall, you can try Uninstalling VMM and then deleting the VMM Database. Not too sure how you do that with MSDE. That way you get a clean refresh of the database.
You could check the VMM Logs. See if there's anything in them. That's where I found the hints as regards the iSCSI stuff.