Users are getting an error message “Mfgsys.exe has stopped working” when they try to add a Calendar Exception in Resource Group Maintenance. We tried clearing cache, reinstalling Epicor and enabling compatibility mode without success. There are no personalizations that we can see on this screen but we may just do a purge all personalizations if needed. This is happening on a Windows 10 PC client.
Can you successfully “add a Calendar Exception in Resource Group Maintenance” on a different Windows machine? If you open Resource Group Maintenance in Customization mode are you using the Base Form or is there a Customization on this Form? Maybe try using the Base Form and see if it works? Any BPMs that might be triggering?
There is no BPM or customization on the form. I would have expected the error to happen as the user logs on each time. Thinking it could be related to Windows 10 but we’ll have to test on another Windows machine.
We run the E9 Client on all Windows 10 machines here and (fingers crossed) we haven’t run into any problems like this…could it be the .NET version you have installed on this particular machine? Do you have the right .NET version installed for the E9 client? Just grasping at straws here to try to help… 
You’re running E9 on Windows 10 with no problems? Hmm, I thought that wasn’t supposed to work. I’ve been avoiding Windows 10 like the plague for that reason. Luckily our agency hasn’t really been prepared for 10 either (AD has to get elevated, blah blah blah) but they’re working on getting that done.
Any tips?
Heather,
Try deleting the ch files under this folder and sub folders. I worked for Win 7 and 8
C:\Users\yourusername\AppData\Roaming\Microsoft\CLR Security Config
Tom
1 Like
Tom’s solution worked for us on Windows 10 also. The two paths and files we check and delete are:
file security.config.cch under C:\Users%USERNAME%\AppData\Roaming\Microsoft\CLR Secrity Config\v2.0.50727.312
file(s) *.cch under C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG
It doesn’t happen often, but when it does this fix worked every time.
Sue
1 Like