One More Trick to Ease Your Sage CRM – 300 ERP Integration Woes

Fixing Sage CRM – 300 ERP Integration Issues

If I put my thinking cap on and really dwell on it, I’d say that the biggest problem users run into, when setting up their Sage CRM – Sage 300 ERP integration, is improper setup and use of a dedicated Windows User (generally I dub as “CRMWEB or SAGEWEB”) that is utilized to logon and run as service. Setting this user, directing Web Deployment to utilize it as an identity under which to run, and giving it maximum sharing and rights to all of the hubs and spokes related to integration has often been the shove in the back to send an environment tumbling down the hill to successful integration. For many complainants, based on a couple described symptoms, this has been my go-to resolution and 95% of the time it truly has been the cure-all.

So what about the other 5%? There is nothing worse that hanging my hat on a “guaranteed” fix that doesn’t resolve things when coupled with all of my other best practices (said best practices are here). To be specific, I was presented with a few different scenarios where, based on the configuration of the Sage CRM – Sage 300 Environments, everything “should” have worked just fine. However, it didn’t and problems included hung screens in Sage CRM when updating records linked to Sage 300 and users getting unceremoniously booted out of their Sage CRM session.

After some hunting and pecking and a number of trials and tribulations (insert third overused – by me – phrase here) we discovered the good news that a known issue in Windows Server 2008r2 was at the root cause of this. I honestly say “good news” as it’s (a) not a problem with the Sage apps and (b) has a simple work around. The problem is that, for whatever reason, the operating system does not want to run the a4wnetMgrService.exe and a4wnetsvHost.exe programs as “normal” WS08r2 programs and therefore we need to adjust its runtime Compatibility mode. To do so, follow these simple steps:

1. Navigate to C:Program Files (x86)Common FilesSageSage Accpac

2. Highlight and right-click “a4wnetMgrService.exe” then choose “Properties”.

3. When the “Properties” window appears, click the “Compatibility” tab and click the “Change settings for all users” button near the bottom.

4. When the “Change settings for all users” window appears, click the “Compatibility” tab and click the

5. In the “Compatibility Mode” box near the top, fill-in the checkbox labeled “Run this program in compatibility mode for:” and choose “Windows Server 2003 (Service Pack 1) in the dropdown and Apply and OK to Save.

6. Repeat steps 2-5 for a4wnetsvHost.exe as well.

I won’t go as far as to suggest that this will be the final article I’ll post on overcoming head-scratchers on Sage CRM – 300 Integration, but I do feel pretty good about this being another nice tool in hammering out a stable environment. If you have followed all of my other recommendations on setting up a stable integrated environment, and are still having problems, give the above a shot and then let me know how it goes. As always, feel free to drop me a post here, hit me up on twitter @AzambaDavid, or drop me an email via with any feedback on these issues or other Sage CRM – ERP integration questions or problems you may have.

Photo by David Haas



Are your Sage CRM and Sage 300 systems compatible?