This article outlines the steps to solve the problem of Sage 50 2018 unable to company files.
Sage 50 2018 is the latest edition of Sage 50 and has introduced many changes such as a new user interface; the facility to choose inventory items based on last activity date; adding a column for showing ‘Cleared Date’ in the ‘Check Register’ and ‘Cash Disbursement Journal’; and the option for including the link to payments in email invoices.
The inability to open company files in Sage 50 2018 might be manifest in any of the following ways:
- At the end of the conversion process (to Sage 50 2018), “Unable to open the company file.” An error message appears.
- The sample company can be opened.
- In the SAJ folder, the conversion log states “‘simply.tnxtpids’ doesn’t exist”.
- The conversion fails at one of the steps.
Sage 50 has been incorrectly installed or the required components have been blocked.
NOTE: Solving this issue requires expert-level knowledge of operating systems and so, only qualified IT personnel must proceed with this solution. Any incorrect modification of the Windows Registry can cause irreparable damage to the computer. Users must back up their data before completing the steps mentioned below.
1: Disabling anti-virus and real-time scanners
- Users must first disable the anti-virus software. If Microsoft Security Essentials is installed then, real-time protection and auto protection must be disabled.
- Next McAfee firewall and real-time scanning must be turned off.
- If any auto backup program is being used to back up the company data file it must be disabled and then the Windows ‘Event Viewer’ logs must be checked.
- For any warning on MySQL related to IPV6 users must check relevant resources.
- Once this is done users must right-click on the Sage icon and choose ‘Run as administrator’ and restart the conversion process. Once the conversion is completed, the security software must be re-enabled.
- If the files still can’t be opened users must refer to information on problems related to converting to a newer version of Sage 50.
2: Checking the errorlog.txt file
- In the data file location, the errorlog.txt file must be opened. If the file contains large blank portions or unreadable/unfamiliar characters, the file is corrupt and won’t convert and must be repaired.
- If the errorlog.txt file is alright, users must go to MySQL and then folders and look for the 2nd last version of XXXX. This might even be 3rd version XXXX. To verify, users must check the image found in ‘Additional Information’.
- Then, right-clicking on the Sage icon, ‘Run as administrator’ must be chosen, and it must be checked that the conversion can be started.
3: Verifying that there are no read-only or hidden file attributes
- Users must verify that the company file (SAJ folder and SAI file) doesn’t have these attributes. Next, right-click on both, select ‘Properties’. Now after selecting ‘Read-Only’ and ‘Hidden’, ‘Apply’ must be selected followed by deselecting ‘Read-Only’ and ‘Hidden’ and selecting ‘Apply’ again.
- These changes must be carried out in all subfolders inside the SAJ Folder.
- Now it must be checked if the sample company file can be converted. If the computer is on a network, a backup must be restored on the desktop and the company files converted locally.
4: UAC is blocking conversion
If this is the case relevant resources on company file not opening during conversion must be checked, following which it must be checked that the conversion can be started.
5: Checking the advanced database check log
- In an earlier version of Sage 50, ‘Maintenance’ must be chosen, followed by ‘Advanced Database Check’
- Next, opening Windows Explorer, users must go to ‘C:\Users\<username>\Documents\ My Documents\Simply\DbVerifier\Logs’ and the current numbered log file must be opened.
- If ‘tnxtpids’ doesn’t exist’ is seen in the conversion log users must try Solution 1 mentioned above and retry the conversion.
6: Checking if SAJ folder has duplicate files
- Duplicate files can be generated in several ways and so the naming might vary also
- The simply and mysql folder must also be checked to see that it doesn’t contain extra files and folders.
7: Locating and locally restoring a ‘Cabinet’ backup file
It must be checked that there’s no pre-existing conversion log in the SAJ folder. The conversion log is a time stamp .txt file that is created when conversion fails. Therefore, the data file might only be partially converted. While locating the backup, ideally users must try to find the file prior to that time.