A Troubleshooting

The Replication Manager provides error messages for all errors. The user can continue with other operations as normal, unless the error prohibits the normal operations of the software.

In the case of critical errors such as a database connection failure or an inability to contact the server, an error page appears and provides a description of the error and the option to save the error log on the client system. The user is able to login to the application after the issue is solved.

To save the error log, click the Save Error Log button.

NOTE: All errors are saved to the log file on the server. The log file is located at log\RMS_ServiceLog.log. Contact HP Support for help.

Table 1 Common issues

Symptom

Possible Cause

Solution

 

 

 

Unable to login

• The user already logged in and is trying to

Click the Force Login box on the login page.

 

login from a second browser window.

This will terminate the previous session.

 

• The user has closed the browser window

 

 

 

abruptly while accessing the application and

 

 

 

is trying to login from a new browser.

 

 

 

• The user clicked on the browser refresh

 

 

 

button.

 

 

 

 

 

 

Unable to login,

The host name is being resolved to an IPv6

•

Use the IPv4 address of the host to access

flash player

address instead of an IPv4 address.

 

Replication Manager.

exception, and

 

•

Resolve the host name to an IPv4 address

application does

 

 

 

instead of an IPv6 address.

not respond

 

 

 

 

 

 

 

 

 

Server not

The server status is not Good or the server is

1.

Check the status of the server.

available—Replication

disconnected.

2.

If the server status is Good, check the

Manager cannot

 

 

connection to the server.

connect to a server

 

 

 

that has already

 

 

 

been added to the

 

 

 

system.

 

 

 

 

 

 

 

Device addition

• Invalid IP Address.

•

Add the device with valid IP address.

failure

• The specified IP address is not reachable,

•

Check the network connectivity and ensure

 

 

either due to network problems or because

 

the device is running.

 

the D2D device is not running.

•

Add a valid D2D device.

 

• The specified IP address is not for a D2D

 

•

Check the history log to find which device

 

device.

 

 

failed to add, ensure device connectivity,

 

• Could not add some of the devices.

 

 

 

then add the device again.

 

 

 

 

86 Troubleshooting