G
Guest
Hi,
For some reason this exception is thrown by our application, when attempting
to retrieve a performance counter:
ExceptionName: System.InvalidOperationException
exceptionMessage: Custom counters file view is out of memory.
site: System.Diagnostics.SharedPerformanceCounterInt32 CreateCategory(Int32,
System.String, Int32, System.String, Int32, System.String)System,
Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
stackTrace: at
System.Diagnostics.SharedPerformanceCounter.CreateCategory(Int32
categoryNameHashCode, String categoryName, Int32 counterNameHashCode, String
counterName, Int32 instanceNameHashCode, String instanceName)
at System.Diagnostics.SharedPerformanceCounter.GetCounter(String
categoryName, String counterName, String instanceName)
at System.Diagnostics.SharedPerformanceCounter..ctor(String categoryName,
String counterName, String instanceName)
at System.Diagnostics.PerformanceCounter.Initialize()
at System.Diagnostics.PerformanceCounter..ctor(String categoryName,
String counterName, String instanceName, Boolean readOnly)
at System.Diagnostics.PerformanceCounter..ctor(String categoryName,
String counterName, Boolean readOnly)
Searching for a solution revealed that others have seen this error but
nobody knows whats happening. A fix has been offered:
"I did a brief investigation I am wondering if you are using lots of
performance counters.
I found that there is a .config setting that controls the max fileView
memory size. It is
<configuration>
<system.diagnostics>
<performanceCounters filemappingsize="524288" />
</system.diagnostics>
</configuration>
(see the filemappingsize attribute in the performanceCounters element)"
But id much rather fix the problem instead of doing the above in a live
environment hoping for the best.
In hopes of an answer...
Regards Alex
For some reason this exception is thrown by our application, when attempting
to retrieve a performance counter:
ExceptionName: System.InvalidOperationException
exceptionMessage: Custom counters file view is out of memory.
site: System.Diagnostics.SharedPerformanceCounterInt32 CreateCategory(Int32,
System.String, Int32, System.String, Int32, System.String)System,
Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
stackTrace: at
System.Diagnostics.SharedPerformanceCounter.CreateCategory(Int32
categoryNameHashCode, String categoryName, Int32 counterNameHashCode, String
counterName, Int32 instanceNameHashCode, String instanceName)
at System.Diagnostics.SharedPerformanceCounter.GetCounter(String
categoryName, String counterName, String instanceName)
at System.Diagnostics.SharedPerformanceCounter..ctor(String categoryName,
String counterName, String instanceName)
at System.Diagnostics.PerformanceCounter.Initialize()
at System.Diagnostics.PerformanceCounter..ctor(String categoryName,
String counterName, String instanceName, Boolean readOnly)
at System.Diagnostics.PerformanceCounter..ctor(String categoryName,
String counterName, Boolean readOnly)
Searching for a solution revealed that others have seen this error but
nobody knows whats happening. A fix has been offered:
"I did a brief investigation I am wondering if you are using lots of
performance counters.
I found that there is a .config setting that controls the max fileView
memory size. It is
<configuration>
<system.diagnostics>
<performanceCounters filemappingsize="524288" />
</system.diagnostics>
</configuration>
(see the filemappingsize attribute in the performanceCounters element)"
But id much rather fix the problem instead of doing the above in a live
environment hoping for the best.
In hopes of an answer...
Regards Alex