====== Troubleshooter: Replication Previously Setup And Running ====== -->Replication previously set up and running Is the master server running --> Yes Is the replicant server running --> Yes Are the ports used by the master and replicant open and listening --> Yes <-- --> No Have your network staff open the required ports for inbound and outbound communications <-- --> Not sure --> Checking master to replicant port access <-- --> Checking replicant to master port access The following commands are using default install values. If these values do not match our installation you will need to replace with the correct database location and required ports Stop the replicant server. Open config file, comment out replicant section and save file restart server in foreground mode, using the command in an administrative command line window TMSS10Server -f -h "%TMSS10DB%" -p 5010 Open another administrative command line window and execute the command netstat -na | find "5010" to check that the port is actively listening. If it is you will receive output similar to netstat -na | find "5010" TCP 0.0.0.0:5010 0.0.0.0:0 LISTENING From the master server run the command TMSS10Ping with the replicant server address and port. --> Connection successful <-- --> Connection unsuccessful Have your network staff open the port <-- <-- <-- <-- --> No Restart the replicant server using the Framework Server Helper, administrative command line or windows services <-- <-- --> No <-- --> Not sure From an administrative command line window on the master server run the command TMSS10Ping --> Connection Successful From an administrative command line window on the replicant server run the command TMSS10Ping --> Connection Successful <-- --> Connection Unsuccessful <-- <-- --> Connection Unsuccessful Restart the master server using the Framework Server Helper, administrative command line or windows services <-- <-- <-- {{tag> server replicate update_doco}}