I'm working with a Sage 50 file that is shared using Remote Share. This file began freezing Sage when performing certain actions.
I unshared the file and ran the DB tools against it (How to run the Advanced Database Check (ADC) (sage.com).
Option 2: I attempted to run an advanced check and repair but the tool could not verify the file. I attempted to run a basic check and the tool flagged the file as corrupt, but when I told it to run a repair it claims it's not a valid Sage 50 company file.
Option 3: I ran an advanced check and repair; the tool found no issues. I ran the advanced check and repair a second time, this time it claimed to find corruption. When trying to repair, the tool claims it's not a valid Sage 50 company file. I ran it a third time; the tool claimed it found no issues. A fourth run had the same results as the third run.
We have a file system backup of the folder location housing the Sage files from before the freezing began, but no Sage back up. Typically, in scenarios where Sage Remote has not been enabled, I am able to restore the SAI and SAJ file/folder from the backup and open it up.
When I go to open that restored backup, it complains because the backup was taken when Sage Remote was enabled, and now its disabled from the troubleshooting. If we re-enable Remote form the corrupted file, then open the backup, Sage Remote sync's the latest changes and introduces the corruption onto the restored file.
The backup file will not open without an internet connection due to its reliance on Sage remote.
What are my options for restoring this backup without syncing the corruption from Remote?
