I'm on Exchange 2010 SP1 and every time I run the Exchange Best Practices Analyzer, after I select to do a basic Health Check, it crashes on me. It says Best Practices Analyzer has stopped working. I then check the event logs and these two errors show up every time: Log Name: Application Source: MSExchange Common Date: 5/27/2011 8:47:44 AM Event ID: 4999 Task Category: General Level: Error Keywords: Classic User: N/A Computer: COMPUTERNAME Description: Watson report about to be sent for process id: 10760, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, ExBPA, M.E.Data.Directory, M.E.D.D.NativeMethods.DsaccessPerfCounterUpdate, System.AccessViolationException, 351d, 14.01.0289.001. ErrorReportingEnabled: False Log Name: Application Source: Application Error Date: 5/27/2011 10:00:06 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: COMPUTERNAME Description: Faulting application name: ExBPA.exe, version: 14.1.218.11, time stamp: 0x4c5fab80 Faulting module name: dsaccessperf.dll, version: 14.1.279.0, time stamp: 0x4d22ce68 Exception code: 0xc0000005 Fault offset: 0x0000000000006369 Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 It used to work just fine and then the next day it stopped working. I didn't make any changes that I know of. This is a new exchange install with an Exchange 2010 SP1 DVD running on Windows Server 2008 R2 SP1. This server runs the CAS and HUB roles. Our mailbox role server can run the BPA just fine and has the same setup/updates, besides the different roles. Any Ideas? Thanks

1. Check your logs,these to be very generic. Seems like there's some drwtsn log avaliable. 2. You can try and update your to the latest rollup if you're not on there? 3. Maybe a support call to MSFTSukh

Hi ajkeys, Any update for your issue? How about update the the EXBPA tool, or reinstall the managemnt tool ? Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

A reboot seemed to fix the issue, but I did notice on reboot that I got two errors in the event log, again relating to performance counters. The first one is: Event ID: 10 Source: System.ServiceModel 4.0.0.0 Description: A performance counter was not loaded. Category Name: SMSvcHost 4.0.0.0 Counter Name: Connections Dispatched over net.tcp Exception:System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. And the second is: Event ID: 106 Source: MSExchange Common Description: Performance counter updating error. Counter name is Total Bytes To Download, category name is MSExchangeFDS:GM. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. It doesn't seem to be affecting any services though. Would be nice to figure out what is happening. I have spent days searching, but haven't found anything that seems to help.

Hi ajkeys, After doing some research about the issue, it maybe cause the hardware issue, what's the mode of the exchange box server? I would suggest that you could update the driver. Please also check the server performance, confirm the RAM and CPU usage whether is normal. Any other software installed on the server, such as antivirus software. Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.