We recently found that Test-ExchangeSearch cmdlet was failing on our Exchange 2010 SP2 installation with error Time out for test thread.
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.IncrementBy(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue)
Last worker process info : Last worker process info not available!
The problem is that by default in Exchange 2010 not more that 52 databases (any state Mounted/Unmounted) so that get listed available under MSExchange Search Indices Counter. To work around this issue you can add the following Dword value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Search Indices\Performance
DWORD VALUE FileMappingSize
Decimal Value 1048576
We also created Msftefd.exe based on the Kb2837276 to resolve the issue.
Feel free to start a new thread on our forum to report a new issue or followup on this one
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016