Here are some common Sage 300 errors that customers have reported, along with instructions to resolve them.

“Cannot find program file. Windows defender and A4wcontainerXP.exe”

These errors appear if the ‘a4wContainerXP.exe‘ file located in the:

[Sage Programs]\Runtime directory is missing or corrupted.  On December 1, 2016, Microsoft Windows Defender began falsely detecting the a4wContainerXP.exe file as “Trojan:Win23/Detplock”.

How to Resolve:

Before recovering the a4wContainerXP.exe file on PCs with MS Windows Defender installed, use Microsoft’s instructions to exclude the [Sage Programs]\Runtime folder from scanning, then restart the PC for the exclusion to take effect.

Check the MS Windows Defender, Quarantine for the file.  If it’s present, and the folder exclusion has been set, then restore the file.  If the file is not in the Quarantine then copy the a4wContainerXP.exe from a working computer that has the same installation and version of Sage 300.

If another copy of the file isn’t available, then a complete Repair of the Sage 300 installation should be run, followed by installation of the Product Update in use at the time of the error.

“Sage 300 UI Container has stopped working”

This message may occur on a Windows 2008 R2 or Windows 2012 server when printing reports to preview.  When you click on the drop-down arrow to View problem details, the following message is displayed:

Assertion failed!
Program: C:\Apps\Accpac\RUNTIME\A4WCONTAINERXP.EXE
File: repcmd.c
Line: 227
Expression: NULL == record->pCrystalObjectHandle

How to Resolve:

You can resolve this error by following the detailed steps in this Sage 300 knowledgebase article (#18397). If you continue to see the error after trying those steps, be sure to reboot the server and the workstation for changes to take effect, and then everything should work correctly.

“You do not have a license to use this product”

If you see this error when opening a company on a specific computer or with a specific Windows user, it’s due to a Windows user account having insufficient rights to the Sage 300 Shared Data directory.

How to Resolve:

1. Check Sage 300 Shared Data directory path in the registry, (Go to Start, Run, type regedit).

32-bit environments:

HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC International, Inc.\ACCPAC\Configuration

64-bit environments:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ACCPAC International, Inc.\ACCPAC\Configuration

2. Confirm this is the same location displayed in the registry from a workstation(s) that can open a company successfully.
3. Check the user permissions for the Sage 300 Shared Data directory. Windows user accounts must have full access to the folders and sub-folders (Sage recommends that Windows user accounts be part of the Power Users group).

Note: The above steps have resolved a majority of these issues. In some cases, there is a second registry key in the HKEY_CURRENT_– USER\Software\ACCPAC INTERNATIONAL, INC. that is causing the error.

Error: “Cannot access database (error=49153)” during login to an existing system.

The cause for this error is when the system is not bale to connect to the database.

How to Resolve:

1. Open Sage Database Setup and the Company and System Database Profiles. Verify what Data Source or Server name, Login ID and Database names are set.
   
   
2. Open the 32-bit version of ODBC Data Source Administrator, either from Control Panel > Administrative Tools > Data Sources (ODBC), or from C:\Windows\SysWOW64\odbcad32.exe on 64-bit PCs.On the System DSNs tab find the Data Source name or Server name (if Server name is used a 32 is appended to it).Confirm the name of the SQL server in the DSN entry. Enter the User ID and password in the SQL Authentication, and confirm that the remaining settings are left as default.Test the database connectivity from the DSN.
   
   
   1. If the above test failed, then in a Windows Command Prompt (cmd.exe) ping the server name to test address resolution and connectivity.
      
      
   2. If the ping test is not successful, try using the IP address directly for the ping.
      
      
   3. If successful, enter the IP address in the DSN entry and test the database connectivity again.If the database connectivity is not successful with the IP address:
      • The User ID being used may not have permission to access the SQL Server.
      • The SQL Server may not be prepared to service the connection.
        
   4. If none of the above tests are successful, then continue troubleshooting using the article KB 33287: Error: “Cannot access database Error=49153” with a newly installed server to further test the SQL Server.

See Also: Sage 300 Invalid Database Specification

Error: “Can’t Create Control”

This error message occurs when opening some UI controls in Sage 300.

How to Resolve:

Can’t create control error message appears when screen resolution is low, and the window you want to open, is larger than the screen.

Error was observed with screen resolution of 800 x 600 dpi.

Increase the screen resolution to 1024 by 768 or greater to resolve the error.

Need Help with Sage 300 ERP (Accpac) or Other Errors?

Click to ask a question or get in touch with Acumen Information Systems – Sage 300 (Accpac) software support experts.