SecurityException: The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: State.
The reason you are receiving this error is due to Microsoft locking out applications from making changes to the newly added State event log. There is only one way to resolve this, you must run the Registry Editor as a SYSTEM account to grant the PanatrackerGP application rights to modify the State event log. To do so, please follow the instructions below:
- Download [PsExec](https://docs.microsoft.com/en-us/sysinternals/downloads/psexec) from Microsoft Sysinternals.
- Unzip and extract the tool to a permanent folder (e.g., c:\tools)
- Open an [elevated or admin Command Prompt](https://www.winhelponline.com/blog/open-elevated-command-prompt-windows/) window.
- Start the Registry Editor under the SYSTEM account, type the following command, and press ENTER: c:\tools\psexec.exe -sid c:\windows\regedit.exe
- Navigate/expand the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\State
- Right click on this entry and select Permissions
- Add the user "IIS APPPOOL\PanatrackerGP" user and give user Full Control
Once these steps have been done, resubmit the transaction twice and the correct error should appear in the portal.
Related Articles
eConnect Errors that may be encountered when using PanatrackerGP
"Error 1189: taSopHdrRecalc - Payment total does not match deposits+payments" Error: Payment total does not match deposits+payments entered for the document This error usually occurs when the taSopHdrIvcInsertPre stored procedure has been modified. ...
Security Exception when writing to Event Log
Symptom The following message may occur during the submission of a transaction: System.Security.SecurityException: The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security Cause This scenario may occur ...
Set Device Name or ID
Each handheld device used with PanatrackerGP needs a unique name. Name devices based on their intended location or use — for example, "WHS1" for Warehouse 1. Complete the setup for all mobile computers as soon as you receive them. Steps Open the ...
Adding a New GP Company to PanatrackerGP
Overview To add a company to PanatrackerGP: Grant the Panatracker SQL login access to the company Download and run required scripts Create the company record on the PanatrackerGP portal and aim it at the proper database Create a profile that ties ...
Barcode read failed. Result: A0000023
Symptom "Barcode read failed. Result: A0000023" error message appears on the handheld. Cause The error is caused by a handheld application named DataWedge conflicting with PanatrackerGP. Solution Disable DataWedge via Settings Open the Start Menu on ...