Performance counter updating error
If Exchange is running in a DAG environment, failing to update any database instance of that counter category, can cause problems activating databases with an error similar to: Log Name: Microsoft-Exchange-High Availability/Operational Source: Microsoft-Exchange-High Availability Event ID: 306 Task Category: Database Action Level: Information Keywords: User: SYSTEM Computer: server2.Description: Initiating move for database 'DB1' (From Server=server2.contoso.comm, To Server=, This happens when Active Manager is unable to read the Process ID counter from MSExchagne IS Store on the pasive database instance.If you're wondering whether you're running into this problem, check on the MSExchange IS Store counters in perfmon and verify if they have values other than zero for all the database instances.Both servers are in vertulized with VMware, in an IBM storage. Moved all the mailboxes, public folders to the new server.Now on the old server (CAS, Hub Transport only), I am getting the following error, Performance counter updating error. Invalid Operation Excce 2552 Rtvscan 2156 SMSvc Host 9 SAVFMSESp 772 Logon UI 4908 svchost 5688 conhost 564 w3wp 2336 Locator 560 SMSMSEMgmt Srv 944 svchost 2716 svchost 6852 SAVFMSESrv 5148 SAVFMSELog 940 SAVFMSESp 3500 w3wp 344 csrss 2312 svchost 5660 SAVFMSEUI 1128 svchost 5852 Cmaf Report Srv 7032 SAVFMSESp 2892 Microsoft. Antispaervice 6760 SAVFMSESJM 6956 SAVFMSESp 5772 w3wp 3492 w3wp 792 svchost 252 svchost 444 winlogon 1624 exfba 6728 Console App Mgr 240 smss 5556 SMSUtility Service 624 svchost 2396 SAVFMSETask 3576 svchost 5564 conhost 400 wininit 5532 SAVFMSESp 408 csrss 4740 svchost 1980 MSExchange Transport 6500 SAVFMSESp 6704 conhost 4 System 1912 Microsoft. Service What events occur immediately before and after this event may provide more information about the root cause of this error Was there some updates done to this server for CAS role ? Moved all the arbitration mailboxes to the new server.Counter name is Explicit Sign-On Inbound Proxy Sessions - Total, category name is MSExchange Control Panel. Did you run EXBPA to check if it reports something related to this issue ? Cross checked if anything related mail box role is still exists in the server.Once confirmed all, uninstalled the mail box role and rebooted the server.
Understanding some of those differences helps on assessing the issue at hand.I used Exchange Management Shell with the following commands: (If you have a 32 bit OS you can replace AMD64 in lines 2 and 3 with x86) If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. After you install the Microsoft Exchange Server 2013 Client Access server role on a new server and then restart the server, you receive many Event ID 106 errors in the Application log.For example, you may receive the following error message: ID: 106 Level: Error Source: MSExchange Common Machine: – Message: Performance counter updating error. Invalid Operation Exception: The requested Performance Counter is not a custom counter, it has to be initialized as Read Only.\ When you check the Exchange Setup log (Exchange Setup.log), you see the following information: [WARNING] The performance counter definition file C:\Program Files\Microsoft\Exchange Server\V15\Bin\Perf\AMD64\Gls Performance could not be found.I am getting hundreds event id 106 for the performance counters for Microsoft Exchange: Log Name: Application Source: MSExchange Common Date: 8/22/2012 AM Event ID: 106 Task Category: General Level: Error Keywords: Classic User: N/A Computer: MAIL01.************* Description: Performance counter updating error. Invalid Operation Exc From what I understand sometimes when Exchange is installed in segments the performance counters are missed.Counter name is Event Dispatchers, category name is MSExchange Assistants - Per Assistant. I did not find the exact reason/reasons that caused this, but this is what I did to fix the problem.(Counter, Category, and Exception message vary): Performance counter updating error.Counter name is Percentage of MSAUser Net ID Cache hits for last minute, category name is MSExchange Global Locator Processes. Exception: The exception thrown is : This is the most common exception and normally not affecting more than the counter itself.Depending on the counter being reported the root cause can be code trying to access counters on an instances that is no longer running or disabled.The call stack could give us more insight on the specific situation. Invalid Operation Exception: Instance 'ad-umworkerprocess-umworkerprocess.exe' already exists with a lifetime of Process.