Object Explorer/Server Explorer Error

Question

I have just installed the released VS2005 as well as the released SQL2005.  When ever I try to browse my SQL Server with either the Object Explorer in MS SQL Server Management Studio or the Server Explorer in VS2005 I get the following error:

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)).

Does any one have possible solutions for me? Any help would be greatly appreciated.

--Nick

Answer 1

I've got the exact same error. And I've tried uninstall / reinstall SQL 2005, SQL 2000, uninstall / reinstall Client Component where the Management Studio is located, and even uninstall / reinstall VS2005, VS2003 with NO luck and NO clue to get it going.

Can someone shed some light on this issue?

===================================

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)). (Microsoft.VisualStudio.OLE.Interop)

------------------------------
Program Location:

   at Microsoft.VisualStudio.OLE.Interop.IServiceProvider.QueryService(Guid& guidService, Guid& riid, IntPtr& ppvObject)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceProvider.GetService(Guid guid, Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceProvider.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ShellWindowPaneUserControl.GetService(Type svcClass)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.System.IServiceProvider.GetService(Type serviceType)
   at System.ComponentModel.Design.ServiceContainer.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NodeContext.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetChildren()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren()

Answer 2

I have a solution for the problem, but I still do not know why it was a problem to begin with. It seems that the IServiceProvider COM object is not registered on the system.  I went to a system that this was working properly and exported the following registry entries:

[Copy from HERE]
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\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"
[ ... TO HERE]

Merging them on the broken system fixed the problem.  I would still appreciate anyone shedding some light on the situation, but it works for now.

--Nick

Answer 3

Thanks a lot! Nick, that appears to have fixed the problem.

Answer 4

I'm having the same problem. How do you go about "merging" the registry results you have above into a new registry?

Thanks in advance.

Answer 5

Copy the text inbetween the two copy markers and save them to a text file with any name and a ".reg" extension.  Right click on the file you just created and select "Merge".

Hope this helps,
--Nick

Answer 6

Perfect, that did it. Thanks!

Answer 7

Solved my problem with Team System as well as Sql Server 2005. 

Thanks Nick.  Lifesaver.

Answer 8

I have no words to thank you enough!!

It worked flawlessly.

You saved me lots of headaches.

-- EduQuint

Answer 9

Worked for me too, perfectly!  THANKS! This needs to be made easier to find on the web...

 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)). (Microsoft.VisualStudio.OLE.Interop)

------------------------------

Program Location:

 

at Microsoft.VisualStudio.OLE.Interop.IServiceProvider.QueryService(Guid& guidService, Guid& riid, IntPtr& ppvObject)

 

Answer 10

Hi All,

I am getting this error

"Unable to cast COM object of type 'System.__ComObject' to interface type
VSLangProj.VSProject'. This operation failed because the QueryInterface
call on the COM component for the
interface with IID '{2CFB826F-F6BF-480D-A546-95A0381CC411}' failed
due to the following error: No such interface supported (Exception
from HRESULT: 0x80004002 (E_NOINTERFACE))."

while working with VS2005. I added a test project and included a web test. The test is running for the first time but when I close the application and open that again and try running the test it is showing this error. I have repaired VS2005 also but nothing is working.

Could anyone help me in solving this...
Thanks in advance,

 

Answer 11

Did not help me. I checked reg and made sure everything is there. But I still get the same problem. Please help!

Answer 12

Try re-registering actxprxy.dll (in system32\). I had this problem, and the root cause was that the path to this dll in the InProcServer registry key was wrong. I have no idea how it got corrupted, but running regsvr32 on the dll fixed it.

Answer 13

Thank - You, registering the actxprxy.dll fixed the error for me :)

Answer 14

Thank you so very much.  This fixed my problem.

John

Answer 15

While trying to create a new table with Microsoft SQL SERVER  Mangement Studio, I receive this error message:

Impossible d'effectuer un cast d'un objet COM de type 'System.__ComObject' en type d'interface 'Microsoft.VisualStudio.DataTools.Interop.IDTDocTool'. Cette opération a échoué, car l'appel QueryInterface sur le composant COM pour l'interface avec l'IID '{00000000-0000-0000-9C05-9B6BA8059B6B}' a échoué en raison de l'erreur suivante : Cette interface n'est pas prise en charge (Exception de HRESULT : 0x80004002 (E_NOINTERFACE)). (SQLEditors)

