
This issue is still under investigation and we have categorized this as an issue around Anti Virus. Our findings so far indicate this is an intermittent environmental issue affecting per user/machine. We have had various cases come through together over the past month with this issue.
We have had reports of fixes deployed by IT teams to various Anti Virus softwares or Security solutions . We need your help to appropriately report to us what the cause and fix was so we can update this guide with more information.
 CAUTION: Sage takes no responsibility for the following guidance, this has been provided as a goodwill gesture while this issue is still under investigation. It is up to you to test and resolve as Sage does not own or manage your environment. We will do our best to update this guide with cases we have had replies on to what has fixed it.
 CAUTION: Sage takes no responsibility for the following guidance, this has been provided as a goodwill gesture while this issue is still under investigation. It is up to you to test and resolve as Sage does not own or manage your environment. We will do our best to update this guide with cases we have had replies on to what has fixed it.
Here are a few potential ways to workaround the problem once it occurs.
 NOTE: Do not reset the user's desktop settings in an attempt to resolve this issue. This will not prevent the problem from recurring and will require the user to reconfigure their preferences.
 NOTE: Do not reset the user's desktop settings in an attempt to resolve this issue. This will not prevent the problem from recurring and will require the user to reconfigure their preferences.


 TIP: Have you identified the root cause? - Please click on the appropriate link for more information about Root Cause, Environmental and Intermittent Issues.
 TIP: Have you identified the root cause? - Please click on the appropriate link for more information about Root Cause, Environmental and Intermittent Issues. 
 NOTE: Sage takes no responsibility for the following guidance, this has been provided as a goodwill gesture while this issue is still under investigation. It is up to you to test and resolve as Sage does not own or manage your environment. We will do our best to update this guide with cases we have had replies on to what has fixed it.
 NOTE: Sage takes no responsibility for the following guidance, this has been provided as a goodwill gesture while this issue is still under investigation. It is up to you to test and resolve as Sage does not own or manage your environment. We will do our best to update this guide with cases we have had replies on to what has fixed it.
Some Business Partners have added the following directories to their Anti Virus exception list after removing the Sage 200 client install by following this guide and then reinstall.
C:\Users\*\AppData\Local\Sage
C:\Users\*\AppData\Roaming\Sage
We have seen some instances of this issue on sites where they use All -in-one Security software rather than standalone antivirus software.The below exclusions are recommended to supplement the Antivirus advice above .
Please refer to the vendors help files for specific advice .
C:\Users\*\AppData\Local\Sage\Sage200\Desktop\Sage.MMS.Desktop.Common.Resources.dll
C:\Users\*\AppData\Local\Apps\2.0\*\*\*\Sage.MMS.Launcher.Remote.exe
C:\Users\*\AppData\Local\Apps\2.0\*\*\*\Sage200Desktop.exe
C:\Users\*\AppData\Local\Sage
C:\Users\*\AppData\Roaming\Sage