This is one of the most common eConnect errors that I continue to see with Dynamics GP customers. It occurs when a new server is setup with eConnect, or when an integration is migrated to a new server where eConnect was just installed.
It is very simple to fix, but requires Local Admin rights on the machine running eConnect.
eConnect error:
Exception: 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: Security.
Resolution:
1. Identify the domain user account assigned to the eConnect windows service on the machine where eConnect is installed and the import is being run
2. Temporarily add that eConnect domain user account to the Local Administrators group on the machine
3. Re-run the eConnect integration. If the same errors occur again, run the import a second or third time. eConnect should finalize the Event Viewer configuration and the errors should go away.
4. Remove the eConnect domain user account to the Local Administrators group on the machine
Steve Endow is a Microsoft MVP in
Los Angeles. He works with Dynamics GP, Dynamics 365 Business Central, SQL
Server, .NET, Microsoft Flow, and PowerApps.
Does not work - I get the same error no matter how many times I run it.
ReplyDeleteWe're in process of replacing GP, but still need eConnect in the meantime. Ran into this same error after moving GP and eConnect to a new server. Performed the steps mentioned above and we're back in business. Good info as always, Steve!
ReplyDelete