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
This page was created by Hans.karlsen on 2019-11-14. Last edited by Edgar on 2025-01-20.
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
- Open the Registry Editor:
- Select
StartthenRun - Enter
regedt32orregedit
- Select
- Navigate/expand to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security Tip: I set the permission on the whole EventLog node - Right click on this entry and select Permissions
- Add the
Network Serviceuser, or to the user running the AppPool - Give it Read permission