You’re offline. This is a read only version of the page.
18,265
Hello,
I am getting following error. I have added user in Admin Group and Event log security but still no luck.
Action: Service Create Current User Name: IIS APPPOOL\AHI_Integration_Pool Input parameters: Exception type: System.Security.SecurityException 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.
Any help on this is highly appreciable.
Thanks much
Sandip Jadhav
*This post is locked for comments
It sounds like you having been trying the same things
I would have. It is difficult without the full picture of what is running where and how they interact to suggest much more.
I think I would be getting process explorer out and logging around the exception to see what is really going on.
https://technet.microsoft.com/en-gb/sysinternals/bb795533.aspx
Tim.
Hi Tim,
Much appreciate for your reply. I am using .asmx webservices using eConnect to integrate data.
On Database Server where eConnect is installed--> under Application and Services Logs it shows Dexterity, Dynamics & eConnect.
On Database Server WebServices are working fine it return data too. But from application server it does not work and give above mention error.
I have added users in Admin Group as well as Reg Edit on EvenLog given full permission.
Any other thoughts will be highly appreciable.
Have you got an eConnect node in your Applications and Services Logs of event viewer of the machine running eConnect?
Where are you seeing the error, in an application that uses eConnect, i.e. where did you get the exception message from?
Almost always in my experience this message is an application trying to create an entry in an event log, but the event log source does not exist (for example Dexterity, Dynamics, eConnect are sources in screen shot). The process running does not have permission to create it either, so it has to raise an exception. Which I think is the same conclusion you have come to it you are adding permissions.
The user you granted admin to, you are certain it is the user under which the error is generated. For example if you call from one application via WCF to another and it is the remote app raising the error (thinking econnect window service user here) that remote app might be running under a different user context. You could try running process monitor as it might
After writing above response, I've Googled it, seems Steve has had similar issue and independently has come to the same conclusion:
https://dynamicsgpland.blogspot.co.uk/2015/04/dynamics-gp-2015-econnect-error-source.html
Tim.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (