Table 1 Common issues (continued)
Symptom | Possible Cause | Solution | |
Fatal Error. | Replication Manager is not able to connect to | • | Ensure that Replication Manager is running |
| the database. |
| on the server. |
|
| • | If the Replication Manager will not |
|
|
| 1. Completely uninstall Replication Manager. |
|
|
| 2. Perform a new installation of Replication |
|
|
| Manager. |
|
|
| 3. Use the Restore utility (see Restoring the |
|
|
| |
|
|
| choose the most recent backup. |
|
|
|
|
Replication | Port number 3095 is already used by another | 1. | Edit the server.xml file in the \tomcat\conf |
Manager service is | application. |
| folder and change the port number 3095 to |
not starting. |
|
| some other free port number value, in the |
|
|
| line Connector port="3095" |
|
|
| protocol="HTTP/1.1" |
|
|
| connectionTimeout="20000"/. |
|
| 2. | Restart Replication Manager from the |
|
|
| windows services list. |
|
|
| |
Replication |
| Continue to backup the database, using backup | |
Manager crashed. |
| utility on the Program Menu at regular intervals, | |
|
| so that these can be used for restoring in case | |
|
| of any Replication Manager crash. | |
|
| 1. | Completely uninstall Replication Manager. |
|
| 2. | Perform a new installation of Replication |
|
|
| Manager. |
|
| 3. | Use the Restore utility (see Restoring the D2D |
|
|
| Replication Manager database) and choose |
|
|
| the most recent backup. |
88 Troubleshooting