------------------------------
Emplacement du programme :

   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.TableDesignerNode.CreateDesigner(IDTDocToolFactoryProvider factoryProvider, IVsDataConnection dataConnection)
   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDataDesignerNode.CreateDesigner()
   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDataDesignerNode.Open()
   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VirtualProject.Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Urn origUrn, DocumentType editorType, DocumentOptions aeOptions, IManagedConnection con)
   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ISqlVirtualProject.CreateDesigner(Urn origUrn, DocumentType editorType, DocumentOptions aeOptions, IManagedConnection con)
   à Microsoft.SqlServer.Management.UI.VSIntegration.Editors.VsDocumentMenuItem.CreateDesignerWindow(IManagedConnection mc, DocumentOptions options)

If someone can help me about this please...

 

 

Answer 16

Hi Nick

 

I'm a newbie here.  I enjoyed your analysis of 0x80004002.  However, I do have a simple question, where would one go to get a copy of reg files for merging?  They are not on my machine.  Are they downloadable from some where on the internet?  Thanks for your time!  Sanford

Answer 17

If you go back to my posted marked "Accepted Answer" from 02 Nov 2005, 6:49 PM UTC...


1. Copy all text from the after the [Copy from HERE] line to and before the [ ... TO HERE] line
2. Open notepad or anyother text editor and paste the text in.
3. Save the file with a ".reg" extension.
4. To merge them just right click the file you just created and select "Merge"

--Nick

Answer 18

Hi Nick

Again, thanks for taking some time to reply!

I did try what you outlined.  However when I clicked "merge" on the *.reg file another error message popped up indicating only binary registry files may be merged.  I initially saved the *.ref file to my desktop after creating it in Notebook.  The file had the traditional "reg" look about it with all the "little squares" surrounding the icon.  I attempted to merge that file from my desktop.  I still received the merge error message.  Ideas?  Sanford.

Answer 19

Hi Nick

I tried to install it a second time and it took!  Great!  But.  After I rebooted and attempted to re-trace my steps - I received the same 0x80004002 error!!!  I re-read the thread and someone had the same problem but fixed it by calling actxprxy.dll via regsvr32.  I must confess I do not not know which formula/switch to use:  regsvr32/i/u/s/?/(Cmdln?)actxprxy.dll to re-register the .dll.  Possibly this will solve my dilemma.  Thanks, again, Sanford

Answer 20

I will assume that you tried to double click on regsvr32.exe from Windows Explorer.  If this is incorrect and you ran it from the command prompt then type: regsvr32.exe actxprxy.dll

Otherwise find and select actxprxy.dll in the same directory as regsvr32.exe. Drag actxprxy.dll and drop it on the regsvr32.exe.

I would not worry about other command line options they are not applicable to this situation.

--Nick

Answer 21

Thanks Nick!  Maybe one day I can return the help?!  I really appreciated your help.  Sanford

Answer 22

Nick, you're the man. Thanks

Answer 23

Please let me offer my thanks as well.  I started getting the error after installing SourceSafe.  I uninstalled SQL2005 and re-installed and still got the error.

Followed your instructions and it solved the problem.  Many thanks.....

Answer 24

this worked for me too!  Thanks.

Does anyone know why the registry would not have this already set up? I had my db working just fine and then today it stops working? strange.

 

thx,

M

Answer 25

WOW - it worked for me, and now my SQL Server Mgmt Studio is faster than ever! 

Thanks Nick!

Answer 26

I followed this thread and figured you would be able to help. I am getting a similar error, here is the scenario:

Using ArcGIS Desktop 9.1 (build 722) or ArcGIS Desktop 9.1 sp1 on Windows XP sp2, I am getting an error when opening a project in our application (GeoFields DFASG):

