When analyzing an Exchange 2013 Server, the user connections statistics that are available in the GSX Monitor Statistics or Graphs section may display a very high value.
This article describes how a corrupted Performance Counter can affect multiple statistics, how to identify when it happened and what the best actions are to restore the counter to the correct value.
- Exchange Statistics OWA Current Unique Users > 2147483650.
How to Troubleshoot the Issue
The OWA Current Unique Users statistic is reaching the maximum value for an integer (2147483650).
As this value is used to compute the Total User Connections, the related statistics are also affected:
- Total User Connections.
- Total User Connections without Maintenance.
- Total User Connections Bus. Hours without Maintenance.
- Max Total User Connections.
- Max User Connections without Maintenance.
- Max User Connections Bus. Hours without Maintenance.
To track the history of scans, you can use the Graphs view in GSX Monitor to determine when the value became corrupted.
- From GSX Monitor, select the Graphs view.
- Open Exchange - Total User Connections.
- Right-click on the relevant server graph and select Details - Selected statistic for this server only.
- You can scroll through this scan history to determine the first time the Performance counter became corrupted.
It is worth investigating if anything happened on the date the value changed. This could be related to a Windows update, or any other updates that require an operating system restart.
- Open a Session on the relevant Exchange Server using an Exchange Administrator account.
- Open a PowerShell Prompt.
- Issue the following command to retrieve the Performance Counter value:
Get-Counter “\MSExchange OWA\Current Unique Users”
The full name of the performance counter may be different if your language is not set to English.
After trying to troubleshoot the issue in several customer environments, we determined that the operations below can return the Performance Counter to a normal value. Either option can resolve the issue.
- Restarting the Exchange Server.
- Restarting the IIS Processes (see this Help Center article for details).