SQL Server Configuration Manager – Remote Procedure Call Failed

SQL Server Configuration Manager – Remote Procedure Call Failed

If you find a need to install multiple version of SQL Server on a laptop of server, you are bound to run into a problem with the MMC snap for configuring the instances.  One of the most common, the remote procedure call failed.  This error is simply due to the lack of backward compatibility for 2008 SQL Server Configuration Manager.  In this case, the set of events that were probably taken were

1. SQL Server 2012 was installed
2. SQL Server 2008 or prior was installed

In this case, the tile that is shown will point to the 10 build of SQL Server Configuration Manager.  Since 2008 manager has issues connecting, it throws the RPC error – seen below.

To fix this problem on Windows 8, a new shortcut simply needs to be pinged to start or, you can edit the current one already there.

Right click the tile to start.  Click Open File Location in the menu shown on the bottom of the screen.

 

You should come to either a 2005, 2008 or 2008 R2 configuration list

Right click the SQL Server configuration Manager shortcut and go to properties.

In the Target, you’ll see the snap is going to the SQLServerManager10.msc.  This is a 2008 R2 version and will not work well, if at all, with 2012 (or 2014).

C:WindowsSysWOW64mmc.exe /32 C:WindowsSysWOW64SQLServerManager10.msc

Looking further, the MSC for opening MMC, is located in the SysWOW64 folder.  This is the common location in which all the MSC files will be located.  As shown below, you can see both 2008 R2 and 2012 MSC files.

What you will want to do is one of two things.

1. Remove the SQL Server Configuration Manager form the tiles on your machine and add the one below, found in the 2012 folder
2. Leave the prior version, if needed for other configurations, and rename the 2012 MSC so it is easily distinguished – recommended

To perform the second option, open the folder as shown below.

Right click the shortcut and rename it something you can either see in the tile or hover over to distinguish that it is the 2012 configuration manager.  Ensure the Target points to the SQLServerManage211.msc as shown below.

Once completed, right click the shortcut and “Pin to Start”

The tile will now show as well as hovering over it, showing this is the 2012 version that should not throw the RPC error.

Test the new shortcut to validate the services do, in fact, load correctly now.