2. Workgroup Synchronization Commence Corporation

3. Workgroup Synchronization  Basics  Changes between 3.x and 4.0/2000/RM  Details of Synchronization  DATA.INI settings that affect synchronization  Troubleshooting  General steps  Examples

4. The Basics  Commence keeps track of the changes  SYNCLOG.PIM  DATA.INI  Changes copied to files  0001006b.UP  Files are exchanged between the Clients and Server  Shared LAN Directory  E-Mail  FTP Site SYNCLOG.PIM lists all the changes in order DATA.INI has pointers into synclog.pim that say what has and has not synchronized. SYNCLOG.PIM lists all the changes in order DATA.INI has pointers into synclog.pim that say what has and has not synchronized. Example of a file name: 1st 4 digits are a seq. Number, last are the Workgroup ID

5. Typical Workgroup Commence Server PC Client A Client B Client C

6. Typical Workgroup Changes are made to the client database on Client A Commence Server PC Client A Client B Client C

7. Typical Workgroup Changes are copied to the Server database via synchronization files (packets) Commence Server PC Client A Client B Client C

8. Typical Workgroup Server copies all changes it received and communicates them to the other client databases via synchronization files Commence Server PC Client A Client B Client C

9. Changes between 3.x and 4.0/2000/RM Version 3.xVersion 4.0/2000/RM  Pointer into SYNCLOG.PIM maintained by ‘local’  Pointer into SYNCLOG.PIM maintained by ‘remote’  If sync packet lost/bad, data lost  If sync packet lost/bad, data will be re-sent  DATA.INI only refers to ‘local’  DATA.INI refers to ‘local’ and ‘remote’

10. DATA.INI  Commence 3.x  Backup#= ; ; - User ID the of the user associated with the backup line. - Workgroup ID (in decimal), can be determined by selecting Help-System Information- Workgroup Information (in Hex). Each client has a unique number. - A number. Represents a pointer into the SYNCLOG.PIM file of the next change to synchronize out. All numbers should be in the same range.

11. DATA.INI  Commence 4.0/2000/RM  Backup#= ; ; ; ; - Same as 3.x. - Same as 3.x, except the number is displayed in Hex. - A number. Represents a pointer into the SYNCLOG.PIM file of the next change to synchronize out. All numbers should be in the same range.

12. DATA.INI  Commence 4.0/2000/RM  Backup#= ; ; ; ; - A number. Represents a pointer into the SYNCLOG.PIM file of the ‘remote’ of the next change to synchronize out. It also represents the last changes that the ‘local’ received successfully. - Current synchronization status, i.e. sending a sync file or receiving one.

13. Client Synchronization - General

14. Server Synchronization-General

15. Client Sync Out Process A

16. Server Sync In Process C

17. Server Sync Out Process D

18. Client Sync In Process B

19. DATA.INI Settings The following settings affect workgroups and workgroup synchronization: [Other Options] MessageLogUpdate=# (in sec. default=10) MessageLogMin=# (in KB, when active.log reaches max, it is truncated to this value) MessageLogMax=# (in KB, the maximum the active.log file can reach before truncating, default=64)

20. [Workgroup] Enable=# (possible values: 0 or blankstandalone database 1remote database 2base database 3client database 4server database Note: Do NOT change these numbers manually!) Server=TRUE/FALSE DATA.INI Settings

21. SharedDBID=# (The ID of the database. All clients of this database must have the same ID. Note: Do NOT change this number manually!) NumEntries=# (The number of backup lines, including the lines for remote databases.) RemoteCount=# (The number of remote databases)

22. DATA.INI Settings MaxPackets=# (Only valid at server. The maximum number of sync packets the server will process in one sync interval. Default=50, valid values=1-32,000. If set to 0, will not synchronize. SyncValid=list of valid backup line numbers. (When a client is registered or removed, this line is updated. Typically, this line is edited if a SYNCLOG.PIM file is very large.)

23. DATA.INI Settings Backup#= ; ; ; ;  Name and WID are the User ID and the Workgroup ID of the user the backup line is for.  is the pointer into the local SYNCLOG.PIM file. It points to the next change that needs to synchronize out.  is the pointer into the remote SYNCLOG.PIM file. It points to the location where the local database last successfully synced in.