Message: Unable to cast COM object of type 'System.__ComObject' to interface type 'ESRI.ArcGIS.Carto.PageLayout'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{4A708AE4-4B40-438E-A609-0BBD67EA508C}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
StackTrace:
at GeoFields.UI.DFASG.frmMain.openGFTemplate(String sFilePath)
at GeoFields.UI.DFASG.frmMain.mnuOpenGFProject_Click(Object sender, ClickEventArgs e)

I re-installed ArcGIS 9.1 build 722.
I upgraded to ArcGIS 9.1 sp1.
I registered actxprxy.dll
I re-started COM+System Application Service.

I am getting this error consistently on two of my testing machines and that prevents me from running our application. The application runs fine on other testing machines.

Do you have any other suggestions what I could try?

Answer 27

Hi all

I am getting a problem:

I use OLE DB Connetion Manager with IBM Informix OLE DB Provider driver (IBM Informix Connet 2.90 TC6) in Integration Services of Visual Studio to connect my Informix server, when test the connection get error 'IErrorInfo.GetDescription: E_NOINTERFACE(0x80004002)'

 

Can anyone help me?

Thank you!

 

Answer 28

This was really helpful. Solved my problem. Thanks a lot

Answer 29

Thanks Nick... You da man :)

Answer 30

mckenzieg1 wrote:

Try re-registering actxprxy.dll (in system32\). I had this problem, and the root cause was that the path to this dll in the InProcServer registry key was wrong. I have no idea how it got corrupted, but running regsvr32 on the dll fixed it.

Thanks Dude!  That worked!  No need to muck around with the registry directly.

Answer 31

This was perfect! Thanks for the information.

Answer 32

Brilliant Nick!

I had the same problem after installing Visual Studio 2005 Extensions for Share Point Services 3.0. Removed the extensions, but it did not solve the problem. However your patch worked. Thanks a lot!

Alex

Answer 33

Hi Nick,
I followed this thread and seem to believe that you must know the answer to a similar problem I have.

I recently installed SQL 2005 and Visual Studio 2005. Since then when using Business contact manager in Outlook, I get the following error. I tried to merge the registry entry in your previous thread, but the problem still exists. please help:

Unable to cast COM object of type 'System.__ComObject' to interface type 'msforms.Control'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{04598FC6-866C-11CF-AB7C-00AA00C08FCF}' failed due to the following error:  could not be found. (Exception from HRESULT: 0x80030002 (STG_E_FILENOTFOUND)).

Answer 34

Nick,

I have been facing the same error as yours but with different Interface. The error is:

Unable to cast COM object of type 'System.__ComObject' to interface type 'EnvDTE.ProjectItemsEvents'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{22800963-2811-410D-BF87-A7808EAC977D}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

I've tried to solve it but useless. Any suggestions!!! I'll be thankful.

Answer 35

C:\WINDOWS\system32>regsvr32 actxprxy.dll fixed mine too. Thanks a bunch!

Answer 36

This worked well.  Thanks a million.

Babu

Answer 37

Thanks, the regestration worked for me no issues.

 

Thanks !!!

Answer 38

Re-registering actxprxy.dll fixed the problem. Thanks a lot!

Answer 39

hey Nick that was superb........i tried install/reinstall twice before and it used to work only for the first time and then it gave me errors.............you have saved me...plz keep posting such informations....they are really valuable. thanks

Answer 40

I WAS having the same error (0x80004002) in SQL Server Management Studio installed with SQL Server Enterprise x64 extended on a machine running the Windows 2003 R2 x64 OS. I have tried the solutions posted in this forum with no luck. The exact error message and the error's location are posted below.

 

Then I ran RegSvr32.dll against the version of ActxPrxy.dll that lives in Windows\SysWOW64. The problem is now gone.

 

Thanks for the tips.

 

Chris

 

===================================

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)). (Microsoft.VisualStudio.OLE.Interop)

