DFIC Error 500 - PracticeMaster and Tabs3 / TAS Files Are Not Synchronized

Last reviewed: 12/29/2011
Article ID: R10589

The information in this article applies to:

PracticeMaster Version 16, 15, 14, 12, 11 & 10
Tabs3 Version 16, 15, 14, 12, 11 & 10

SUMMARY

This error occurs when PracticeMaster and Tabs3/TAS data files do not match. The synchronization checks all files and fields that are integrated between PracticeMaster and Tabs3 to ensure that the contents of the file and the field values match.

MORE INFORMATION

Known causes of this error include:

When PracticeMaster Premier or PracticeMaster Basic is installed in an existing Tabs3 program folder for the first time, none of the data from Tabs3 will be in the corresponding PracticeMaster data files. As a result, an error 500 will appear until the Synchronize PM & Tabs3/TAS program is run. This also applies to installing Tabs3 into an existing PracticeMaster program folder for the first time.
Restoring from a backup in one of the two programs and not in the other.
Restoring from mixed backups (i.e., restoring Tabs3 and PracticeMaster backups that were not made at the same time).
The field lengths for some of the PracticeMaster fields are different than the field lengths for the corresponding fields in Tabs3.
Certain types of data corruption can cause the error 500. For example, if the Data File Integrity Check in PracticeMaster and/or Tabs3 reports error code 26, 66 or 69, an error 500 will usually accompany these errors.

RESOLUTION

Note: If the error 500 resulted from installing PracticeMaster into an existing Tabs3 current working directory for the first time, or vice versa, complete the steps in the Software was Recently Installed section. Then, simply follow the instructions listed below to synchronize the Tabs3 and PracticeMaster data. This will resolve the error.

The best solution is to restore PracticeMaster, Tabs3 and TAS (if applicable) from a backup. If restoring from a backup is not an option, run the Data File Integrity Check in whichever of the two programs has not yet had it run. In both PracticeMaster and Tabs3, resolve any errors other than the error 500. For information on resolving other Data File Integrity Check errors, click here.

Once there are no Data File Integrity Check errors in PracticeMaster or Tabs3 other than the error 500, synchronize PracticeMaster and Tabs3.

To synchronize Tabs3 and PracticeMaster data:

In Tabs3, select Maintenance | Integration | Synchronize Tabs3 and PracticeMaster.
Click Yes and then OK to make the temporary backup. If you have data in PracticeMaster, make a backup in PracticeMaster also.
Leave the default option to "Perform synchronization and prompt for a resolution to all conflicts" selected. It is also not necessary to change the setting for the "Convert Tabs3 archive records to PracticeMaster fee and cost records" option.
Click Start Synchronization, or for more information about the synchronization program, press F1.
Click Yes to begin the synchronization process.

There are four things that can happen at this point:

A message will be displayed indicating that changes were made. You will be asked if you want to view a list of changes. If this occurs, print the list of changes if desired and when you are finished, skip to step #6.
The Synchronization Exception Resolution window will appear. (Note: If this is a new PracticeMaster installation, call Technical Support before proceeding.) From this window you must select the program that contains the information you would like to keep. For example, if client 101 has an address of 200 Main Street in Tabs3 and an address of 600 Sycamore Drive in PracticeMaster, you must choose which system has the correct address. (Note: If the description field from a transaction is listed and both programs show a blank description, you must select PracticeMaster as the correct value.) You will then receive a message indicating that changes have been made and will be given the option to view the list of changes. Print the list if desired and once you are finished, skip to step #6.
A message indicating that no modifications were needed will be displayed. Click OK and proceed to step #6.
A message indicating that Synchronization had problems will be displayed. This usually occurs when you have restored a backup in one program but not the other. You must restore both programs to a backup from the same time, i.e., a nightly tape backup.

Select Utilities | Data File Integrity Check.
Click OK on the message that explains the Data File Integrity Check.
Click OK to start the process.

If the Tabs3 Data File Integrity Check completes with no errors, run the Data File Integrity Check in PracticeMaster. If you still have the error 500 in either program, contact our Technical Support Department.

Note: The Data File Integrity Check compares the mirrored records only until a discrepancy is detected. It is intended that the user will then run the Synchronization program and all discrepancies will be handled there.

Software was Recently Installed

If you have recently installed PracticeMaster in an existing Tabs3 program folder for the first time, or vice versa, first check to see if CMFEE or CMCOST exist in the current working directory. If so, erase PracticeMaster fee/cost data using the steps detailed below. These steps ensure that no duplicate fee or cost transactions are created during synchronization of Tabs3 and PracticeMaster data.

To erase PracticeMaster Fee/Cost data:

From the PracticeMaster menu, select Maintenance | File Maintenance.
Click Yes to back up your data files when prompted, and click OK when the backup completes.
Double-click Common Client Related Files and then double-click the Fee file.
On the Utility tab, select the Erase File Data option. Click Yes to confirm data deletion.
Repeat this process for the Cost file.

After completing the steps above, return to the steps for synchronizing Tabs3 and PracticeMaster data to finish the synchronization process and resolve the error 500.

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.