Full Network Resynchronization

Sometimes just using Request a Full Database Refresh isn't sufficient -- sometimes log files get corrupted or there is some issue where a workstation can't figure out how to get in sync.

If you're on version 10.0 or later, there's a one-step option that should work.  Otherwise, there's a quick manual version that may work, and then a last-resort full re-sync that may be required.

Important: All methods assume that the Master computer has the most correct / up-to-date information.  If not, that must be corrected first by copying the database from the most up-to-date client to the master.

The One-step Option

As of version 10.0, you can initiate a full resync in one step -- on the Master (server), make sure you're logged in as an Administrator and go to Maintenance / Network Functions / Initiate a Full Network Resynchronization.  After a couple conformation prompts, it will start the process, which is similar to the Quick Version (deletes log files on each computer and sends a full database).  This can be a lengthy process, and it's still recommended to start with the clients disconnected and then connect them one at a time.  However it should still work even if some are still connected.

The Quick Manual Version

Note: We recommend that you use this quick version only if you're using version 9.1 or 9.2.  Earlier versions do not have the enhancements needed for this to work most of the time.  This is also best used it you can first identify which client is causing the problem.

1. Shut down the master (server).

2. If the client is locked up, restart it.  Campground Master will fail when attempting to connect... continue (close the connection window) and log in as an Administrator.

3. Go to Maintenance / Network Functions / Network Setup.  Under the Diagnostic Options tab, click "Delete ALL log files", and confirm the prompt.

4. Close the client.

5. Restart the master (server).  Log in as an Administrator.

6. Go to Maintenance / Network Functions / Network Setup.  Under the Diagnostic Options tab, click "Delete ALL log files", and confirm the prompt.

7. Restart the client.  Once it connects, watch to see if it Requests a Full Database automatically.  If it does not, then go to Maintenance / Network Functions / Request a Full Database Refresh.

Assuming that was the only client with a synchronization problem, this will likely resolve the problem.  If not, then proceed to the full version below.

The Full version (last resort)

1. Shut down ALL clients.

2. On the master (server):

Make sure all orphans are fixed -- Maintenance / Database Maintenance / Report and repair Transactions orphaned from Reservations, and click the "Fix" button.  Repeat for the other 2 "Report and repair" functions.

Also go to View / Alerts, and if any are shown then highlight them all and select "Dismiss".

Go to Maintenance / Network Functions / Network Setup.    

 -- Under Timing, make sure the "Max delay between saves" is at least 600.  

 -- Under Diagnostic Options, uncheck the box "Show an alert...".  Also make sure the top 3 boxes ARE checked (Enabled/Auto/Force).  The "Request full database" box should NOT be checked.  

 -- Click "Delete ALL log files" (under Diagnostic Options), and confirm the prompt.

3. Under Maintenance / Program Options / Database, make sure "Automatically save the database..." is checked, and that "History Logging Enabled" is checked.

4. Make a backup from the master (Maintenance / Back up database), e.g to a thumb drive or somewhere you can access it easily.  IMPORTANT: Be sure to use a unique name for the backup file so there's no mistaking the correct file when you restore from it below, and pay attention to the "Save In" location to be sure it's going where you want it to go (e.g. the thumb drive).

5. Shut down the master so clients can't connect.

6. On each client:

Start Campground Master.  

If any alerts come up, use the "Close/ignore" option to close them.

Go to Maintenance / Network Functions / Network Setup.    

 -- Under Timing, make sure the "Max delay between saves" is at least 300.

 -- Under Diagnostic Options, uncheck the box "Show an alert...".  Also make sure the top 3 boxes ARE checked (Enabled/Auto/Force).  The "Request full database" box should NOT be checked.

 -- Click "Delete ALL log files" (under Diagnostic Options), and confirm the prompt.

Go to Maintenance / Restore from Backup, and restore from the backup you made above -- paying attention to the "Look In" location and the file name so you now that you're getting the correct file.

... Repeat for each client.

7. Once this is done on each client, restart the master.

That should guarantee they are in sync.  Start the master, and they should all connect immediately without a problem.

You might want to open the Networking Diagnostics window for awhile to make sure things are going smoothly.  Keep an eye out for any issues like re-sending things repeatedly, workstations disconnecting, sending a full database, etc...