RPC Server too busy?
This is a discussion about RPC Server too busy? in the Windows Networking category; WTF I am trying to apply attributes and I get this message saying the RPC Server is too busy to complete the operation. But the server has nothing to do except be PDC (Primary Domain Controller) and serve files.
WTF I am trying to apply attributes and I get this message saying the RPC Server is too busy to complete the operation. But the server has nothing to do except be PDC (Primary Domain Controller) and serve files...
What is the problem here it is very frustrating?
What is the problem here it is very frustrating?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Oct 23
Oct 30
0
1 minute
Responses to this topic
The easiest way to check your RPC activity is with Perf Mon. Open a perf mon session for that machine and monitor your individual processes and check which one is using the most resource. Once you've isolated your thread using the most resources, check how many Virtual Bytes the process is trying to use. This would usually be an app trying to do a remote operation. Should the virtual bytes be large, it indicates that that's the amount of resources it's trying to use (Virtual Bytes that is). You have to execute perf mon on the machine as RPC will not allow another connection if it claims to be too busy!
