Sage 300 ERP UI Container has stopped working

Ran into the most bizarre errors on a client’s installation today. Existing single user Sage 300 2016 installation with SQL 2014 Express on a straightforward dekstop PC. Client updated to Windows 10 at some point and at some point after that printing stopped working. No knows for sure exactly when as printing is only used by the accountant once a month so I can’t ascertain if Windows 10 was the cause or an update or something else. Initially it was failing with “Sage 300 ERP UI Container has stopped working” with no further message. Event log showed MSVCR80.DLL as the faulting module.

Google searches only mentioned re-registering a4wcrinterop.dll by using regasm ( C:\Windows\Microsoft.NET\Framework\v4.0.30319\regasm /register [sage300runtimefolder]\a4wcrinterop.dll). However this is specific to receiving the “Assertion failed!” error message when printing Crystal reports. I tried it any way but without any joy.

I then uninstalled and reinstalled using “run as administrator” thinking that maybe the previous consultant had not done so and that this might resolve the issue. I then encountered “there was a problem registering the assembly a4wcrinterop.dll during installation” followed by “DLL function call crashed: ISRT._DotNetCoCreateObject” which prevented Sage 300 from being installed. Ok, so maybe it’s a .NET issue. I install .NET 3.5 via “Turn Windows features on or off” as it didn’t appear to be installed. I proceed yet again to install Sage 300 2016 and it finishes successfully. I press the final button on the final screen and two seconds later the following message pops up:

Unhandled Exception
Error Number: 0x80070002
Description: Could not load file or assembly ‘Microsoft.Web.Administration, version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 or one of it’s dependencies. The system cannot find the file specified.
Setup will now terminate.

???

Press Ok and another message pops up stating it’s uninstalling Sage 300 Financial Intelligence but actually just wipes the entire installation clean. Far faster than a normal uninstall would have too! To cut a long story short, the resolution was to enable “Internet Information Services (IIS) Web Management Tools” via Windows Features as per https://oasysadmin.com/2012/01/30/could-not-load-the-file-or-assembly-microsoft-web-administration-version7-0-0-0-when-running-the-exchange-management-console/ even though this is a desktop PC not running anything remotely relevant to IIS and not running any of the web screens or web deployment or portal features of Sage 300 2016. Just a straight forward General Ledger, Accounts Payable and Cashbook installation.

Hopefully this will help save somebody else a couple of hours of sheer frustration and hair pulling 🙂

Leave a Reply

Blogroll