Backing up and restoring HP Insight Management 7.3 Central Management Server (Windows)

Technical white paper | HP Insight Management 7.3

Appendix K: Troubleshooting

The

mxsync

tool times out before Systems Insight Manager starts successfully.

By default, mxsync waits 15 minutes for the Systems Insight Manager Windows service to start before terminating. To

change the wait period, set the variable init.hpsim.wait.minutes in the

<SIM>\mxsync\conf\mxsync.properties file to the preferred value. On a Microsoft Windows Server 2008/2012

server, you may see a timeout error if you are not running mxsync as Administrator. You must run mxsync as

Administrator.

ERROR: Access denied. The entered logon token is invalid. Obtain a new token and perform the operation again.

The token used by mxsync to connect to Systems Insight Manager is no longer valid. The most likely cause is that the

session has timed out because of inactivity. The default timeout value is 30 minutes. You must exit the mxsync tool and

then restart it to establish a new session.

The

mxsync

tool fails if

lsmanalyzer

cannot communicate with HP Storage Provisioning Manager.

This can occur if the certificates between Matrix OE and SPM become out of sync after the restore. In this case, the

lsmanalyzer tool tries to create the MatrixService1 account, but fails because the account already exists.

Here is an example of the mxsync output when lsmanalyzer cannot communicate with the HP Storage Provisioning

Manager:

**** Analysis: Logical Server Catalog Storage Pool Entry Resources ****

**** Section 3 of 5, phase 3 of 3 ****

Analyzes the definition of catalog-based storage pool entry resources to ensure

the definitions are consistent with the actual state of the managed resources.

Running lsmanalyzer to perform the analysis. This may take a few minutes.

Complete analysis of catalog storage pool entry resources. ...........[ERROR]

ERROR: Execution of lsmanalyzer, "C:\Program Files\HP\Virtual

Server Environment\bin\lsmAnalyzer.bat" --catalogSPE,

failed with an unknown error.