------------------------------
Program Location:

   at Microsoft.VisualStudio.OLE.Interop.IServiceProvider.QueryService(Guid& guidService, Guid& riid, IntPtr& ppvObject)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceProvider.GetService(Guid guid, Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ServiceProvider.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ShellWindowPaneUserControl.GetService(Type svcClass)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.System.IServiceProvider.GetService(Type serviceType)
   at System.ComponentModel.Design.ServiceContainer.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NodeContext.GetService(Type serviceType)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetChildren()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren()

Answer 41

Thanks! - That worked beautifully!

 

Mike

Answer 42

I don't see the following registry keys even on a good system with no problems with SQL Server 2005, what should I do?

I don't see an Interface directory under [HKEY_CURRENT_USER\Software\Classes PLEASE HELP!!!

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

[HKEY_CURRENT_USER\Software\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

Answer 43

Ok I followed your instructions on importing the regkeys and I also had to regsiter that dll mentioned again.

This is really strange considering it was working fine before.

Answer 44

This helped me as well. Thanks a lot!

 

Answer 45

this doesn't solve my problem. merge process is successful but i'm still having the same error

 

Answer 46

I solved my problem by using late binding maybe(I hope ) it helps you, too.

Answer 47

Nick,
thank you very much for putting this in this thread. It's solved my problem which I have facing since 3 days. It's saved my life. Thanks tons.
Rowan

Answer 48

me too.

Thanks all for the .reg and .dll fix!!!

Answer 49

 

I tried the registry merge method and that didn't work for me but when I re-registered the DLL it worked perfectly, thank you.

Answer 50

Thanks for this solution.  The registry part above didn't fix it for me,  re-registering seems to have worked.  Thanks for this advice.

Answer 51

I had this error after the server had been rebooted by another team.

The actions below fixed it for me - slightly less work than the regsvr32 route:

• Open SQL Server Management Studio, and dismiss the initial connection dialog so that SSMS opens without any connections
• Click the "New Query" button in the toolbar and this time give your credentials at the prompt

I guess that the missing actxprxy.dll appears to be re-registered automatically this way, because I no longer get the error "Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.VisualStudio" when I open SSMS.

 

Answer 52

Thanks for all of the solutions guys, but I'm hoping someone could help me with a problem implementing them.

I have the exact same error. I created the registry fix and ran it. And all I can get is:

Registry Editor

Cannot import E:\Desktop\new keys.reg: Not all data was successfully written to the registry.  Some keys are open by the system or other processes.


That's fine, I presume SQL Server is probably still going. I turn everything off, still won't work.

I have tried:
Killing all identifiable SQL process and stopping all SQL services
Booting into Safe Mode
Uninstall SQL Server 2005 and Installing SQL Server 2008 (
not upgrade)
Uninstalling all traces of SQL Server I can find.

... and still, it tells me that some keys are open when I run the .reg file. Opening SQL Server Management Studio (if installed) still gives me the same error (even in 2008).

I manually checked the registry keys which are changed in your suggested solution to see which hadn't been altered or weren't at the correct value, and the one that is causing me the trouble is  the very last one:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{B8DA6310-E19B-11D0-933C-00A0C90DCAA9}"

Currently it's at a completely different value, and I can't alter it manually because ... you guessed it, it's open by the system or other processes.

I'm going nuts trying to fix this, and most of all I need my SQL Server back up and running.

Does anybody know what specifically uses this key so I can specifically kill said process? Any other ideas?

Thanks,
Hannah

Answer 53

 

I am receiving this error and none of the fixes have worked. I am running Windows XP 64-bit.

Answer 54

 

Sorry please disregard.

Answer 55

So I too am just now having this problem.  I have Visual Studio 2005 and 2008 with SQL Server 2005 installed in a VMWare instance that has been working well for several months.  Today I added an existing .html file to a project I have been working on and I started getting this unregistered COM error like the rest of you.

 

I merged the registry entry in this thread and I re-registered the actxprxy.dll to no avail.  I am still getting the same error!

 

I am running all of this in Windows Server 2003...

 

-Ideas?

 

Answer 56

     I don't know what's I should say here can express my great appreciation to you.You know ,I got this problem several days ago,and it troubled me servely these days.Fortunately,I come here and get your help.You can nerver imagine how I'm excited when the problem was fixed and my .NET available.Thank you very much,my GOOD FRIEND!!! GOD BLESS YOU!!!  (There may be some wrongs with these words because of my poor English,Please don't mind)

Answer 57

Thx for the hint!!

 

Been trying for hours!

Answer 58

Well I tried all of this out and it didn't work. He had this probllem also when going to Visual Studio and also had problems when being in windows ecplorer that everything popped up in another window.

 

I tried the registry changes and re-registered that dll without any succes.

 

Now what is really funny is that this week i also had to rechange the guys computer name so i had to retake him out of the domain. After computer name was changed i put him back in the domain and both problems where instantly gone.

 

Why this happened i have no idea, but it might help the peoples who had exactly like me the problem that it didn't work. I was looking to fix that problem like over one week already. So i hope peoples can fix it quicker in the future.

 

Greetz

Answer 59

If you are running a 64-bit OS, you will need to run register the dll, but under C:\Windows\SysWOW64!

</hugeheadache>

Answer 60

Thank you very much.

Answer 61

Thanks Nick - this was our fix as well.  We're not sure why we started to get this error out of the blue but your suggestion fixed it for us.

jd

Answer 62

TITLE: Microsoft 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)). (Microsoft.VisualStudio.OLE.Interop)

