Hi We use WMI to monitor Exchange 2003 servers. Some of these are installed in a cluster env. The wmi based monitoring works great for the standalone servers, but fails with an error message about the rpc server being too busy for the clustered servers.. I get the same problem when testing it with the "wbemtest" tool. I do the following: - Start->Run->wbemtest - Click on connect and thype root\cimv2\Applications\Exchange - Select "Enum classes" with recursive option - Double-click on "ExchangeLink" in the returned list, and press the "Instances" button I now see 10 returned rows, and then I get a popup window error message stating: Number: 0x800706bb Facility: Win32 Description: The RPC server is too busy to complete this operation Anyelse else experience this in Exch2k3 cluster nodes? What could be the problem? BR, Frank

The above described problem occurs *every* time I run the described command. It shows 10 rows (which is similar to the number shown in the batch count setting in the wbemtest tool), and then fails with the RPC too busy message. I have btw tried to increase the batch count setting in wbemtest, to see what happens. If I increase i just slightly, e.g. 12, I see 12 rows. But if I increase it to e.g. 20, I get no rows at all but instead get the RPC too busy error message right away. Anyone able to help? Frank

Hi Frank, Have you checked out whether one or more event ID message is logged in the Application event log? If it did, please paste the error information here. Such as event ID, event source and description, etc. You said “the above described problem occurs *every* time I run the described command”, does it means the issue occurs whatever on a standalone server or a cluster server? And I also recommend you run Exchange Best Practices Analyzer to have an overall health of your Exchange server and topology. Microsoft Exchange Best Practices Analyzer v2.8: https://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en I look forward hearing from you. Best regards, Serena

Hi Serena When the problem occurs, I see no traces of it in the event log :( With "occurs *every* time I run the described command" I meant that it occurs every time I run it on on the clustered servers. The problem is i.e. consequent. On non-clustered servers this problem does *not* occur. Frank

Hi Frank, Thanks for your post. Have you run ExBPA just mentioned above? If not, please try to run it and view the report provided by ExBPA. Best regards, Serena