Eventlog
No edit summary
No edit summary
Line 10: Line 10:
# Navigate/expand to the following key:  <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security  Tip: I set the permission on the whole EventLog node</code>
# Navigate/expand to the following key:  <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security  Tip: I set the permission on the whole EventLog node</code>
# Right click on this entry and select Permissions
# Right click on this entry and select Permissions
# Add the <code>Network Service</code> user
# Add the <code>Network Service</code> user, or to the user running the AppPool
# Give it Read permission
# Give it Read permission

Revision as of 08:22, 8 September 2020

MDrivenServer will try and write exceptions to the eventlog.

The eventlog may be restricted for the user running the MDrivenServer process. If this is the case you will see notes in MDrivenServer logs that is unable to write to eventlog.

To fix you must allow the MDrivenServer process user access. Follow the solution here: https://stackoverflow.com/questions/1274018/system-security-securityexception-when-writing-to-event-log

  1. Open the Registry Editor:
    1. Select Start then Run
    2. Enter regedt32 or regedit
  2. Navigate/expand to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security Tip: I set the permission on the whole EventLog node
  3. Right click on this entry and select Permissions
  4. Add the Network Service user, or to the user running the AppPool
  5. Give it Read permission
This page was edited 69 days ago on 02/10/2024. What links here