------------------------------
BUTTONS:

OK
------------------------------



I am getting the same problem again can some1 help me

Answer 63

I have tried both fixes, none of them helped. To me error occurres when trying to publish any project.

I don't know what to do. Except burn my computer. :)

Answer 64

I tried the answers here but it's NOT WORKING still.

I tried re-install it but it's not solving it either.

Any clue?

Thanks

Answer 65

What worked for me was to first deregister the dll then register it again

so i first did this  C:\windows\system32 > regsvr32.exe /u actxprxy.dll

and then register it again C:\windows\system32 > regsvr32.exe actxprxy.dll

Hope this helps.

Answer 66

Try removing ie8 http://support.microsoft.com/kb/957700
This worked on a win 2k8 A/P cluster running sql 2008

Answer 67

This happened to a Windows 2008 box, running SQL Server 2008. SQL Management Studio was throwing an error on attempting to explore the server.

The removal of IE8 cured the problem with the above link. Very annoying!

Answer 68

What worked for me was to first deregister the dll then register it again

so i first did this  C:\windows\system32 > regsvr32.exe /u actxprxy.dll

and then register it again C:\windows\system32 > regsvr32.exe actxprxy.dll

Hope this helps.

Win 2008 64 sql server 2005 64 sp3 tis fix work ok.

unregister and register again and now works.

---

Michalek

Answer 69

I read through the whole thread and tried the registry modifications and the unreg reg options. I'm using Win7 and sql 2008 w/ SP1.  Nothing seems to work for me.  Oh, and it's win7 so there is no way to uninstall IE8.


Error:

TITLE: Microsoft 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)). (Microsoft.VisualStudio.OLE.Interop)

------------------------------
BUTTONS:

OK
------------------------------

Answer 70

Hi Jonathan,
I am having the same problem with Win7 (RC) X64 and SQL 2008 Developer.  There is a way to remove IE8 under WIn7 through the Control Panel -> Turn Windows features on or off.

Unfortunately, removing IE 8 under Win7 did not correct the problem.

I have tried merging the registry settingsd (merged OK) and registering the file actxprxy.dll (fails) but neither of these corected it either.

If you find a solution for Win7 7, I would be very greatful to hera your approach.  I will try SQL 2005 on my Win7 box.

NormD

Answer 71

Hi Jonathan (again)
I solved the problem with Win7 (RC) X64 and SQL 2008 browsing databases.

Just for kicks, I launched SSMS by selecting "Run As Administrator".  Once that was done, all of my database browsing problems went away.

Even tough I was logged in as the primary user for Win7 which as set up as a member of the Administrators group, launching SSMS normally raises the error.  I remember from the past that the built in WIndows Administrator had certain rights that are not inherited by a normal login that is a member of the Administrators group but I don;t know where they afre defined.

I hope that this will also work for you.

NormD

Answer 72

I'm running Win7, and installed Visual Studio 2008 before installing SQL 2008.  I have the problem and the same machine installing those two in reverse order does not have the issue.  Not sure if that caused it but none of these fixes have worked on Win7.

The only one that worked a bit is to close out of the opening connection then connect to a server from the server list.   Using that opening connection causes the error.

