Siebel Remote and Replication Manager Administration Guide > Troubleshooting Remote and Replication Manager > Troubleshooting Synchronization Manager >

SynchMgr Situation

The following error was encountered in SynchMgr_xxx.trc/log files:

• DCK-00123: Error opening file (null) for read

  [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:

  • Unable to access the File System directory.
  • File Attachments do not exist in the File System.

    If this occurs with only one particular Mobile Web Client, make sure the System DSN is set up correctly.

    Verify that the attachments are available in the file system. Siebel eBusiness Applications come with a set of default templates. Make sure you have copied the files from the <dbsrvr>\files to the Siebel File System.

• DCK-00164: Error connecting to datasource (null) ((null))

  Possible Causes:

  • Siebel Gateway and Services were started while database server was shut down.

    Workaround:

  • From the application-level menu, choose Navigate > Site Map > Administration - Server Management > Components, shut down the Synchronization Manager and then restart it. Refresh the applet to make sure that Synchronization Manager has a state of running.

    For more details about Synchronization Manager, see Siebel System Administration Guide and Starting Siebel Remote Server Components. SynchMgr_xxx contains the following error message: (syncsrvr.cpp 22(692) err=1700213 sys=0) DCK-00213: Another Synch Server is already servicing this node.

    Possible Causes:

  • Interrupted synchronization sessions. If a client synchronization session stops or disconnects abnormally, the Siebel Synch. Manager may still remain running.
  • If a user connects through a dial-up line via TCP/IP and the line is disconnected, then the TCP/IP session stays active for a certain time. The Synchronization Manager task cannot close until the TCP/IP session is finally released.

    Workaround:

  • Configure the TCP/IP timeout on the Applications Server. Contact your System Administrator for information about the TCP/IP keep-alive functionality.
• SyncMgr_xxx contains the following error message: "DCK-00214: Directory (null) does not exist"

  Possible Causes:

  • Docking directories of Mobile Web Clients have been deleted.

    Solution:

    Reextracting the mobile users will re-create these docking directories and client should be able to download the latest snapshot files and then synchronize with the server again.