Right-click the file, select , and ensure the Read-only attribute is unchecked.
Errors in the wc-dataload.xml or similar environment declaration files can cause the loader to fail and trigger a generic "check configuration" warning. 3. Troubleshooting Steps
: Specific OS security patches block legacy registry pathways or database communication schemas used by the offline tool. Direct Comparison of Common TecDoc Initialization Faults
: If the path is a network drive, ensure the drive is mapped and accessible. TecCom Wiki 2. Release "Exclusive" Database Locks Right-click the file, select , and ensure the
Here are proven solutions that go beyond standard recommendations.
If you are integrating TecDoc via a custom C# or Java application, ensure you are opening the configuration file with access, not exclusive.
: For networked or server-client TecDoc installations, the network path or mapped drive letter has changed or disconnected. Troubleshooting Steps : Specific OS security patches block
Ensure no other workstation is currently accessing the database during a core update or configuration change. If the data is on a server, restart the server’s file-sharing service to "force-release" any dead locks on the files. 5. Antivirus and Firewall Interference
The software needs to know exactly where your massive parts database is stored.
Open the configuration file in a text editor to ensure it contains the required DataloadBusinessObjectConfiguration or environment declarations. Release "Exclusive" Database Locks Here are proven solutions
Did this error occur directly after a or Windows update ?
This is a , not a data corruption issue. The error message is moderately clear (points to config file, mentions “exclusive”) but could be improved by naming the specific file or process causing the lock.
Another process (e.g., a background update, an abandoned session, or a secondary instance of TecDoc) is already using the configuration file.