web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Inaccessible logs error with inherited GP Add-in

(0) ShareShare
ReportReport
Posted on by 1,588

The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security

I am getting this error from a GP add-in I have inherited. My searches online have pointed to either a missing even source key or to permissions. My confusions about this scenario are : 

  • A search of the code for the use of the EventLog class finds nothing 
  • The add-in works in a production environment, I am getting this error in a new GP 2015 test environment
    • When I compare the permissions on the regkey for the Security event log between the production terminal server and the test terminal server they are the same. Or should I be looking at the database server? 
      • SYSTEM
      • Administrators
      • EventLog
  • As a GP Add-in, what user does not have the proper permissions to the Security event log? I assume it would be the Windows account for whomever is running GP. 

Very uncertain where to go with this next. Your help is greatly appreciated.

*This post is locked for comments

I have the same question (0)
  • steveendow Profile Picture
    2,281 on at

    Hi Chad,

    See my blog post about this error:

    dynamicsgpland.blogspot.com/.../dynamics-gp-2015-econnect-error-source.html

    In my experience, the error seems to only happen once, then magically goes away.

    I haven't been able to figure out the exact cause, but my guess is that eConnect needs to create its own event log, and that causes the error the first time, but then works fine afterwards.

    If you repeatedly get the error, let me know.

    Steve

  • chadbruels Profile Picture
    1,588 on at

    I am receiving the error multiple times - across multiple transactions in a single test, across multiple test attempts, and across multiple days.

    screencast.com/.../xH0jxBzN

    I have tried adding my Windows account and the eConnect service account to the Event Log Readers group of the local machine.

  • Verified answer
    steveendow Profile Picture
    2,281 on at

    Hi Chad,

    It's a long shot, but have you tried launching GP using Run As Administrator?

    Next step would be to try and temporarily add the eConnect service domain account to the Local Administrators group on the machine, to see if that makes any difference.

    Intriguing...

    Steve

  • chadbruels Profile Picture
    1,588 on at

    When GP was launched using Run As Administrator the error happened on the first transaction and then started creating normal eConnect errors for subsequent transactions. Also the error is not appearing any longer when launching GP normally.

  • steveendow Profile Picture
    2,281 on at

    Excellent, thanks for the update.  Glad that worked.  I would have never thought that Run As Admin would cause that.

    Steve

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans