Hi,

I'm encountering an issue whenever I try to run the sample applications provided with the SDK. I am receiving the following exception:

An unhandled exception of type 'System.Web.Services.Protocols.SoapException' occurred in system.web.services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Security.SecurityException: The event source ExceptionManagerInternalException does not exist and cannot be created with the current permissions. ---> System.Security.SecurityException: Requested registry access is not allowed.
at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)
at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName, Boolean useMutex)
at System.Diagnostics.EventLog.CreateEventSource(String source, String logName, String machineName)
at System.Diagnostics.EventLog.CreateEventSource(String source, String logName)
at Axosoft.Common.ExceptionManagement.DefaultPublisher.VerifyValidSource()
--- End of inner exception stack trace ---
at Axosoft.Common.ExceptionManagement.DefaultPublisher.VerifyValidSource()
at Axosoft.Common.ExceptionManagement.DefaultPublisher.Publish(Exception exception, NameValueCollection additionalInfo, NameValueCollection configSettings)
at Axosoft.Common.ExceptionManagement.ExceptionManager.PublishInternalException(Exception exception, NameValueCollection additionalInfo)
at Axosoft.Common.ExceptionManagement.ExceptionManager.Publish(Exception exception, NameValueCollection additionalInfo)
at Axosoft.OnTime.DataLayer.DataTools.GetConnectionString()
at Axosoft.OnTime.DataLayer.BaseDataClass..ctor()
at Axosoft.OnTime.DataLayer.Defects..ctor()
at OnTimeWebServices.DefectHandler.GetAllDefectsWithNames(Guid securityToken)
--- End of inner exception stack trace ---

Any help would be greatly appreciated.

thanks!

I have forwarded this to development for further research.

---

Michael Robinson
Axosoft Training Specialist

Click here to learn about Axosoft University!

I found a work around for the time being. I created a separate application pool under IIS 6.0 that uses the identity of the local system and moved the SDK to that application pool.

It looks like there may have been an issue with getting the connection string, which caused OnTime to try to publish the error, by default to the Event Log, which in turn caused the permission error.  Once you moved it to another app pool did everything work ok?

---

Dragan Marceta
www.Axosoft.com

Yes, everything is working OK with the SDK. However, the Web Edition is still using the default Application Pool without any problems at all...

We had the same issue with a fresh install of 6.1.3 on a new box today and upgrading to 6.1.4 or 2007 is not an option at this time.  The seperate application pool fixed the issue, but I wonder if a "permanent" solution has been identified?

--Scott

The issue is that when an error occurs in the SDK we try to write it out to the database, but the SDK is not setting up the connection properly, so the errors end up getting published to the event log.  The ASP.NET process does not have permission to access the event log so it ends up throwing the error you are seeing.  We will have to fix the SDK to properly set up the exception publisher to be able to write exceptions to the database.

---

Dan Suceava
http://www.axosoft.com