If you have ever contacted me via email, you would know that I am very active in replying to emails. Many of the emails are for suggestions and I don’t get much time to help everyone, but I do reply to them letting them know the alternatives. If you are following my blog, you would know that I do provide “On Demand” services to help critical issues. This blog is an outcome of one of such short engagement. This is how it started and it is about RPC Server.
Received an email
Need your urgent help “On Demand”!
We are trying to install SP2 on the passive node of a SQL Server 2016 cluster. This patch has already worked on one server, but now we’re getting RPC too busy errors.
We are under strict timelines to finish this activity. Can you please help us quickly?
Without spending much time, I asked them to join GoToMeeting and got started. When they showed me the screen, the SQL Server setup was on the error “Failed to retrieve data for this request”.
I asked to cancel the setup and share the setup logs to see exact error.
Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. —> Microsoft.SqlServer.Configuration.Sco.SqlRegistryException: The RPC server is too busy to complete this operation.
As we can see above, SQL setup is failing to do an activity on remote node. I immediately recalled a similar blog which I wrote earlier having same remote node symptoms, but the error message was different.
We checked “Remote Registry Service” on remote node and sure enough, it was in “stopped” state. As soon as we started, we were able to move forward and finish the activity in less than the scheduled time.
If you are having any quick issue to resolve, you can also avail the same kind of services. Click here to read more about it.
Reference: Pinal Dave (https://blog.sqlauthority.com)