In Part 2, we will further explorer the Sage 300 ERP UI Container error. In Part 1, we saw that the error could appear while saving a Timecard, when using web deployment or when printing reports.
Let’s continue on where else you may encounter the pesky Sage 300 ERP UI Container error.
Exporting
This error has been known to appear when exporting reports and could be related to the Terminal Services environment. For example, the error only started to appear recently or appears intermittently. The former indicates a possible change in the Terminal Service environment that could be the cause. Seeing the latter indicates that something in the network environment is triggering the error. We recommend that you investigate what changes were made to the Terminal Services environment in order to troubleshoot this error.
Shortcut Keys
If you like to use shortcut keys like CTRL+C or CTRL+V then the “Sage 300 ERP UI Container has stopped
working” error has been known to crop up. To avoid the error, we recommend that you double-click or press the space bar on your keyboard in the Description field before using any shortcut keys. But we do have a hotfix that resolves this error: KB 32923 “Error: "UI container has stopped working" message when pressing shortcut keys in the Description field for any Sage 300 ERP screen”.
General Ledger
We also have a hotfix if you see this error when printing the GL Posting journal.
Accounts Payable
Entering AP invoices has been known to trigger the container error while in Sage 300 ERP 2012. The culprit seems to be using the keyboard combination of CTRL+C after inserting a new detail line and then clicking on the description field. Unfortunately, there is no fix or workaround for this but we will let you know via Twitter (@Sage300ERPCS) or on Sage City as soon as one is available.
Also in AP, this error occurs when positing AP or Payroll checks after printing the checks and just before posting is complete. The error could be caused by a corrupted user profile in Sage 300 ERP. We suggest that you, in the share data folder under the USER folder, rename the user associated with this issue. This may resolve the error.
Payroll
If you are using Canadian and US Payroll 6.0 and 7.0 in version 2012 then you may come across this error. Download the hotfix found in KB 28880: Error: "UI Container has stopped working" occurs entering Transaction History.
Sage CRM
Updating a Sage CRM integrated customer and seeing this error? It’s because a SSL certificate error was returned when accessing the Sage CRM WSDL (Web Services Descriptive Language) URL. This web service URL is called when making the connection to SageCRM database from Sage 300 ERP.
If your Sage CRM uses https or SSL to connect to the website, there needs to be a valid SSL certificate assigned to that URL. We recommend that your system administration fix issues related to SSL certificates in IIS.
Using Multiple Machines
If you are using multiple machines to print reports then the “Sage UI Container has stopped working” error has been known to appear. It seems that the issue is caused by other products that uses Crystal. This error can be resolved by following these steps:
- Un-install System Manager
- Rename the runtime folder
- Rename the \Business Objects\Common\3.5\bin folder
- Re-install System Manager
- Re-install the product updates
- Print report again
If you have any questions about the Sage 300 ERP UI Container errors that we’ve outlined in this blog and our previous one, let us know in the comments. Also, share with us your own troubleshooting tips.