If someone finds a fix for Win7 please post!

thnx!

Answer 73

Thanks NormD  I haven't tried it yet because I was to quick to rebuild. (it's hard not to with how fast win7 installs, it still blows me away!)

preAmped I see the problem after installing the SP on VS.  I guess if I install SQL after all that, instead of before, that may work, I'll give it a try, however the runas administator would be good enough for me for now.

Jonathan

Answer 74

So I figured out my issue.   Installing Vault 3.5...   might not want to do that running win7!   Luckily, right before I installed it I created a restore point.  Restored and was good to go!   This was my 4rth install of Win7 and I bet it all goes back to having Vault installed at different stages.  

Everything is running smooth for me now.

ry

Answer 75

Also having the problem with Win7 (and SQL Server Mgmt Studio 2005) -  neither the registry fix or the dll registration fixed it for me either.

Can work around, but definitely an annoyance.


HELP US oh great Windows 7 gods!

Answer 76

Vault 3.5 installs ok on Windows 7 64 bit (setup completes successfully), but it messes up SQL Server Management Console 2008 (the same error as others have described). Registering the DLL doesn't work.

I tried a couple of different ways but could only get back to a functioning system by using a restore point.

Answer 77

I figured out how to make Vault 3.5 work on a Windows 7 64 bit system.

1) Install the Vault client using setup program.
2) Roll the install back out of your system using the last system restore point (it leaves the Vault program files, but clears out the damage to the registry made during the install).
3) Add the following registry settings to your system (change the D:\ drive reference below to the drive that you have Vault installed on).  These settings will make Vault show as a provider in Visual Studio)

-- start of registry script --

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider]
"ProviderRegKey"="Software\\SourceGear\\Vault Client"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider\InstalledSCCProviders]
"SourceGear Vault Client"="Software\\SourceGear\\Vault Client"

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear\Vault Client]
"SCCServerName"="SourceGear Vault Client"
"SCCServerPath"="D:\\Program Files (x86)\\SourceGear\\Vault Client\\VaultIDE.dll"

-- end of registry script --

Answer 78

I had this problem after just installing Access 2007.  Everything was fine (SQL2005 and VS2008), until then.

Thanks for the fix!

Answer 79

Thanks for the info Henrick.

I have just installed Win 7 x64, SQL 2008, VS 2008, Vault 3.5 and then SP1's for SQL & VS, and now have this error with SQL Mgmt Studio.

Unfortunately I don't have a restore point available pre Vault install, so any ideas if I can fix this without a complete re-install!  I just finished getting everything completely installed and configured how I like when I noticed this SQL problem, so would really like to avoid a re-install if I can.

Thanks,
Murray

Answer 80

Thanks for the info Henrick.

I have just installed Win 7 x64, SQL 2008, VS 2008, Vault 3.5 and then SP1's for SQL & VS, and now have this error with SQL Mgmt Studio.

Unfortunately I don't have a restore point available pre Vault install, so any ideas if I can fix this without a complete re-install!  I just finished getting everything completely installed and configured how I like when I noticed this SQL problem, so would really like to avoid a re-install if I can.

Thanks,
Murray

I am in the same boat. Would great appreciate a fix for this particular scenario. I am on Win 7 x86, but seeing the same issues. none of the fixes proposed to this point work, and I don't have a restore point available :(

Answer 81

I upgraded my Vault Server to the latest release (4.1.4) and upgraded my Vault Client on my Win 7 x64 pc (that had the SQL Mgmt Studio problem) and everything is now working fine! 

No manual registry changes required, just install the latest vault client (which uninstalls the old client automatically, and fixes whatever the problem was). 

Luckily I already was using some Vault 4.x license keys on the server, so was able to perform the upgrade of the server without the cost of purchasing new vault 4 licenses.

Answer 82

I upgraded my Vault Server to the latest release (4.1.4) and upgraded my Vault Client on my Win 7 x64 pc (that had the SQL Mgmt Studio problem) and everything is now working fine! 

No manual registry changes required, just install the latest vault client (which uninstalls the old client automatically, and fixes whatever the problem was). 

