The error message in the email indicated that the data load had failed, and the configuration file was exclusive. John's first thought was, "Not again!" This was not the first time the data load had failed, but it was the third time in the past month.
At its core, TecDoc is a complex, data-heavy software that relies on a configuration file to locate its essential databases. When it can't find these, you get this error. Based on extensive community reports and technical analysis, the primary causes include:
Look for flags like FileLocking = True or DatabaseMode = Shared . If your import utility requires exclusive interaction, ensure the mode parameters match your deployment documentation.
or configuration XML file (usually in the installation folder or C:\ProgramData\TecDoc Open it with Notepad and ensure the DatabasePath correctly points to your local or network data drive. The error message in the email indicated that
Often, a crashed session leaves a hidden process running that locks the database exclusively. Press Ctrl + Shift + Esc to open .
: Ensure the Data and Program folders have "Full Control" permissions for your current Windows user.
If found, (do not delete .ini or .xml configuration files). When it can't find these, you get this error
) exists in the database folder even when the program is closed, delete it manually to release the exclusive hold. Network Path Issues
The phrase in the error log specifically implies that a file lock conflict exists. The software throws this error primarily due to:
If the previous steps have not worked, you may be dealing with a deeper installation issue. A clean reinstallation is often the most effective solution. or configuration XML file (usually in the installation
: Ensure the section points to the exact absolute paths on your hard drive where the Data and Media folders are stored. Example structure:
does not run during your operating hours.