Table 26.	Problems That Synchronization Manager Logs in the Log File
     | 
    Diagnostic Steps or Cause  | 
     | 
    DCK-00123: Error opening file (null) for read. The Synchronization Manager log contains the following error message:  [ERR33] (drl.cpp 5(206) err=1700123 sys=1400022) DCK-00123: Error opening file d:\siebfile\S_DOC_PPSL_0-CQNE_0-S9.saf for read 
 | 
    Possible causes include the following items: 
- Unable to access the file system directory.
 - File attachments do not exist in the file system.
  
 | 
    You can do the following: 
- If this problem occurs with only one particular remote client, then make sure the System DSN is configured correctly.
 - Verify that the attachments are available in the file system. A Siebel application comes with a set of predefined default templates. Make sure you have copied the files from the 
dbsrvr\files directory to the Siebel File System.
  
 | 
    DCK-00164: Error connecting to datasource (null) ((null)) The Synchronization Manager log contains the following error message:  (syncsrvr.cpp 22(692) err=1700213 sys=0)  
 | 
    The Siebel Gateway and Services were started while the Siebel Server was shut down.  | 
    You can do the following: 
- Navigate to the Administration - Server Management screen, and then the Components view.
 - Shut down the Synchronization Manager, and then restart it. 
 - To make sure that Synchronization Manager contains a running state, refresh the applet.
  
For more information, see Configuring Server Components for Synchronization and Transactions and Siebel System Administration Guide.   | 
    DCK-00213: Another Synchronization Server is already servicing this node.  | 
    Possible causes include the following items: 
- A synchronization session is interrupted. If a client synchronization session stops or disconnects abnormally, then the Siebel Synchronization Manager might still be running.
 - If a user connects to a dial-up line through TCP/IP and the line is disconnected, then the TCP/IP session remains active for a certain time. The Synchronization Manager task cannot close until the TCP/IP session is released.
  
 | 
    You can do the following: 
- Configure the TCP/IP timeout on the Siebel Server. Contact your System Administrator for information about the TCP/IP keep alive functionality.
  
 | 
    DCK-00214: Directory (null) does not exist  | 
    Docking directories of remote clients are deleted.  | 
    You can do the following: 
- To recreate these docking directories to enable the remote client to download the latest snapshot files, you can reextract the users.
 - Resynchronize with the Siebel Server.
  
 |