The source was not found, but some or all of the event logs could not be searched

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

When running a SmartConnect map, an error appears stating
“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 and ensure that the new source name is unique. Inaccessible logs: Security.”

This message indicates that the account assigned to the eConnect service does not have administrative rights on the local machine.

To resolve this issue, follow these steps:

1. Go to Start → Run, type Services.msc, and press Enter.
2. In the Services window, locate “eConnect for Microsoft Dynamics 20XX Integration Service.”
3. Right-click the service, select Properties, then open the Log On tab and note the User ID being used.
4. Open Computer Management on the same machine and add the noted user to the local Administrators group.
5. Close SmartConnect completely and relaunch it by right-clicking the icon and selecting “Run as administrator.”
6. After that, run the same map again—SmartConnect and eConnect should now be able to write to the event log successfully.

If you’re still seeing an error message, it’s possible that the SmartConnect event logs are missing or there may be a permissions issue under Application and Services Logs in Event Viewer.

The error occurs because the SmartConnect event log hasn’t been created on the local machine. SmartConnect uses a Windows Event Log located under Application and Services Logs in Event Viewer, and this log is specific to each machine. When a map runs and encounters an error, SmartConnect tries to write that error to the event log. If the log doesn’t exist yet, you’ll see this error because the current user doesn’t have permission to create a new event log. To fix this, you need to run SmartConnect as an administrator one time. Right-click the SmartConnect shortcut/icon and select “Run as Administrator.” I understand that you’ve already done step 05—please verify it once, then run the same map again. This is important because the event log is only created when an error needs to be written. If the map runs successfully, no log is created.

For some reason, if the SmartConnect event logs have not been created, you can manually create them using PowerShell.

Tech Tuesday: Using PowerShell to Create SmartConnect Event Log

Have a question? Please reach out to us at support@eonesolutions.com