x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 133 subscribers
  • Views 719 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
756
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
TheRedMeadow

Revocation information for the security certificate for this site is not available

SUGGESTED
Posted By

We just installed a new endpoint protection and I've entered the file and folder exceptions from our previous endpoint protection however, all of our users are getting an error popup after logging into the Sage 300 Desktop. Once they've logged in and the welcome page pops up they have an error dialog box with "Revocation information for the security certificate for this site is not available. Do you want to proceed?"

When clicking on View Certificate it shows Issued by and our Endpoint's name. What am I missing when it comes to exceptions and whitelisting? Thanks.

Parents
  • 0

    Make sure you at least whitelist ACCPAC.EXE, A4WCONTAINERXP.EXE, A4WLICMGR.EXE, A4WVBA,EXE - essentially whitelist the entire Programs path if possible.  It sounds like the Endpoint protection is blocking ACCPAC.EXE because of how its signed.  If you get really stuck, remember the full answer will always be in the Event Viewer on the client attempting to launch Sage 300.  You should see an event for the error and an event showing the security app causing it right at the same time.  Also make sure you have any "behavior detection" or other similar tools turned off for the Programs path too.  Cheers...Tim

Reply
  • 0

    Make sure you at least whitelist ACCPAC.EXE, A4WCONTAINERXP.EXE, A4WLICMGR.EXE, A4WVBA,EXE - essentially whitelist the entire Programs path if possible.  It sounds like the Endpoint protection is blocking ACCPAC.EXE because of how its signed.  If you get really stuck, remember the full answer will always be in the Event Viewer on the client attempting to launch Sage 300.  You should see an event for the error and an event showing the security app causing it right at the same time.  Also make sure you have any "behavior detection" or other similar tools turned off for the Programs path too.  Cheers...Tim

Children
No Data

*Community Hub is the new name for Sage City