Skip to content
logo Knowledgebase

Error: "Unable to open the company file." during or at the end of conversion

Created on  | Last modified on 


This article describes how to solve the error message "Unable to open the company file." at the end of or during the conversion process.


Option 1: Verify path location

  1. Ensure that when converting to a new version, all files are on a local drive.
    • If the file is on a network, copy the file locally
    • After conversion, copy the file back to the network
  2. Verify the file path is no more than 284 characters.

Option 2: Verify if the sample company opens

  1. Open the sample company. See How do I open the sample company?.
    • If the sample company does not open/convert, see The sample company does not open and try the conversion on your data file afterward, otherwise continue to Option 3.

Option 3: Verify if the SAJ folder contains duplicate files

  1. Open the .SAJ folder.
  2. Check for duplicates files names that contain:
    • ibdata1 (Copie de Joe conflit 2012-09-27) ibdata1 (joe's conflicted copy 2013-01-09)
    • accounts (1).frm, simplygroupmembership (2).frm, tbgtah01-1.frm or tbgtah01-2.frm;
    • Verify the simply and mysql folder does not have extra files or folders as well

Option 4: Restore a Backup

  1. Find and restore a Cabinet (.CAB) backup file locally
  2. It is recommended that you restore to a new .SAI file and .SAJ folder see How to restore from a backup.
  3. Make sure there is no conversion log pre-existing in the SAJ folder
    • Conversion log files are time stamped text files that are created when conversion failed, and the data file might be a partially converted
    • (i.e., 2017-06-28-16-20-55.txt - this file failed to convert at 2017 June 28 4pm
    • Find a file before this date and restore this

Option 5: Adjust Anti-virus and Real-Time Scanners

  1. Disable the antivirus
    • If you have more than one antivirus / security software, then uninstall them until you only have one left and disable it before conversion
    • If your computer is installed with Microsoft Security Essentials (or any other anti-virus), do the following:
      • Disable real-time protection
      • Disable auto protection
      • McAfee needs to have both real time scanning and the firewall
  2. Turn off the Firewall and Realtime Scanning.
  3. If your computer is using any auto backup software to backup company data file, disable it
  4. Verify the windows Event Viewer logs.
    • If you get a warning message for MySQL related to IPv6 see the article in the Related resources
  5. Right-click Sage 50 icon and Run as administrator.
  6. Start the conversion again.
  7. After file conversion, re-enable any security software.
  8. If some files still do not open, follow Unable to convert data to a newer version of Sage 50

Option 6: VPNs Running

  1. If no files will convert, including the sample company, disable any VPNs currently running and try again.

Option 7: Check errorlog.txt file

  1. Go to data file location and open the errorlog.txt file. If there are huge blank sections or sections with strange characters, then the file is corrupt and would not be converted. Please call Customer Support at 1-888-522-2722 to discuss repair options.
  2. If errorlog.txt seems fine, then go to mysql and simply folders; look up something about (2nd last version of XXXX)
    • Sometimes it can go up to 3rd version xxxx.

  3. Right-click Sage 50 icon and then select Run as administrator.
  4. Verify that you can now start the conversion.

Option 8: Verify that file attributes (no read-only or hidden)

  1. Verify that the company file (the SAJ folder and the SAI file) has not read-only and hidden attributes.
  2. Right-click on both and choose Properties.
  3. Check Read-Only and Hidden.
  4. Click Apply then Uncheck Read-Only and Hidden
  5. Click Apply again.
  6. Apply the changes to all subfolders in the SAJ folder.

Option 9: User Account Control is enabled

  1. See Method 2 in How to Run Sage 50 CA as Administrator

Option 10: Check Advanced Database Check log

  1. Select Maintenance, then Advanced Database Check in the previous version of Sage 50
  2. Open Windows Explorer.
  3. Browse to C:\Users\ \Documents\ My Documents\Simply\DbVerifier\Logs
  4. Open the latest numbered log file.
  5. Scroll to the end of the file.
  6. If conversion log says simply.tnxtpids' doesn't exist, then follow Option 3 above.
  7. Try the conversion again.

Chat with support