Skip to content
logo Knowledgebase

Error: "An error has occurred in the script on this Page"

Created on  | Last modified on 

Summary

How to resolve the message "An error has occurred in the script on this Page" when opening Sage 50 Accounting.

Cause

  • The latest Service Release wasn’t installed
  • ActiveX controls blocked in Internet settings
  • Not installed in the Program Files (x86) directory on a 64-bit computer
  • Invalid program path files
  • Damaged or incomplete installation
  • User Account Control (UAC) settings

Resolution

1. Install the latest Service Release

  1. Open Sage 50—U.S. Edition.
  2. Select Services, Check for Updates, and then select Check Now.
  3. Select Download.
  4. Close Sage.
  5. Service Release will now install.
  6. Verify you get no errors when opening Sage.

2. Turn off Sage Advisor settings

  1. Open Sage 50.
  2. Select Help, Sage Advisor, Settings.
  3. Uncheck all the boxes and click OK.
  4. Close Sage for the changes to take effect.
  5. Open Sage.
  6. Open a screen from the Maintain menu and verify you no longer get an error.

3. Make sure Sage 50 installed to the right directory

  1. If you have a 64-bit computer, follow the below steps.
    • Use this Windows FAQ to see if you have a 32-bit or 64-bit system
    • If you have a 32-bit computer, skip to the next section
  2. Check the current program path.
    •  EXAMPLE: PROGRAMPATH=C:\PROGRA~2\Sage\PEACHT~1\ 
  3. If your program path doesn’t look similar to the sample above, uninstall Sage 50.
  4. Reinstall the program, being careful to select the Program Files (x86) directory for the program files.

4. Repair Sage 50

  1. Close Sage.
  2. Browse to the program path.
  3. Rename the PTToday folder to OLDPTToday.
  4. Rename the ProductServices folder to OLDProductServices.
  5. Run Repair on Sage 50.
  6. Disable any antivirus and reinstall the latest Service Release.
  7. Verify Sage 50 opens without error.

6. Disable User Account Control (UAC)

  1. Disable User Account Control (UAC).
  2. Verify you no longer receive the error and that you can pay multiple employees.

7. Rename UserPref.dat

Rename UserPref.dat.

If you’re also seeing the error "Assertion Failed: System.IO.FileLoadException: Retrieving the COM class factory for component with CLSID {22743F12-6056-4120-A3FE-98200361EF91} failed due to the following error: 80131040." after going through the Script Error, refer to Error: "Assertion Failed, Abort, Retry, Ignore" when opening.

 

Need more help?

Chat now