workgroup synchronization commence corporation workgroup synchronization basics changes between...
TRANSCRIPT
Workgroup Synchronization
Commence Corporation
Workgroup Synchronization
BasicsChanges between 3.x and 4.0/2000/RMDetails of SynchronizationDATA.INI settings that affect
synchronizationTroubleshooting
General stepsExamples
The BasicsCommence keeps track of the changes
SYNCLOG.PIMDATA.INI
Changes copied to files0001006b.UP
Files are exchanged between the Clients and ServerShared LAN DirectoryE-MailFTP 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
Example of a file name: 1st 4 digits are a seq. Number, last are the Workgroup ID
Typical WorkgroupCommence Server PC
Client AClient B
Client C
Typical Workgroup
Changes are made to the client database on Client A
Commence Server PC
Client AClient B
Client C
Typical Workgroup
Changes are copied to the Server database via synchronization files (packets)
Commence Server PC
Client AClient B
Client C
Typical Workgroup
Server copies all changes it received and communicates them to the other client
databases via synchronization files
Commence Server PC
Client AClient B
Client C
Changes between 3.x and 4.0/2000/RM
Version 3.x Version 4.0/2000/RM Pointer into
SYNCLOG.PIMmaintained by ‘local’
Pointer intoSYNCLOG.PIMmaintained by‘remote’
If sync packetlost/bad, data lost
If sync packetlost/bad, data will bere-sent
DATA.INI only refersto ‘local’
DATA.INI refers to‘local’ and ‘remote’
DATA.INI
Commence 3.x Backup#=<Name>;<WID>;<Local>
• <Name> - User ID the of the user associated with the backup line.
• <WID> - Workgroup ID (in decimal), can be determined by selecting Help-System Information-Workgroup Information (in Hex). Each client has a unique number.
• <Local> - 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.
DATA.INI
Commence 4.0/2000/RM Backup#=<Name>;<WID>;<Local>;<Remote>;
<Status>• <Name> - Same as 3.x. • <WID> - Same as 3.x, except the number is
displayed in Hex.• <Local> - 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.
DATA.INI
Commence 4.0/2000/RM Backup#=<Name>;<WID>;<Local>;<Remote>;
<Status>• <Remote> - 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.
• <Status> - Current synchronization status, i.e. sending a sync file or receiving one.
Client Synchronization - GeneralSy nc interv al oc c urs
at c lilent
Sy nc Out Proc es sf or Client
A
Sy nc In Proc es sf or Client
B
More .DWN f ilesin WORKGRP orShared LA N dir?
no
y es
Wait f or nex t s y ncinterv al
Server Synchronization-GeneralSy nc interv al oc c urs
at s erv er
Sy nc In Proc es sf or Serv er
C
Sy nc Out Proc es sf or Client
D
More .UP f iles inWORKGRP or
s hared LA N dir?
no
y es Pac kets s y nc edin < Max Pac kets
(def ault=50)?
y es
no
Wait f or nex t s y ncinterv al
Client Sync Out
Process A
BeginA
Is <Loc al> < endpointer to
s ync log.pim?
# changes >Max LogsPerSync(def ault=16,000)?
y es , changes made
Copy f iles f or emptys ync pac ket to TEMP
Copy changes f rom<Loc al> to end of
s ync log.pim to TEMP
Copy MaxLogs PerSy ncc hanges to TEMP,
s tarting w ith <Local>
A ny errorsc opy ing out
data?
Delete TEMP f iles
A dd <Remote>number
A dd # of las t c hangec opied out <las t>
Compres s f iles intoSY NCWORK.TMP inWORKGRP direc tory
Copy nex t in order inWORKGRP dir to .TMP
in s hared LA N dir
Rename to .UP
A ny errorsc opy ing the f ile?
Delete .UP f ile inWORKGRP direc tory
Rename .UP f ile inWORKGRP direc tory
to .SER
Put error intoMes sage Log
Disable sy nc ing
Us erInterv ention:
Enable sy nc ing
EndA
no
no
no
no
y es
y es
y es
Set Mes s age Logicon to RED
Rename to .UP
BeginC
Copy f ile w ith low es ts eq. # to WORKGRP
direc tory as .TMP
Rename .UP f ile to.ERR
Sy nc c hanges intodatabas e
Unc ompres s s y ncpac ket to TEMP
A ny errorss y nc ing in data?
Modif y data.ini:-Replac e <Loc al> inbac kup line f or c lientw ith <Remote> f roms y nc pac ket-Replac e <Remote> inbac kup line f or c lientw ith <las t> f rom s y ncpac ket
Rename .UP to .ERR
Put error intoMes s age Log
Set ERROR to TRUE
EndC
no
no
y es
y es
A ny .UP f iles inWORKGRP or
s hared LA N dir?
y es
Rename to .UP
A ny errorsc opy ing the f ile?
Changesinc luded in s y nc
pac ket?
Delete TEMP f iles
Delete TEMP f iles
Delete .UP f ile f romWORKGRP direc tory
no
no
y es
Server Sync In Process
C
BeginD
Is <Loc al> < endpointer to
s y nc log.pim?
# c hanges >Max Logs PerSy nc(def ault=1600)?
y es , c hanges made
Copy f iles f or emptys y nc pac ket to TEMP
Copy c hanges f rom<Loc al> to end of
s y nc log.pim to TEMP
Copy Max Logs PerSy ncc hanges to TEMP,
s tarting w ith <Loc al>
A ny errorsc opy ing out
data?
Delete TEMP f iles
A dd <Remote>number
A dd # of las t c hangec opied out <las t>
Compres s f iles intoSY NCWORK.TMP inWORKGRP direc tory
Copy to .TMP ins hared LA N direc tory
Rename to .DWN
A ny errorsc opy ing the f ile?
Delete .DWN f ile inWORKGRP direc tory
Rename .DWN f ile inWORKGRP direc tory
to .SER
Put error intoMes s age Log
Set ERROR to TRUE
EndD
no
no
no no
y es
y es
y es
Is ERROR f als e?y es
Copy f iles f or errors y nc pac ket to TEMP
Clear ERROR
Rename to .DWN
Copy nex t in order inWORKGRP dir to .TMP
in s hared LA N dir
Server Sync Out
Process D
BeginB
Copy f ile w ith low es ts eq. # to WORKGRP
direc tory as .TMP
Rename .DWN f ile to.ERR
Sy nc c hanges intodatabas e
Unc ompres s s y ncpac ket to TEMP
A ny errorss y nc ing in data?
Modif y data.ini:-Replac e <Loc al> inbac kup line f or s erv erw ith <Remote> f roms y nc pac ket-Replac e <Remote> inbac kup line f or s erv erw ith <las t> f rom s y ncpac ket
Rename .DWN to.ERR
Put error intoMes s age Log/s et
ic on RED.
Dis able s y nc ing
EndB
no
no
y es
y es
A ny .DWN f iles inWORKGRP or
s hared LA N dir?
y es
Rename to .DWN
A ny errorsc opy ing the f ile?
Changesinc luded in s y nc
pac ket?
Delete TEMP f iles
Delete TEMP f iles
Delete .DWN f ile f romWORKGRP direc tory
no
no
y es
Us erinterv ention:
Enable s y nc ing
Error pac ket f roms erv er?
y es
no
Client Sync In Process
B
DATA.INI SettingsThe 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)
[Workgroup]
Enable=# (possible values: 0 or blank standalone database1 remote database2 base database3 client database4 server databaseNote: Do NOT change these numbers manually!)
Server=TRUE/FALSE
DATA.INI Settings
DATA.INI Settings
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)
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.)
DATA.INI Settings
Backup#=<Name>;<WID>;<Local>;<Remote>;<Status> Name and WID are the User ID and the
Workgroup ID of the user the backup line is for. <Local> is the pointer into the local
SYNCLOG.PIM file. It points to the next change that needs to synchronize out.
<Remote> is the pointer into the remote SYNCLOG.PIM file. It points to the location where the local database last successfully synced in.
DATA.INI SettingsBackup#=<Name>;<WID>;<Local>;<Remote>;
<Status> <Status> a number that shows the current sync status.
• -1 An error occurred when converting from the 3.x format to 4.0/2000/RM
• 0 Only used when convert from 3.x to 4.0/2000/RM
• 1 No activity.
• 2 Local is sending a sync file to the remote
• 3 Local is receiving a sync file from the remote
• 4 Local is waiting for a response from the remote
• 5 Local is reading/processing a sync file from the remote
• 6 Local is writing a sync file for the remote
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.
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
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
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
TroubleshootingBasic 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).
TroubleshootingBasic 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.
TroubleshootingBasic Process:
7. Check the Technical Notes on Admineng (TN4310) and Commence Internal Status (TN3312) errors.
It’s a learning process.
TroubleshootingCommon problem:
Shrinking sync log file. (UINFO-WG-2345)
Solution:
Remove any unused clients, check and fix data.ini.
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
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.
Troubleshooting-Example 115.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)
Troubleshooting-Example 24/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.
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
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
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
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
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
syncconn.c: 1962: ADMINENG.DLL encountered an error: 32, 15, 0x3, 4562, (). (ERR-WG-2339)
Result: Problem logging into mail program.
Troubleshooting-Example 7
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
Commence Corporation