Troubleshooting a Bad Connection During Synchronization Problem

This topic describes how to troubleshoot a problem that occurs when connecting to the Siebel Server during synchronization. If this problem occurs, then Siebel Remote typically displays a message that indicates there is a problem with the connection between the remote client and the Siebel Server.

To troubleshoot a bad connection during synchronization problem

1. Log in to the remote client.

2. Open a DOS command-line window on the remote client.

3. To ping the Siebel Server, run the following command from:

   ping name_of_the_server_computer
   

   If you cannot ping the Siebel Server by name, then try pinging the IP address of the Siebel Server. The expected result is that the ping can resolve the host name to an IP address and connect to the computer.

4. Before attempting to synchronize again, increase the level of tracing on the remote client.

   For more information, see Recovering from a Failure.

   For help with a connection problem, see Getting Help from Oracle. Be prepared to send the syncthrd log file. For more information, see Log Files on the Remote Client.

5. If the connection is created on the Siebel Server, or if the Synchronization Manager server component is not running, then examine the Synchronization Manager log file.

   For more information, see Naming Conventions for Log Files.

6. Examine the DockConnString in the [LOCAL_SE] section of the configuration file on the remote client.

   For more information, see Examining the DockConnString Parameter.

7. If the failure message is Login Failed, then verify that Synchronization Manager references the correct user name and password when it connects to the Siebel database.

   For more information, see Registering a New Password with the Siebel Gateway.