How to fix Event View Error : It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.

Question

It has taken too long to refresh the W3SVC counters, the stale counters are being used instead. I don't know how to solve. We are runs some servers at this computer and this error was thrown for the lasty few days. I searched in Internet, they said, This usually happens under 100% CPU load. You can safely ignore this message as your system works as expected (response time and etc.). I'm not go with answer because we have a load balancer. If one server loads over then the second server balances the load... So need to find another way to solve this... Thanks in advance... Here I attached some details about that error log on Event Viewer.

It has taken too long to refresh the W3SVC counters, the stale counters are being used instead.

Log Name - Application

Source - IIS W3SVC-PerfCounters

Event ID - 2001

Level - Error

User- N/A

OpCode - Info

Task Category - None

Keywords - Classic

Answer 1

If the service is so busy it can't update the performance counters you'll have to reduce the load on the CPUs. You can reduce the maximum number of connections, maybe disable compression when the CPU usage exceeds some limit, reduce the number of queued requests for the application pool(s), etc.

But this really isn't something the PowerShell has any control over. You should remove the "Window Server PowerShell" tag from your question.

Answer 2

Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

The Event View Error occurs when the Windows Performance Counters fail to refresh in time. To fix this, you can try the following steps:

Open up the Command Prompt as an Administrator.

Type in the command: lodctr /R and press Enter.

Wait for the command to finish executing and then reboot your system.

After the reboot, open up the Command Prompt again and type in the command: lodctr /R and press Enter.

After that, restart the WMI service.

Finally, restart the IIS services.

These steps should resolve the issue with the W3SVC counters failing to refresh in time.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

Answer 3

Hi @tony strak,

"This usually happens under 100% CPU load". It isn't quite due to CPU utilization. It is actually due to the W3SVC being busy with requests to deal with performance counters, it can be related to CPU or memory constraints.

The issue will be corrected by the system. You can refer to IIS W3SVC Performance Counter Availability. You can try Restart W3SVC, just follow these steps.

Hope my answer could help you.

Best Regard,

TengFei Xie

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.