24. DATA.INI Settings Backup#= ; ; ; ;  a number that shows the current sync status. -1An error occurred when converting from the 3.x format to 4.0/2000/RM 0Only used when convert from 3.x to 4.0/2000/RM 1No activity. 2Local is sending a sync file to the remote 3Local is receiving a sync file from the remote 4Local is waiting for a response from the remote 5Local is reading/processing a sync file from the remote 6Local is writing a sync file for the remote

25. Syncing Tidbits  Server will only sync out in response to a request from the client.  The Server will NEVER accept a complete sync from a client.  Sync packets are created every sync interval, even if no changes occurred.

26. Syncing Tidbits  Data/Definitions sync out/in a particular order:  Sync In: Administration Files Categories Items Connection Definitions Connection Data Detail Forms Color Codes Letter Templates Views Desktops Agents

27. Syncing Tidbits  Data/Definitions sync out/in a particular order:  Sync Out (Complete): Administration Files Categories Connection Definitions Items Connection Data Detail Forms Color Codes Letter Templates Views Desktops Agents

28. Syncing Tidbits  Data/Definitions sync out/in a particular order:  Sync Out (Incremental): Administration Files Items Connection Data Categories Connection Definitions Detail Forms Color Codes Letter Templates Views Desktops Agents

29. Troubleshooting Basic Process: 1.Check the ATIVE.LOG or Message Log for errors. 2.Make sure you are looking at the right place. The Message Log may say the error occurred at the server or at the client. 3.Determine what process was occurring when the error occurred (syncing out/in at the client/server).

30. Troubleshooting Basic Process: 4.If you can determine the process, locate it on the flowchart. Any possible errors here? 5.If still not sure, gather more information by turning on trace /trace /trace=2 for full details 6.Recreate the problem and look at the log file.

31. Troubleshooting Basic Process: 7.Check the Technical Notes on Admineng (TN4310) and Commence Internal Status (TN3312) errors. It’s a learning process.

32. Troubleshooting Common problem: Shrinking sync log file. (UINFO-WG-2345) Solution: Remove any unused clients, check and fix data.ini.

33. Troublshooting [Workgroup] Enable=4 SyncValid=1 2 3 4 Backup1=user1;0X6501;34567;456;1 Backup2=user1;0X6601;0;0;1 Backup3=user1;0X6701;34500;234;1 Backup4=user1;0X6801;2000;100;1  Edit SyncValid= and remove 2, 4

34. Troubleshooting  CLIROLE.CPP: 207: 15.07.97: 19:16: Commence internal status information - (ERR-DENG-2301)  CLIROLE.CPP: 959: 15.07.97: 19:16: Contact your administrator: This client failed while syncing in from the server. Check the Message Log for information about the problem. Auto-syncing will be disabled until the problem is resolved. (TECH-WG)  CLIROLE.CPP: 692: 15.07.97: 19:16: Contact your administrator: This server failed while syncing out to the client. Check the Message Log for information about the problem. Auto-syncing will be disabled until the problem is resolved. (TECH-WG) These messages don’t mean anything without the previous portions of the Message Log or ACTIVE.LOG. They just say that there was some problem.

35. Troubleshooting-Example 1 15.07.97: 19:16: Copying In Connection: Contact Log Created by Employees (UINFO-WG) 15.07.97: 19:16: Leaving SyncInComplete. (UINFO-WG) 15.07.97: 19:16: Leaving SyncIn. (UINFO-WG) 15.07.97: 19:16: Auto-sync error: Unknown error. Please call Tech Support. (UINFO-WG-2022) CLIROLE.CPP: 959: 15.07.97: 19:16: Contact your administrator: This client failed while syncing in from the server. Check the Message Log for information about the problem. Auto-syncing will be disabled until the problem is resolved. (TECH-WG) CLIROLE.CPP: 608: 15.07.97: 19:16: Commence internal status information - (ERR-DENG-2301) CLIROLE.CPP: 692: 15.07.97: 19:16: Contact your administrator: This client failed while syncing out to the server. Check the Message Log for information about the problem. Auto-syncing will be disabled until the problem is resolved. (TECH-WG) CLIROLE.CPP: 207: 15.07.97: 19:16: Commence internal status information - (ERR-DENG-2301)

