Thursday 31 January 2019

The remote procedure call failed. [0x800706be]


Good day everyone and welcome to (or welcome back to) SQL Something!

Firstly, HAPPY 2019! I wish all my visitors the best for the coming year. May you all find your own special brand of success and happiness. 😊

Alright let’s get into it. I recently redid my PC and I had to re-install my various SQL instances as well as a couple variations of Visual Studio. Sometime after all of that was done, I opened SQL Server 2017 Configuration Manager and saw the following:

The remote procedure call failed. [0x800706be]

Woe is me...



Now after some digging around on the internet, I saw that it has to do with the fact that I have multiple versions of SQL Server. Apparently, Configuration Manager 2017 was attempting to incorrectly use the older versions of the service as opposed to the ones that were installed with SQL Server 2017.

So what do we do? We change SQL Server Configuration Manager to point to the correct one. This is a fairly easy process.


Step 1:

  • Press the Windows Key.
  • Type "SQL Server Configuration Manager".
  • Right click SQL Server Configuration Manager and choose “Open File Location”.
Step 1.

Step 2:

  •  Right click the SQL Server Configuration Manager and choose “Properties”.
  • Select the Shortcut tab.
  • Under the Shortcut tab, you will see a section marked “Target”. You may see a file path like “C:\Windows\SysWOW64\mmc.exe /32 c:\Windows\SysWOW64\SQLServerManager10.msc”.
  • You will be going to the folder location that is identified there. It will usually be something like “C:\Windows\SysWOW64\mmc.exe”.
  • Keep this Properties window open as you will be changing the file path soon.
Step 2.


Step 3:

  • Once in there you should see multiple SQL Server Manager files. Remember the name of the one with the biggest number.
Step 3.


Step 4:

  • Go back to the SQL Server Configuration Manager Properties window.
  • Change the Target file path (under the Shortcut Tab) to reflect the newest file. Example: Change “C:\Windows\SysWOW64\...SQLServerManager10.msc” to “C:\Windows\SysWOW64\...SQLServerManager14.msc”.
  • Click Ok.
  • Re-open SQL Server Configuration Manager.



And that’s it. Special thanks to the following article:

DISCLAIMER: As stated, I’m not an expert so please, PLEASE feel free to politely correct or comment as you see fit. Your feedback is always welcomed. :-)

No comments:

Post a Comment