Resolving ProTax Database Mismatch errors in Lacerte

When working in Lacerte, users may encounter ProTax Database Mismatch error messages. These errors occur when Lacerte is no longer able to properly read the client database.

Troubleshooting

Reboot the affected computer

One of the simpliest solutions to test first is to reboot the computer. Sometimes, this error can result from a memory or access related issue. As a result, a quick reboot to clear out the memory can resolve this issue.

Reboot server if a network setup

Similar to rebooting the computer earlier, the memory or access issue could be due to a file stuck on the server. In these cases, all workstations would encounter the error with the impacted tax type. Rebooting the server can clear out the stuck files from memory, and resolve the issue.

Update Lacerte using WebSetup

Another common cause is when the Lacerte program isn't on the same version as the database. In these cases, run the WebSetup via the Windows Start menu or My Account to download the latest updates.

The most common cause of this is on a network setup that only share the datapath, not option paths. It can also occur for standalone setups that have separate standalone installations that have different updates.

Perform a Forced WebSetup

When a normal WebSetup does not resolve the issue, a Forced WebSetup is the next step to try. Normally WebSetup just updates the files that are out of date, but a Forced WebSetup will have it redownload all the program files for Lacerte.

The easiest method to do a Forced WebSetup is to use the Lacerte Tool Hub.

Check Firewall and Antivirus

Firewall and Antivirus programs could cause this messaging. They can intermittently block access to the database files while they scan them, which will prevent Lacerte from being able to read them properly. This can lead to Unable to Access Encrypted Database or the ProTax Database Mismatch errors. If the error occurs sporadically or keeps reappearing after it has been previously resolved, it is likely due to a third party program interferring, most commonly Antivirus or Firewall programs.

Test another Datapath

If the above items do not resolve the issue, then we have ruled out the Lacerte installation and most of the computer-related items as the cause. The next possibility is that there is a problem with the database itself.

If you are able to open Lacerte, you can access the Options and change your datapath to a new location such as the Demodata folder.

If you are not able to open Lacerte, you can open your Windows File Explorer and locate the data folder. Rename the folder by adding -old at the end, and then open Lacerte. This will create a new, empty database. Then you can attempt checking other tax types or Demodata.

If other databases are working fine, then the problem is with the database itself.

Running CLPack

You can use the CLPack program to attempt to repair the database. Much like the Forced WebSetup earlier, this can be found in the Lacerte Tool Hub as well. Depending on the type of damage in the database, its possible CLPack may encounter the same errors as Lacerte.

Restoring data from a backup

If we have confirmed the issue is with the database, but the CLPack program is unable to repair it, the only solution will be to restore the database from a backup.