By Steve Endow
After upgrading an eConnect integration to Dynamics GP 2015, I received the following strange error message:
![]()
![]()
![]()
![]()
![]()
After upgrading an eConnect integration to Dynamics GP 2015, I received the following strange error message:
Exception type:Microsoft.Dynamics.GP.eConnect.eConnectException
Exception message: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.
Stack Trace: at Microsoft.Dynamics.GP.eConnect.ServiceProxy.CreateTransactionEntity(String connectionString, String xml) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.EntityImportImplementation(String connectionString, String sXML, Boolean isTransaction) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.ProcessEntityImport(String connectionString, String sXML, Boolean isTransaction) at Microsoft.Dynamics.GP.eConnect.eConnectMethods.CreateTransactionEntity(String connectionString, String sXML)
That part that stood out was "Inaccessible logs: Security". This reminded me of some errors I've seen where an application is trying to write to a windows Event Log that doesn't exist, that it is unable to create, or that it doesn't have permissions to write to.
I looked all of the logs Windows Event viewer, but couldn't figure out what was causing the error.
After running the GP 2015 integration a few more times, I eventually received an error I did recognize.
Error Number = 936 Stored Procedure= taPMDistribution Error Description = Vendor number does not existNode Identifier Parameters: taPMDistribution
Once I fixed the vendor ID in my test data file, the integration ran fine and I didn't receive the strange "The source was not found" message again.
I then installed the integration on the customer's workstation, and once again, the "The source was not found" error message appeared. After a few more tests, we received a standard eConnect error message, fixed the data, and the integration ran fine.
My guess is that there is some type of issue with the eConnect 2015 install or the process that creates or writes to the eConnect event log when the first error is encountered. The error appears once, and then things get straightened out in the log, and subsequent errors are logged properly.
Since the error does go away and appears to be a one-time event, I believe that you can safely ignore this message. Unfortunately it is confusing for users, but if you remember to warn them in advance, or are able to recognize the error and explain the issue to users, it shouldn't be an issue.
And here's some GP geek trivia: Did anyone notice that the error message refers to "eConnect12"? Even though the internal version number for GP 2015 is version 14?
Steve Endow is a Microsoft MVP for Dynamics GP and a Dynamics GP Certified IT Professional in Los Angeles. He is the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.
