Update Troubleshooting
Update Process
-
An error occurred during the move data process -115 - Files being overwritten are open indicating users are in the system. Make sure all users are out and all files are closed.
-
Btrieve Error 46 - a file being updated is an old 16 bit Btrieve format and needs to be rebuilt using the Rebuild Utility
Errors Updating to 2025.1
Here are some problems we have seen with 2025.1:
- During the DDF task, you get an error that there is already a database for a company but the path is wrong. This can happen if the path is actually wrong or if you defined the database using a UNC path that happens to point to the correct folder. Either way, you can just delete the database in the Pervasive/Zen control center and run the update again. It will create it pointing to the correct folder. Deleting a database in Control Center does not delete any data files. If you are using any third party software that connects to the database(s) with ODBC, verify which database your software is configured to connect to because you might need to change it.
- An error occurs in the record size check task. This is rare, but typically indicates there is a problem with your existing dictionary and we might need to manually fix it before you can retry the update.
- Patch downloads fail. We added an option to skip patching during the update installation if this does occur since this step isn’t absolutely necessary.
- (Usually in the DDF task) an error like “the key number parameter is invalid” when trying to fix/create an index. This might indicate something wrong with the data file itself or your dictionary. We probably need to look at the files and find the specific problem.
Using the System After the Update
- Updating to newer runtime. Please restart Evo-ERP - If you repeatedly get this message on a workstation, manually copy the EVOERP.EXE and TP7RUNTIME.EXE from the server folder to the local ISTS folder.