We’ve seen runtime errors come up a lot in Sage 300 ERP and a quick search in Sage 300 ERP’s Sage City forum, it seems a lot of you have too!
So for this week’s blog post, I thought it would be useful to troubleshoot some common runtime errors that you may encounter.
But before we do, let us define what is a runtime error?
According to Microsoft, a runtime error is a software or hardware problem that prevents a program from working correctly. Runtime errors might cause you to lose information in the file you're working on, cause errors in the file (corrupt the file) so you can't work with it, or prevent you from using a feature. Unlike stop errors, runtime errors don't typically cause Windows or a program to stop working.
This little bit of background might help explain why these errors are occurring.
Let’s start with this runtime error:
"This application has requested the Runtime to terminate it in an unusual way"
There are two ways you will encounter this error: 1) when logging in to a Sage 300 ERP database 2) when printing Financial Reports directly to printer. Both scenarios are Microsoft Visual C++ Runtime Library errors.
If you’ve seen this error in the first scenario, then it means you are using a Windows 7 computer to run workstation setup. The workaround would be to install System Manager on the local machine and update the registry path back to the server by following these steps:
- Install the application locally. Run the 300 ERP setup.exe and use the local drive for the program path: i.e. c:\Sage 300 ERP.
- Confirm you are able to login to the database.
- Go into the Windows Registry and change the Programs path back to the server:
- Go to Start, Run or in the Search field type regedit and press Enter
- For 32 bit environments:
HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC International, Inc.\ACCPAC\Configuration - For 64 bit environments:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ACCPAC International, Inc.\ACCPAC\Configuration
Before performing any of the above steps, ensure you’ve created a backup or seek the assistance of a qualified Sage Business Partner, network administrator or Sage Customer Support analyst if you are unsure of what to do.
Now if you see this error when trying to print Financial Reports directly to print, your Windows Event log may report an error on the WMIPrvse.exe process. Download Sage 300 ERP 2012 Product Update 3 or PU4 to resolve this error.
Another Runtime error is “Runtime error 429: ActiveX component can’t create object” when accessing Statement Designer. The cause of this is the accpacfrXXX.xla file (where "XXX" indicates the version of the file) may be missing as an add-in component in Microsoft Excel or there is insufficient access to that component.
This error can easily be resolved by changing the macro security settings in Excel to “Disable all macros without notification,” which can be changed in the Trust Center.
If you find that this didn’t resolve your issue then logon to the server with the Administrator account and attempt to run Statement Designer. If you still get the same error, this probably means that the accpacfrXXX.xla file may need to be added manually as an add-in component in Microsoft Excel. KB article 19640 “Error: "Runtime error 429: ActiveX component can't create object" when accessing Statement Designer” outlines the steps to follow to add this file manually.
And the last runtime error we will troubleshoot is “Warning: '13' A Runtime error has occurred. Format does not match."
This error occurs when entering report parameters in Sage Intelligence Report Viewer. The cause of this error was that the Korean language was being used as the Windows default input language. Unfortunately, at this time, Sage Intelligence does not support Korean as a Windows input language. Switch to a language that is supported and this error should disappear.
Seen other Runtime errors? Let us know in the comments below.
