Access issue with old Microsoft.Practices.EnterpriseLibrary.Data when running from Azure App Service

Question

Access issue with old Microsoft.Practices.EnterpriseLibrary.Data when running from Azure App Service

Gola, Mariusz 45

Hi and thank you in advance.

We have an older asp.net 4.5 web form application we are migrating to Azure App Service. After deploying it to the app service we are getting the following error related to an older Microsoft.Practices.EnterpriseLibrary.Data, please see below.

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. at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly, Boolean wantToCreate) at System.Diagnostics.EventLog.SourceExists(String source, String machineName, Boolean wantToCreate) at System.Diagnostics.EventLogInternal.VerifyAndCreateSource(String sourceName, String currentMachineName) at System.Diagnostics.EventLogInternal.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData) at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type) at Microsoft.Practices.EnterpriseLibrary.Common.Instrumentation.PerformanceCounterInstances.ReportCounterFailure(String message) at Microsoft.Practices.EnterpriseLibrary.Common.Instrumentation.PerformanceCounterInstances..ctor(String categoryName, String counterName, Boolean createNewInstance) at Microsoft.Practices.EnterpriseLibrary.Common.Instrumentation.InstrumentedEvent.AddPerformanceCounter(String category, String[] counterNames, Boolean createNewInstance) at Microsoft.Practices.EnterpriseLibrary.Common.Instrumentation.InstrumentedEvent.Initialize(String counterCategory, String[] counterNames, Boolean createNewInstance, String eventLogSource, EventLogIdentifier[] eventIds) at Microsoft.Practices.EnterpriseLibrary.Common.Instrumentation.InstrumentedEvent..ctor(String counterCategory, String[] counterNames, Boolean createNewInstance, String eventLogSource, EventLogIdentifier[] eventIds) at Microsoft.Practices.EnterpriseLibrary.Data.Instrumentation.DataServiceEvent..ctor(String[] counterNames, EventLogIdentifier[] eventLogIds) at Microsoft.Practices.EnterpriseLibrary.Data.Instrumentation.DataConnectionFailedEvent..ctor(String[] counterNames, EventLogIdentifier[] eventLogIDs) at Microsoft.Practices.EnterpriseLibrary.Data.Instrumentation.DataConnectionFailedEvent..cctor()

From my findings there is a permissions issue of trying to write the logs within the Microsoft.Practices.EnterpriseLibrary.Data library. It works as expected running in VS2022 as admin.

Please advise,

Mariusz

Thank you

External resource

https://stackoverflow.com/questions/20389248/the-source-was-not-found-but-some-or-all-event-logs-could-not-be-searched-inac

Gola, Mariusz 45 Reputation points

2023-07-19T18:31:15.0233333+00:00

The actual call is happening within the Microsoft.Practices.EnterpriseLibrary.Common library which I don't have any control over.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-20T19:38:14.2033333+00:00

Mariusz, To better assist you on this, just to clarify, you have mentioned, "it works as expected running in VS2022 as admin.", does it work when running VS2022 ( as admin)?, but throws the error when not running VS2022 in elevated mode? Or does the deployment work fine on a different machine running VS2022, but not on another VS version?

Do the deployments work fine locally?

Ref: Troubleshoot an app in Azure App Service using Visual Studio
Gola, Mariusz 45 Reputation points

2023-07-21T12:55:13.4766667+00:00

Hi,

Actually today it runs fine locally without any elevated mode or as admin.

Everything works as expected when running localhost from VS2022.

The error is now only showing when I deploy to the app service. From my research the error is due to insufficient permissions.

Thank you

mariusz
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-24T13:00:03.3466667+00:00

mariusz, Apologies for the delay from over the weekend. Thanks for the follow-up and update.

You could try adding this route by appSettings. Please follow docs for the steps and let us know how it goes.
WEBSITE_LOAD_USER_PROFILE=1.

Environment variables and app settings in Azure App Service
Ref: Load certificate from file

If the issue still persists, enable and review the logs to fetch more info about the error.

