Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for Exchange is producing "Performance counter updating error" event logs on the Exchange server

AppInsight for Exchange is producing "Performance counter updating error" event logs on the Exchange server

Created by Tiarnan Stacke, last modified by MindTouch on Jun 23, 2016

Views: 2,410 Votes: 0 Revisions: 4


A monitored Exchange Server with AppInsight for Exchange is producing event logs similar to the following:

Log Name: Application
Source: MSExchange Common
Logged: xx/xx/2016 04:00:15
Event ID: 106
Level: Error

Performance counter updating error. Counter name is Connection Leak, category name is MSExchangeRemotePowershell. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.


  • All SAM versions
  • AppInsight for Exchange


This issue occurs after the initial set-up of Exchange Polling or occurs after cumulative updates have been applied to the Exchange.

The root cause of the issue is that the Performance Counters cannot be loaded.


To resolve this issue please refer to the Microsoft KB - "Performance counter updating error" after you install an Exchange Server 2013 cumulative update.


Last modified