Just a quick update: we were able to recreate the error in the Work Order Maintenance screen so it made things a bit easier to troubleshoot. I have tried the following with no results: .NET 4.0, 4.5.1  and 4.5.2 update, DEP disabled and UAC disabled.

The very last thing I tried was changing the compatibility mode on the module exe itself to windows xp sp3.. I was not able to recreate the error! Since we have multiple modules that are affected I am testing compatibility mode on businessdesktoploader.exe fingers crossed that this works! So much for 2013 being compatible with windows 7 or server 2008 r2!!

Nice job on the troubleshooting.

Nice job on the troubleshooting.

Thank you! I have a bad feeling about running the loader in compatibility mode and might have to do just the affected modules individually :/

so far they are MCZMB001.exe sozdj101.exe sozda101.exe mfzdb001.exe* mfzda001.exe mfzrv001.exe imzqk001.exe Imzmt001.exe pozda001.exe Apzdj001.exe

Monitoring the logs today...

Compatibility mode on desktoplauncher caused “Unable to create MAPI Session or log on to specified Mailbox” with e-invoicing.. So back to compatibility on individual exe's and case opened with Sage :/

What operating system was your Sage 500 client software running on just prior to this upgrade?

It was on server 2003 and windows 7 pro.. I was able to recreate the WO error on our Sage re-sellers machine which tells me this is a Sage issue and not specific to our environment. Since setting the WO compatibility mode we have not seen an error for WO maintenance on server 2008 r2 or windows 7 pro.