Checkout the log directory/location information -here - Access log files

Kindly let us know hot it goes, I'll follow-up with you further.
Gola, Mariusz 45 Reputation points

2023-07-25T14:03:26.34+00:00

No worries, tried your suggestion but still same error. Not sure what other logs you would need I put the inner exception details in the post. We have started converting to different ORM as a solution.

thanks,

mariusz
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-28T13:00:27.69+00:00

mariusz, Just checking in to see if you had got a chance to see the previous response. I understand you have started different ORM as a solution. In my previous post, I have shared info about the App Service underlying operating system functionality, if the answer helped (pointed, you in the right direction) > please click Accept Answer Or please share more info to help you better.

2 answers

Your answer

Gola, Mariusz 45 Reputation points

2023-07-19T18:31:15.0233333+00:00

The actual call is happening within the Microsoft.Practices.EnterpriseLibrary.Common library which I don't have any control over.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-20T19:38:14.2033333+00:00

Mariusz, To better assist you on this, just to clarify, you have mentioned, "it works as expected running in VS2022 as admin.", does it work when running VS2022 ( as admin)?, but throws the error when not running VS2022 in elevated mode? Or does the deployment work fine on a different machine running VS2022, but not on another VS version?

Do the deployments work fine locally?

Ref: Troubleshoot an app in Azure App Service using Visual Studio
Gola, Mariusz 45 Reputation points

2023-07-21T12:55:13.4766667+00:00

Hi,

Actually today it runs fine locally without any elevated mode or as admin.

Everything works as expected when running localhost from VS2022.

The error is now only showing when I deploy to the app service. From my research the error is due to insufficient permissions.

Thank you

mariusz
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-24T13:00:03.3466667+00:00

mariusz, Apologies for the delay from over the weekend. Thanks for the follow-up and update.

You could try adding this route by appSettings. Please follow docs for the steps and let us know how it goes.
WEBSITE_LOAD_USER_PROFILE=1.

Environment variables and app settings in Azure App Service
Ref: Load certificate from file

If the issue still persists, enable and review the logs to fetch more info about the error.

Checkout the log directory/location information -here - Access log files

Kindly let us know hot it goes, I'll follow-up with you further.
Gola, Mariusz 45 Reputation points

2023-07-25T14:03:26.34+00:00

No worries, tried your suggestion but still same error. Not sure what other logs you would need I put the inner exception details in the post. We have started converting to different ORM as a solution.

thanks,

mariusz
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-07-28T13:00:27.69+00:00

mariusz, Just checking in to see if you had got a chance to see the previous response. I understand you have started different ORM as a solution. In my previous post, I have shared info about the App Service underlying operating system functionality, if the answer helped (pointed, you in the right direction) > please click Accept Answer Or please share more info to help you better.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Thanks for the follow-up and update.

All Azure Web Apps (as well as Mobile App/Services, WebJobs and Functions) run in a secure environment called a sandbox.

Azure App Service does not allow the registration of COM components on the platform. If your app makes use of any COM components, these need to be rewritten in managed code and deployed with the site or application.
Apps are not permitted to read from or write to the Event Log service.

Microsoft.Practices.EnterpriseLibrary.Data - The Database class leverages the provider factory model from ADO.NET.

Areas of diagnostics logging and tracing that aren't available to apps are Windows ETW events and common Windows event logs (for example, System, Application, and Security event logs). Since ETW trace information can potentially be viewable machine-wide (with the right ACLs), read and write access to ETW events are blocked.

You may checkout the approach outlined in this doc:

Migrate your .NET web app or service to Azure App Service
Migrate ASP.NET Web App to Azure App Service

If your app cannot be migrated directly to App Service, consider App Service using Windows Containers, which enables usage of the GAC, COM components, MSIs, full access to .NET FX APIs, DirectX, and more.

Reference: Operating system functionality on Azure App Service

Share via

Access issue with old Microsoft.Practices.EnterpriseLibrary.Data when running from Azure App Service

2 answers

Your answer