【问题标题】:Enterprise Semantic Logging OOP Exception企业语义日志记录 OOP 异常
【发布时间】:2015-02-28 11:05:47
【问题描述】:

我正在尝试使用语义日志记录应用程序块来使用进程外日志记录。我已经从here 下载并安装了进程外服务,将事件源名称更改为指向我的源名称。但是在运行服务时出现以下错误:

Message : A fault was detected while processing the configuration for the element 'svcRuntime'. Message: System.Runtime.InteropServices.COMException (0x800705AA): Insufficient system resources exist to
 complete the requested service. (Exception from HRESULT: 0x800705AA)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.InsureStarted(EVENT_TRACE_PROPERTIES* properties)
   at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.EnableProvider(Guid providerGuid, TraceEventLevel providerLevel, UInt64 matchAnyKeywords, TraceEventProviderOptions options)
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.Utility.TraceEventUtil.EnableProvider(TraceEventSession session, Guid providerId, EventLevel level, EventKeywords matchAnyKeyword, IEnume
rable`1 arguments, IEnumerable`1 processNamesToFilter, Boolean sendManifest)
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventServiceWorker.Initialize()
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventService.<>c__DisplayClass6.<AddWorkers>b__2()
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventService.HandleException(String callerName, Action body)
Opcode : Info
Task : 64731
Version : 0
Payload : [faultedElement : svcRuntime] [message : System.Runtime.InteropServices.COMException (0x800705AA): Insufficient system resources exist to complete the requested service. (Exception from HRESU
LT: 0x800705AA)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.InsureStarted(EVENT_TRACE_PROPERTIES* properties)
   at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.EnableProvider(Guid providerGuid, TraceEventLevel providerLevel, UInt64 matchAnyKeywords, TraceEventProviderOptions options)
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.Utility.TraceEventUtil.EnableProvider(TraceEventSession session, Guid providerId, EventLevel level, EventKeywords matchAnyKeyword, IEnume
rable`1 arguments, IEnumerable`1 processNamesToFilter, Boolean sendManifest)
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventServiceWorker.Initialize()
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventService.<>c__DisplayClass6.<AddWorkers>b__2()
   at Microsoft.Practices.EnterpriseLibrary.SemanticLogging.Etw.TraceEventService.HandleException(String callerName, Action body)]
EventName : TraceEventServiceConfigurationFaultInfo
Timestamp : 2015-02-28T10:31:09.3220291Z
ProcessId : 16524
ThreadId : 16984

进程内监听器工作正常。还有什么我需要做的配置吗?

【问题讨论】:

    标签: c# .net logging enterprise-library


    【解决方案1】:

    就我而言,这与我在 SemanticLogging-svc.xml 中配置的平面文件接收器的数量有关。

    似乎一旦我超过 36 个文件接收器就会出现此错误。

    【讨论】:

    • 似乎允许的文件同步数取决于机器上的可用内存。我不确定是总内存还是可用内存。最有可能在服务启动时考虑可用内存。
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2014-08-12
    • 2010-09-26
    • 1970-01-01
    • 1970-01-01
    • 2011-02-27
    相关资源
    最近更新 更多