Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide > Troubleshooting Remote and Replication Manager > Synchronization Manager >
FAQ: Cannot Connect to Server During Synchronization
As the text of the error message indicates, there is a problem with the connection between the Siebel Remote client and the Siebel server.
If this error occurs, do the following:
- Ping the Siebel server from the client by running the following command from the DOS window on the client machine:
If the server cannot be reached by name, try the IP address. The expected result is that the ping is able to resolve the host name to an IP address and connect to the machine.
- Before synchronizing again, refer to How to Set Client-Side Logging to increase the level of client-side tracing. It is located in the \"log" directory of the client. It is named SyncThrd*.log. Send this file to Siebel Technical Support for review.
If the connection is established on the server then there will also be a sync manager trace file. It is named SyncMgr*.log located in the Siebel server log directory.
Check the DockConnString in the [Local] section of the client's CFG file and confirm that it is set to the host name of the Siebel server with which this client will synchronize. Send the client's CFG file to Siebel Technical Support for review as well.
It is recommended that you specify the DockConnString in the following format:
- Siebel server machine name: network protocol: sync port #: server: encryption.
- Siebel server machine name, assuming the default synchronization port number is 40400.
Remote users use the DockConnString parameter in the CFG file to synchronize to the server. For details regarding the syntax of the DockConnString parameter, see Synchronization Parameters.
- If the Synchronization Manager component is not running, check the following:
- %Siebel_server%\log\SynchMgr* log file.
- If the failure message is Login Failed, then verify that Synchronization Manager uses the correct user name and password when connecting to the database.
This should be the system administrator user (SADMIN) and not the database tableowner (SIEBEL or dbo). The system administrator's password in the database must match the password registered in the Gateway Server. If the SADMIN password changed in the database but not in the Gateway Server, users will not be able to log in to Server Manager views. To register a new password with the gateway, verify that the Gateway Server service is running and complete one of the options below from the %Siebel_Server%\bin command prompt.
srvrmgr /g <GatewayName> /e <EnterpriseName> /u <username> /p <password>
/g: specifies the host name of the machine running the gateway
/u: Siebel Administration username
/p: Siebel Administration password
When the Server Manager prompt appears, type:
srvrmgr> change ent param Password=NewSADMINPassword
For more information about Server Manager, see Siebel Server Administration Guide.
srvrcfg /g <GatewayName> /e <EnterpriseName> /m enterprise /w Password=NewSADMINPassword
Stop and restart the Siebel server service to invoke the change.
NOTE: Use caution when changing the password—an incorrect entry will cause errors throughout your system.
If the password of the database account is unchanged, the password of the system administrator account can be changed in the Server Manager views.
To view the current sync manager port number
- From the application-level menu, select View > Site Map > Server Administration > Components.
- From the Server Components list, click Query and run a query for the Synchronization Manager component.
- From the Server Components list, select the Synchronization Manager component for the appropriate Siebel Server.
- Click the Components Parameters tab, and click Query to run a query for the Static Port Number parameter.
To change the current sync manager port number
- Navigate to the Component Parameters tab as in the previous procedure.
- In the Component Parameter list, run a query for the Static Port Number parameter.
- Enter the new value in the Value on Restart field.
- Restart the server.
- Test the connection by copying a CFG file, from a user that is able to connect or synchronize, onto the client machine where the behavior is occurring.
Observe the results and compare the two CFG files for any noticeable differences.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide Published: 19 November 2003 |