HP 3PAR Recovery Manager Software for VMware vSphere Licenses - Manual (Page 100)

After installing Recovery Manager, it is unable to manage the Exchange cluster from Exchange
management. It returns a COM class factory error.
OR
After installing Recovery Manager, an MSCluster-related COM class factory error is returned.
Suggestion:
If the previous version of Recovery Manager is uninstalled, the msclus.dll is unregistered and
results in the COM class factory error. To resolve this, run:
- regsvr32 C:\Windows\system32\msclus.dll
Problem:
How to recover the Exchange writer status from last error Non-retryable to No error.
Suggestion:
If the Exchange writer status shows the last error as Non-retryable on a CCR active or passive
node or an LCR passive copy, try one of the following methods to get the writer into a stable state
with no last error.
Restart the Microsoft Exchange Replication service from the passive node.
OR
Net stop MSExchangeRepl
Net start MSExchangeRepl
If restarting the Microsoft Exchange Replication service does not solve the problem, try one of the
following methods:
Restart the Microsoft Exchange Information Store service.
OR
Net stop MSExchangeIS
Net start MSExchangeIS
Problem:
How to recover the System Writer status from last error Non-retryable to No error.
Suggestion:
Restart the Cryptographic Services service.
OR
Net stop CryptSvc
Net start CryptSvc
Problem:
Remote Copy status for the volume group does not permit synchronization.
Suggestion:
The involved Remote Copy group has virtual volumes that are not in synced state. Wait until all
volumes in the group display in synced state and then retry the operation.
Problem:
An LDP COM error message appears similar to the following:
RME5220: ERROR: COM: Failed to bind to LDAP path Group,CN=InformationStore,CN=WWDC1-EX-CPBE01,CN=Servers,CN=Denver,CN=Administrative
Groups,CN=Westwood,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=westwood2000>: 0xc1032221.
Suggestion:
You may not have permissions for the specified storage group, or the storage group is absent.
Problem:
When using Symantec NetBackup, you see this message: 0x1: ERROR: Cannot connect to [NBU
server name]; socket error.
100 Troubleshooting