Luckily I already was using some Vault 4.x license keys on the server, so was able to perform the upgrade of the server without the cost of purchasing new vault 4 licenses.

Good news. I thought this may solve the issue as well so I installed 4.1.4 but it did not repair things for me :( Since the RTM for Win7's hit, I just re-did my entire box yesterday w/ the RTM. At least TFS Source control has all my source code, and Exchange has all my e-mail. Just had to save a few things off to network. Easy, but definitely a waste of a day.

Looks like SourceGear has some serious stuff to investigate if they want to be Win7 compatible!

Answer 83

I'm having the exact issue on Windows 7, but none of the recommendations have fixed it. 3 years and Microsoft can't stop it from happening?!?!?

Answer 84

I had this problem today and managed to fix it.  I kept getting the same error message when trying to run SQL Server 2008 Management Studio on Windows 7.  The message didn't start appearing until after installing another application using a .MSI that was apparently distributing something that conflicted with SQL Server 2008 Mangement Studio.

I used <a href="http://msdn.microsoft.com/en-us/library/aa370557(VS.85).aspx">Orca</a> to search the registry entries in the .MSI and found that the offending COM object {6D5140C1-7436-11CE-8034-00AA006009FA} was HHActiveX.dll and that the version that was being distributed in the .MSI did not match the version needed by SQL Server 2008 Management Studio.  Since I was the one who built the .MSI, I just removed the HHActiveX.dll from the installation altogether, recompiled the MSI, then installed it again on a restored version of WIndows 7 with a working copy of SQL Server 2008 Management Studio and it worked perfectly.  Anyway, I don't know if this will help anyone else, but I thought it might be useful to mention it.

Answer 85

This happend to me inside of SQL Server 2008 Management Studio (SSMS) running on Windows 7.  Not sure if this was related, but it was after installing VS 2005 and SQL Server 2005.  To fix it, I exported and imported the following out of my other W7 machine.

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]
@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

Answer 86

Thanks Sean. This was driving me mad!

I have VS 2008, SourceGear Vault 3.5, SQL Server Management Studio 2005 running on Windows 7. None of the previous fixes worked for me until I tried importing your registry entries.

Thanks again!

Answer 87

I'm running VS2008, SQL Server Management Studio 2005 and 2008 (both broken) on Windows 7 64-Bit.  None of these registry hacks worked for me, but here's what did:

1.  Install SQL Server

2.  Install the broken Vault Client (for me this was 4.0.6, what we use here at work).  This hosed my SQL-Server Object Explorer, both 2005 and 2008.

3.  Install the lastest Vault 4.x client (4.1.4 I believe).  This worked, and SQL-Server worked, but our Vault Server version wouldn't work with the 4.1.4 client.

4.  Uninstall the latest client using Add/Remove Programs.

5.  Reinstall the broken Vault Client (4.0.6) while leaving an instance of SQL-Server Management Studio open.  

Everything worked after doing this, and so far it's worked on two different boxes for me.  I don't know if leaving SQL-Server Management Studio open was a part of the solution or not, but I've lost like 2 working days to this problem and wasn't willing to try the steps I listed without it open.

Alternate Solution that also worked;

1.  Install Vault 

2.  Make a copy of the Program Files(x86)\Sourcegear\Vault Client folder

3.  Uninstall Vault using Add/Remove Programs

4.  Run Vault out of the copied folder.

This actually worked really well for me, but I couldn't integrate Vault into Visual Studio, but I don't usually run it that way anyway.  I had to figure out the first fix when a coworker upgraded to Windows 7 and he does use Vault in VS.

Hope this helps someone.  

---

Do not go gentle into that food fight

Answer 88

Woah. Thank you for this!

It never occurred to me that Vault client could be causing this since it had worked A-OK in XP and Vista.

I had installed Vault when installing my 64-bit Win 7 as per the normal routine of setting up my environment.
Today I tried if the SQL 2008 R2 CTP would bring any luck in regards to this problem - it didn't.

But then I noticed your post about a possible connection with Vault.

I simply uninstalled the Vault client and now SQL Manager works.
(I did have SQL manager open during uninstall. I am not sure if that helped)

Thank you!