Fix: SQL Server Management Studio COM Error on Startup

Sunday, April 20, 2008

Every once in a while, and especially when I build virtual machines from existing images, I run into a weird error when running SQL Server Management Studio:

Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

With a little google-ing around did find a solution, well, actually two.
Once solution involves running an update to some registry keys (which is what always works for me) and the second a re-registration of a DLL (you've gotta love COM).

Option 1

As I mentioned earlier, this option always worked form me, and therefore I have never had to resort to option 2.

First, copy the following code snippet and paste it into a text file. Then rename the *.txt file you copied the snippet to, and rename to *.reg
Now  run the fix by double-clicking on the *.reg file and voila'. 
You'll get a message prompt telling you whether or not the registry was successfully update.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-

8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-

8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-

8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D514

0C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D514

0C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D514

0C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D51

40C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D51

40C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D51

40C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

PLEASE NOTE: I strongly suggest you back up your registry, as I take NO responsibility it is breaks anything :-)

Option 2

If option one failed to resolve your problem, then try running the following regsvr32 command:

C:\WINDOWS\system32>regsvr32 actxprxy.dll

One last thing to mention is that no one seems to know or remotely understand what causes this issue.

Additional information can be found here: http://forums.microsoft.com/msdn/showpost.aspx?postid=120476&siteid=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=0

Comments

PolUnited StatesPol said:

Got this message every time i clicked on an item (f.i. datbases)in management studio express . Ths message occured after installing vista service pack 1 !!
Did not tried the first solution because the 2nd looks better to me and indeed it works !!
Thanks a lot.

JCUnited StatesJC said:

FYI... Option 2 worked for me with the need for Option 1.

I'm running Windows Vista64 SP1, SQL 2005 SP2

Go to run command line > type in regsvr32 actxprxy.dll

Thanks for blog post!

HelUnited StatesHel said:

Tried removing and reinstalling management studio to no avail. Next tried option 2 (seemed less dangerous than registry editing). Second option worked without the need for the first. Thanks a million!

Antonio ChagouryUnited StatesAntonio Chagoury said:

@hel: Glad to see that helped!

BradUnited StatesBrad said:

Option 2 worked for me without doing option 1. Thanks! This one has been driving me nuts.

RobertUnited StatesRobert said:

Option 1 worked for me, although just copying and pasting from the site to Notepad didn't give me a valid reg file, so I had to do some editing (specifically the GUIds had some Cr/Lfs)..

Thanks!

Nader SolimanUnited StatesNader Soliman said:

The second is much easier and it worked like charm for me.
Thanks a lot.

Mahesh SharmaUnited StatesMahesh Sharma said:

First option worked for me. Thanks a ton

AniseUnited StatesAnise said:

The 2nd option worked great! I was having this error with Server Express 2008 after installing Server Compact Express, installing VS 2008 SP1 and Server Express 2008. Evidently there was some conflict or corruption going on between these 2 programs and the shared add-in program.

DaveUnited StatesDave said:

Thank you so much! This error was driving me insane, and your option #2 fixed it perfectly. I tried option #1 first, but that didn't do the trick for some reason. Many thanks!!

BruceUnited StatesBruce said:

The #1 option works on me. Please make sure you remove the space and line break between '[' and ']' if you copy and paste the code from this page. Otherwise it won't work.

Add comment




  Country flag

biuquote
  • Comment
  • Preview
Loading