Share via

Windows Logs - Application - Error:Perflib:EventID1023

VGuo 0 Reputation points
2026-05-15T10:39:59.76+00:00

My server have msqueue installed with 5 workers, but few months nearly, we oftenly have the issue for msqueue that the error is [no worker avaliable], i check 5 worker process is alive and the queue is not full, i realize there are some error in Windows Logs - Application, the error of the provider name is Microsoft-Windows-Perflib. just want to know is this error related to /or lead to the no worker avaliable error?

Windows for business | Windows Server | Performance | System performance
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. VGuo 0 Reputation points
    2026-05-15T10:45:36.4566667+00:00

    how to verify whether the server OS/MSMQ version matches those affected builds

    Was this answer helpful?

    0 comments
  2. Q&A Assist
    2026-05-15T10:40:12.59+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The Perflib Event ID 1023 errors in the Application log are performance counter initialization/registration issues. They do not control MSMQ worker availability and, by themselves, do not cause MSMQ to report “no worker available.”

    For the MSMQ “no worker available” problem, the context shows MSMQ issues on older Windows versions being caused by defects in Mqqm.dll that can make the Message Queuing service freeze or become unresponsive under load (for example, many remote reads or large queue sizes). In those cases:

    • MSMQ may stop processing messages even though the service and processes appear to be running.
    • The problem is confirmed as a bug in MSMQ components and is fixed by specific updates that replace Mqqm.dll with a newer version.

    Therefore:

    • Perflib 1023 errors are not the root cause of “no worker available.”
    • The MSMQ behavior is more likely related to MSMQ service issues similar to those described for Windows Server 2008/2008 R2, where the queue manager becomes unresponsive or freezes under certain conditions.
    • The recommended direction is to verify whether the server OS/MSMQ version matches those affected builds and ensure the MSMQ-related hotfixes/updates (that update Mqqm.dll) are installed, rather than focusing on Perflib.

    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.