Solution Properties
Solution ID:
224924950075795
Last Modified Date:
Thu Feb 09 14:45:59 UTC 2023
Taxonomy Path:
Category//Installation//Install full program//Latest version
Author:
[email protected]
Error: "Prepared failed with the following error: SY_SQLTranslateFailed:SYS" or "Errors were written to the SQL Translation Log while converting the SYS data to SQL" when migrating to Sage 100 Premium version
Description
Cause
  • Corrupt system file(s)
  • Old fields exist in Source Data Dictionary
Resolution
[BCB:1:Backup warning:ECB]

Option 1: Corrupt system file

  1. Browse to the ...MAS90\MAS_SYSTEM\ folder for the Target installation (Premium installation)
  2. Open 'SQL Data Translation of SYSTEM xxx.log' (xxx = 3 digit number) in Notepad.
  3. Select Edit, Find from the Toolbar
  4. Type: Unable to open Providex file
  5. Select Find Next
  6. Record the name of the system file located to the right of the message
    NOTE: If the file is SY_Metering, contact Sage 100 Customer Support for assistance.
  7. Log into your source installation of Sage 100
  8. Open Library Master, Utilities, Data File Display and Maintenance. Select OK to warning message
  9. Enter the system file name recorded above in the File Name field
  10. Press Enter or Tab
  11. If you receive message "Error opening 'file_name' file", you will need to restore the file from good backup or manually reinitialize it

Option 2: Bad Record in System File

  1. Browse to the ...MAS90\MAS_SYSTEM\ folder for the Target installation (Premium installation)
  2. Open 'SQL Data Translation of SYSTEM xxx.log' (xxx = 3 digit number) in Notepad.
  3. Select Edit, Find from the Toolbar
  4. Type: Error
  5. Record the name of the system file and record located to the right of the message
  6. Log into your source installation of Sage 100
  7. Open Library Master, Utilities, Data File Display and Maintenance. Select OK to warning message
  8. Enter the system file name recorded above in the File Name field
    NOTE: Make backup of file before proceeding to next step
  9. Locate and select record listed in Log
  10. Select Delete
  11. Repeat Steps 7-9 for any additional records

Option 3: Old field on table in Source Installation

  1. Browse to the ...MAS90\MAS_SYSTEM\ folder for the Target installation (Premium installation)
  2. Open 'SQL Data Translation of SYSTEM xxx.log' (xxx = 3 digit number) in Notepad.
  3. Select Edit, Find from the Toolbar
  4. Type: IOList compare - SQL:
  5. Record the name of the system file and field name
  6. Repeat steps 3-6 until you reach the end of the file
  7. Make a backup of your Source installation
  8. Contact Sage Support for additonal assistance

Option 4: Data Dictionary issue

  1. Browse to the ...MAS90\MAS_SYSTEM\ folder for the Target installation (Premium installation)
  2. Open 'SQL Data Translation of SYSTEM xxx.log' (xxx = 3 digit number) in Notepad.
  3. Select Edit, Find from the Toolbar
  4. Type: Unable to open SQL table
  5. Record the name of the system file and field name
  6. Repeat steps 3-5 until you reach the end of the file
  7. Contact Sage for assistance to verify none of the fields on the tables listed in the error log exceed 8000 characters in length.

[BCB:155:Chat 100 US:ECB]


Steps to duplicate
Related Solutions

How to erase or manually recreate data files using the Reinitialize Data Files utility
Error: "Errors were written to the SQL Translation Log"