Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 8820

Custom counters file view is out of memory - MSExchange Common Event ID 106

$
0
0

Hi,

We have a two node Exchange 2010 DAG configuration, with approx 60 databases split equally over the two nodes during normal operation. On one of the nodes we are receiving repeated errors in the event logs with source MSExchange Common and event ID 106. The text of the alert is generally along the lines of:

Performance counter updating error. Counter name is Number of Content Conversions Done, category name is MSExchange Search Indices. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: Custom counters file view is out of memory.

at System.Diagnostics.SharedPerformanceCounter.CalculateMemory(Int32 oldOffset, Int32 totalSize, Int32& alignmentAdjustment)

at System.Diagnostics.SharedPerformanceCounter.CreateInstance(CategoryEntry* categoryPointer, Int32 instanceNameHashCode, String instanceName, PerformanceCounterInstanceLifetime lifetime)

at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)

at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)

at System.Diagnostics.PerformanceCounter.Initialize()

at System.Diagnostics.PerformanceCounter.get_RawValue()

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)

Last worker process info : Last worker process info not available!

The counter name varies from alert to alert, but they are always to do with the MSExchange Search Indices performance object. When I look in performance monitor, the counters under that object are missing 5 of the databases (i.e. only show 55 of the 60).
I've tried rebuilding the search indexes using the resetsearchindex.ps1 script and I've tried reinstalling the Search Indices performance counters but with no difference. The search indexes themselves are building correctly and work fine, so it simply seems to be a performance counter issue. Exchange is running without a problem as well.
Any advice you can offer would be appreciated.
Best regards,
Matt Harbour


Viewing all articles
Browse latest Browse all 8820

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>