On an office with a networked on premise deployment, each client workstation would show the same error on launch:
Table does not exist.
File or directory does not exist.
File: C:\spartner\tmp\%username%\TMPRANGE.DB
Deleting the local/server C:\spartner\ TMP and PRIV folders (including BDE TMP nodes) did not resolve the issue as expected. Nor did updating, re-indexing and re-reading datafiles. Admin compatibility and AV (Eset) was also ruled out.
Eventually the launch error was resolved by implanting a known good copy of the tmprange.db file from a lab instance into each workstation's C:\spartner\tmp\%username%\ path.
RSS Feed