36. Troubleshooting-Example 2 4/07/97: 10:24: Copying Out Connection Data: Help Desk Call Allocated To Person (UINFO-WG) vardata.c: 2094: 4/07/97: 10:27: Commence internal status information - (ERR-DENG-2301) 4/07/97: 10:27: Leaving SyncOutComplete. (UINFO-WG) 4/07/97: 10:27: Auto-sync error: ÐgfgfZgfzgÇBüÿgzgzgÇBM (UINFO-WG- 2022) 4/07/97: 10:27: Compressing sync data. (UINFO-WG) 4/07/97: 10:27: Sending sync command. (UINFO-WG) 4/07/97: 10:27: Receiving sync data. (UINFO-WG) 4/07/97: 10:27: Entering SyncOut. (UINFO-WG) 4/07/97: 10:27: Leaving SyncOut. (UINFO-WG) 4/07/97: 10:27: Auto-sync out for: BG (UINFO-WG)  Result: Bad connection data.

37. xfershar.c: 893: Copying Out Connection Data: Printing Job Has Status Print Job Status (UINFO-WG) xfershar.c: 893: Copying Out Connection Data: Help Desk Call Relates to Resource (UINFO-WG) vardata.c: 2094: Commence internal status information - (ERR-DENG-2301) xferout2.c: 550: Commence internal status information (errorno=29) - (INT-DENG- 2019) xferout2.c: 775: Bad return (INT-IMPORT-2261) sync.c: 925: Commence internal status information - (INT-WG-2301) sync.c: 970: Leaving SyncOutComplete. (UINFO-WG) syncconn.c: 648: Auto-sync error: fRè?ìfÐgfgfZgfzgÇBüÿgzgzgÇBM (UINFO-WG- 2022) syncconn.c: 649: SyncOut failed in ScanFiles. (INT-WG) syncconn.c: 1511: Compressing sync data. (UINFO-WG) syncconn.c: 1526: Sending sync command. (UINFO-WG)  Result: Bad connection data. Troubleshooting-Example 2

38. asimp.c: 1582: 06/07/1997: 3:27PM: Record 1, Field 6 of file C:\WINDOWS\TEMP\~SLX215A\CLS00002.DBF does not map to a field, and Commence cannot continue importing. (TECH-IMPORT-2305)  Result: Category definitions are not the same. Troubleshooting-Example 3

39. Copying Out Category: Person(UNINFO-WG) Copying Out View: People (UINFO-WG) Leaving SyncOut. (UINFO-WG) Auto-Sync out for: Sue (UINFO-WG) Compressing sync data (UNIFO-WG) Sending sync data (UINFO-WG) syncconn.c: 708: ADMINENG.DLL encountered an error: 25, 0, 0x73, 1424  Result: Syncing with removed user Troubleshooting-Example 4

40. shar.c: 893: Copying Out Letter Template: Expenses (UINFO-WG) s.c: 72: Commence internal status information (errorno=10) (INT-DENG- 2019) s.c: 72: Commence internal status information (errorno=12) (INT-DENG- 2019)  Result: Problems with letter templates. Troubleshooting-Example 5

41. syncconn.c: 1290: Compressing sync data (UINFO-WG) syncconn.c: 1290: Sending sync data (UINFO-WG) syncconn.c: 1962: ADMINENG.DLL encountered an error: 7, 16430, 0xBA, 1472, (000100ba.dwn). (ERR-WG-2339)  Result: Network permissions not properly set. Troubleshooting-Example 6

42. syncconn.c: 1962: ADMINENG.DLL encountered an error: 32, 15, 0x3, 4562, (). (ERR-WG-2339)  Result: Problem logging into mail program. Troubleshooting-Example 7

43. XFERSHAR.cpp: 1101: 6/10/97: 12:02PM: Copying In Category: Product Service (UINFO-WG) DISKIO.cpp: 987: 6/10/97: 12:02PM: Open: objects.piW, FH = 26 (PERF- IO-2190) DISKIO.cpp: 987: 6/10/97: 12:02PM: Open: thid.pim, FH = 26 (PERF-IO- 2190) SYNCTHID.cpp: 423: 6/10/97: 12:02PM: Commence internal status information (errorno=29) - (INT-DENG-2019) SYNCTHID.cpp: 102: 6/10/97: 12:02PM: Commence internal status information - (INT-WG-2301)  Result: Bad internal IDs. Must send data to Technical Support. Troubleshooting-Example 8

44. Commence Corporation