Before deep-diving into configuration surgery, attempt these high-probability solutions.

If the configuration file looks correct but loading still fails, the middle layer (database driver) is broken.

In modern versions of Windows (10/11), security restrictions often prevent the software from reading the configuration file correctly.

Steps:

Look for entries defining:

Example of a correct local config:

[DATABASE]
Type=LOCAL
Path=C:\TECDOC\Data\
Version=7.2
[SYSTEM]
LogLevel=ERROR

Example of a corrupted config:

[DATABASE]
Path=    (empty!)
Type=(gibberish symbols)
  • If using SQL: test the connection with a tool like DBeaver or sqlcmd.

    • Navigate to the expected data directory (e.g., C:\ProgramData\TecDoc\Data or a custom install path). Look for files with extensions like .dat, .tcd, .idx, or .sqlite. If you see none, the data is missing.