none
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
    Sunday, October 30, 2005 12:43 AM

Answers

  • Okay, I have tried everything on this thread, without success. Installed, uninstalled I don't know how many times.
    For those you who have installed Sourcegear Vault at any point, check out this link:
    http://support.sourcegear.com/viewtopic.php?f=5&t=12680&p=52790&hilit=management+studio#p52790

    The following worked for me:

    regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"

    if you are running 64 bit windows, try this:

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    I'm still having some weird Windows 7 issues due to something that Vault caused, (explorer windows open in a new window everytime, but I'm going to try nuking my profile and starting again.

    HTH,

    Mark


    Tuesday, December 08, 2009 1:53 PM
  • 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.

    • Proposed as answer by Twheet Tuesday, May 12, 2009 9:28 PM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:23 AM
    Monday, May 11, 2009 1:05 PM
  • 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
    Wednesday, November 02, 2005 6:49 PM
  • 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
    Friday, September 18, 2009 3:55 PM
  • This worked for me on Win7 Professional 64-bit

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
    Monday, February 01, 2010 7:03 PM
  • Try removing ie8 http://support.microsoft.com/kb/957700
    This worked on a win 2k8 A/P cluster running sql 2008
    • Proposed as answer by TPaling Monday, May 18, 2009 11:45 AM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:23 AM
    Tuesday, May 12, 2009 9:30 PM
  • 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
    • Proposed as answer by hkarthik Tuesday, December 01, 2009 7:01 PM
    • Marked as answer by Kalman TothEditor Wednesday, December 02, 2009 7:59 PM
    Saturday, May 30, 2009 9:08 AM
  • 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}"

    • Proposed as answer by PaulTubb Thursday, September 10, 2009 9:38 AM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:22 AM
    Wednesday, September 09, 2009 8:38 PM
  • 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!
    Thursday, November 05, 2009 11:36 AM
  • I am running Win7 HP 64-bit, VS 2008 SP1, and SQL DEV 2008 SP1.  I also have SourceGear Vault Client 3.5.  Crazy it conflicted.

    I made a copy of my Vault Client folder...then uninstalled it from Program Files (x86).  As soon as I did this my SSMS browsing worked again.  I then copied the Vault Client folder back into Program Files (x86)...created a shortcut on my Taskbar and everything works.

    Thanks fr0man and Jan for your comments!  I am happy to have this working.  ~Jarom

    Wednesday, November 18, 2009 10:52 PM
  • I finally figured out that the Vault client was the problem. I'm now running in an XP virtual machine.
    Thomas Derenthal
    Thursday, November 19, 2009 3:47 PM

  • I have similar problem as above. Having a form open in vb2008 and then select "Data", select "add new data source", select   "Choose your database objects"  it come back with the following error an error has occured while retrieving the information from the database.

    "Unable to cast Com object of type 'System_comObject' to interface type 'Microsoft.visualStudio.OLE.Interop.IserviceProfider'  This operation failed because the QueryInterface call on the COM component for the interface with IID'{6D5140C1-7436-11CE-00A006009FA}' failed due to the following error: No such interface suppoerted( Exception from HRESULT:0x80004002(E_nointerface)).

     

    I am running windows 7 professional. Sql 2008 express sp1.

    I have tried all the above suggestions and none of them fixed the problem. I don't know anything about a Vault Client and can't find it on the system. I also installed the new vb2010 beta but that comes back with the same problem when trying to make a new connection as above.

    Any help would be most welcome

    Just some additional information:  I installed vb2008 express on windows xp mode under Windows 7 same machine,  and it works fine under XP Mode

    Solved problem. Reinstalled windows 7 "upgrade" and now working fine

     

    Monday, November 30, 2009 8:14 AM
  • I too found SSMS broken with the same error after installing VS2008 and VAULT.   Uninstalling VS2008 didn't fix it.   I read your post, and uninstalled Vault client (3.1.8) and presto!   SSMS was back in business again.

    Thanks!
    Order Processing Technologies
    Friday, January 15, 2010 6:48 PM
  • Thanks Mark! Re-registering ieproxy.dll worked for me. 
    Wednesday, March 31, 2010 3:12 AM
  • Hey it worked for me.Actualy i am using x64 OS i used ThirdParty Uninstaller to uninstall IDM and accedently i removed few registry using that uninstaller from that point my x86 IE was not working as well as the subjected issue caused.

    Thank you for help Mark.

     

    -----Mukesh------

     

     

     

    Tuesday, January 04, 2011 12:15 PM
  • Vault hosed mine, too, and the regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll" fixed it.  Thanks!
    Tuesday, January 18, 2011 8:42 PM

All replies

  • 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()

    Tuesday, November 01, 2005 5:27 PM
  • 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
    Wednesday, November 02, 2005 6:49 PM
  • Thanks a lot! Nick, that appears to have fixed the problem.
    Wednesday, November 02, 2005 7:01 PM
  • 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.
    Friday, November 18, 2005 10:29 PM
  • 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
    Friday, November 18, 2005 10:43 PM
  • Perfect, that did it. Thanks!
    Friday, November 18, 2005 10:46 PM
  • Solved my problem with Team System as well as Sql Server 2005. 

    Thanks Nick.  Lifesaver.

    Tuesday, November 29, 2005 6:37 PM
  • I have no words to thank you enough!!

    It worked flawlessly.

    You saved me lots of headaches.

    -- EduQuint

    Tuesday, December 13, 2005 9:26 PM
  • 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)

     

    Saturday, February 04, 2006 10:39 PM
  • 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,

     

    Tuesday, February 07, 2006 11:35 AM
  • Did not help me. I checked reg and made sure everything is there. But I still get the same problem. Please help!
    Wednesday, February 08, 2006 5:56 PM
  • 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.
    • Proposed as answer by Andrew GR Wednesday, February 11, 2009 1:19 AM
    Friday, May 05, 2006 9:18 PM
  • Thank - You, registering the actxprxy.dll fixed the error for me :)
    Tuesday, May 16, 2006 1:57 AM
  • Thank you so very much.  This fixed my problem.

    John
    Tuesday, May 23, 2006 1:02 PM
  • 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...

     

     

    Monday, June 19, 2006 12:28 PM
  • 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

    Tuesday, June 27, 2006 9:28 PM
  • 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
    Tuesday, June 27, 2006 9:35 PM
  • 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.

    Tuesday, June 27, 2006 10:55 PM
  • 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

    Tuesday, June 27, 2006 11:41 PM
  • 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

    Wednesday, June 28, 2006 1:15 PM
  • Thanks Nick!  Maybe one day I can return the help?!  I really appreciated your help.  Sanford
    Wednesday, June 28, 2006 1:40 PM
  • Nick, you're the man. Thanks
    Tuesday, August 01, 2006 12:30 PM
  • 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.....

    Monday, August 07, 2006 9:23 PM
  • 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

    Thursday, August 17, 2006 12:58 PM
  • WOW - it worked for me, and now my SQL Server Mgmt Studio is faster than ever! 

    Thanks Nick!
    Friday, October 06, 2006 9:34 PM
  • 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?

    Thursday, October 19, 2006 2:26 PM
  • 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!

     

    Friday, October 20, 2006 3:31 AM
  • This was really helpful. Solved my problem. Thanks a lot
    Monday, November 13, 2006 7:54 PM
  • Thanks Nick... You da man :)
    Thursday, November 16, 2006 5:27 PM
  •  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.
    Sunday, November 26, 2006 8:46 PM
  • This was perfect! Thanks for the information.
    Thursday, December 14, 2006 6:52 PM
  • 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

    Sunday, January 07, 2007 4:46 PM
  • 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)).
    Tuesday, January 23, 2007 8:21 PM
  • 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.

    Friday, March 02, 2007 9:19 PM
  • C:\WINDOWS\system32>regsvr32 actxprxy.dll fixed mine too. Thanks a bunch!
    Wednesday, April 04, 2007 6:14 AM
  • This worked well.  Thanks a million.

    Babu

    Thursday, April 26, 2007 2:22 AM
  • Thanks, the regestration worked for me no issues.

     

    Thanks !!!

    Thursday, June 07, 2007 6:08 PM
  • Re-registering actxprxy.dll fixed the problem. Thanks a lot!
    Tuesday, June 19, 2007 6:43 PM
  • 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
    Thursday, June 28, 2007 10:00 AM
  • 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()

    Sunday, July 08, 2007 4:04 PM
  • Thanks! - That worked beautifully!

     

    Mike

    Wednesday, July 11, 2007 9:14 PM
  • 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}"

    Friday, July 13, 2007 3:21 PM
  • 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.

    Friday, July 13, 2007 3:47 PM
  • This helped me as well. Thanks a lot!

     

    Friday, August 10, 2007 4:45 PM
  • this doesn't solve my problem. merge process is successful but i'm still having the same error Sad

     

    Sunday, September 23, 2007 3:02 PM
  • I solved my problem by using late binding Smile maybe(I hopeSmile ) it helps you, too.

    Thursday, September 27, 2007 3:34 PM
  • 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
    Tuesday, October 02, 2007 3:16 PM
  • me too.

    Thanks all for the .reg and .dll fix!!!
    Thursday, October 04, 2007 1:32 AM
  •  

    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.
    Tuesday, October 09, 2007 8:30 AM

  • Thanks for this solution.  The registry part above didn't fix it for me,  re-registering seems to have worked.  Thanks for this advice.
    Wednesday, November 07, 2007 11:24 PM
  • 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.

     

    Monday, March 03, 2008 9:28 AM
  • 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
    Wednesday, March 26, 2008 12:08 AM
  •  

    I am receiving this error and none of the fixes have worked. I am running Windows XP 64-bit.
    Wednesday, May 07, 2008 8:01 PM
  •  

    Sorry please disregard.
    Wednesday, May 07, 2008 8:10 PM
  • 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?

     

    Friday, May 09, 2008 3:24 PM
  •      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)

    Wednesday, June 18, 2008 1:49 PM
  • Thx for the hint!!

     

    Been trying for hours!

    Thursday, August 07, 2008 11:12 AM
  • 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

    Tuesday, September 09, 2008 9:59 AM
  • If you are running a 64-bit OS, you will need to run register the dll, but under C:\Windows\SysWOW64!

    </hugeheadache>
    Wednesday, September 10, 2008 3:46 PM
  • Thank you very much.
    Saturday, October 18, 2008 4:42 PM
  • 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
    Friday, October 24, 2008 4:34 PM
  • 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
    Tuesday, November 25, 2008 6:14 AM
  • 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. :)
    Tuesday, March 24, 2009 2:40 PM
  • 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
    Monday, April 06, 2009 12:09 PM
  • 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.

    • Proposed as answer by Twheet Tuesday, May 12, 2009 9:28 PM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:23 AM
    Monday, May 11, 2009 1:05 PM
  • Try removing ie8 http://support.microsoft.com/kb/957700
    This worked on a win 2k8 A/P cluster running sql 2008
    • Proposed as answer by TPaling Monday, May 18, 2009 11:45 AM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:23 AM
    Tuesday, May 12, 2009 9:30 PM
  • 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!
    Monday, May 18, 2009 11:48 AM
  • 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
    Wednesday, May 27, 2009 12:01 PM
  • 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
    ------------------------------

    Thursday, May 28, 2009 4:39 AM
  • 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
    Saturday, May 30, 2009 8:18 AM
  • 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
    • Proposed as answer by hkarthik Tuesday, December 01, 2009 7:01 PM
    • Marked as answer by Kalman TothEditor Wednesday, December 02, 2009 7:59 PM
    Saturday, May 30, 2009 9:08 AM
  • 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!
    Tuesday, June 02, 2009 6:29 PM
  • 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
    Tuesday, June 02, 2009 6:52 PM
  • 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

    Wednesday, June 03, 2009 5:48 PM
  • 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!


    Thursday, June 11, 2009 9:00 PM
  • 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.
    Saturday, June 13, 2009 3:34 PM
  • 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 --
    Saturday, June 13, 2009 6:21 PM
  • I had this problem after just installing Access 2007.  Everything was fine (SQL2005 and VS2008), until then.

    Thanks for the fix!
    Tuesday, June 23, 2009 11:00 PM
  • 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
    Tuesday, July 28, 2009 6:16 AM
  • 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 :(
    Tuesday, July 28, 2009 1:19 PM
  • 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.
    Wednesday, July 29, 2009 4:14 AM
  • 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!
    Wednesday, July 29, 2009 12:36 PM
  • 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?!?!?
    Tuesday, August 11, 2009 12:22 AM
  • 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.
    Thursday, August 27, 2009 10:10 PM
  • 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}"

    • Proposed as answer by PaulTubb Thursday, September 10, 2009 9:38 AM
    • Marked as answer by Kalman TothEditor Friday, November 20, 2009 8:22 AM
    Wednesday, September 09, 2009 8:38 PM
  • 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!
    Thursday, September 10, 2009 9:39 AM
  • 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
    Friday, September 18, 2009 3:55 PM
  • 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!
    Thursday, November 05, 2009 11:36 AM
  • I have the same problem. I am running Win7/SQL Server 2008/VS2008-SP1. NOTHING WORKS! NOTHING! I can not work. Not re-registering actxprxy.dll. Nothing. Nothing in any blog or MSDN or anything I have found works. Not merging the  keys from your answer. I have a lot of expensive and useless software on my desk.
    Thomas Derenthal
    Monday, November 09, 2009 8:15 PM
  • I have the same problem. I am running Win7/SQL Server 2008/VS2008-SP1. NOTHING WORKS! NOTHING! I can not work. Not re-registering actxprxy.dll. Nothing. Nothing in any blog or MSDN or anything I have found works. Not merging the  keys from your answer. I have a lot of expensive and useless software on my desk
    Thomas Derenthal
    Monday, November 09, 2009 8:16 PM
  • I am running Win7 HP 64-bit, VS 2008 SP1, and SQL DEV 2008 SP1.  I also have SourceGear Vault Client 3.5.  Crazy it conflicted.

    I made a copy of my Vault Client folder...then uninstalled it from Program Files (x86).  As soon as I did this my SSMS browsing worked again.  I then copied the Vault Client folder back into Program Files (x86)...created a shortcut on my Taskbar and everything works.

    Thanks fr0man and Jan for your comments!  I am happy to have this working.  ~Jarom

    Wednesday, November 18, 2009 10:52 PM
  • I finally figured out that the Vault client was the problem. I'm now running in an XP virtual machine.
    Thomas Derenthal
    Thursday, November 19, 2009 3:47 PM
  • SeanJ_2173,


       Thanks for this, it fixed the problem for me! 

    -Brian
    Thursday, November 19, 2009 10:07 PM
  •  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.


    The following Microsoft Support kb deals with this issue: "By default, SQL Server 2005 and earlier Setup creates the BUILTIN\Administrators login, and then adds the login to the "Sysadmin" fixed server role. This change grants system administrator permissions to any account in the Local Administrators group. In some environments, you might want to impede Microsoft Windows system administrators from having this kind of access to SQL Server."
    Kalman Toth, SQL Server & BI Training, SSAS, SSIS, SSRS; http://www.SQLUSA.com
    Friday, November 20, 2009 3:08 PM
    Answerer
  • 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.

    Thanks so much, i did it and my problem was be resolved.
    Monday, November 30, 2009 3:32 AM

  • I have similar problem as above. Having a form open in vb2008 and then select "Data", select "add new data source", select   "Choose your database objects"  it come back with the following error an error has occured while retrieving the information from the database.

    "Unable to cast Com object of type 'System_comObject' to interface type 'Microsoft.visualStudio.OLE.Interop.IserviceProfider'  This operation failed because the QueryInterface call on the COM component for the interface with IID'{6D5140C1-7436-11CE-00A006009FA}' failed due to the following error: No such interface suppoerted( Exception from HRESULT:0x80004002(E_nointerface)).

     

    I am running windows 7 professional. Sql 2008 express sp1.

    I have tried all the above suggestions and none of them fixed the problem. I don't know anything about a Vault Client and can't find it on the system. I also installed the new vb2010 beta but that comes back with the same problem when trying to make a new connection as above.

    Any help would be most welcome

    Just some additional information:  I installed vb2008 express on windows xp mode under Windows 7 same machine,  and it works fine under XP Mode

    Solved problem. Reinstalled windows 7 "upgrade" and now working fine

     

    Monday, November 30, 2009 8:14 AM
  • After trying everything in this thread and having no luck on Win 7 RTM x64 ultimate with SQL Server 2005, I tried this simple fix and it finally worked!
    Tuesday, December 01, 2009 7:01 PM
  • I have tried the actxprxy.dll fix and the registry hack.  Neither work.  I do not have the Vault software also mentioned in this post and others.  What will fix this problem?
    Wednesday, December 02, 2009 7:46 PM
  • Anybody at MSFT paying attention? The problem goes back over 4 years now. There is no single fix, and it seems to be affecting a lot of developers with various configurations. This isn't just an annoyance, it is a full-on productivity killer. It kept me from getting anything done for the better part of a week. Mybe someone at MSFT knows how to program the high-speed digital computers on the internets?
    Thomas Derenthal
    Wednesday, December 02, 2009 7:54 PM
  • Anybody at MSFT paying attention?
    Thomas Derenthal

    Thomas,

    You can get Microsoft database engine staff attention by submitting bug/suggestion at:

    https://connect.microsoft.com/SQLServer?wa=wsignin1.0

    Let us know what happens.
    Kalman Toth, SQL Server & BI Training, SSAS, SSIS, SSRS; http://www.SQLUSA.com
    Wednesday, December 02, 2009 7:57 PM
    Answerer
  • Hey, I get it. You're marking everything as the answer. None of them worked for me, as is the case for a few others in this thread. The only solution that worked for me was to run SourceGear Vault client in an XP machine - not an ideal solution.
    Thomas Derenthal
    Wednesday, December 02, 2009 8:02 PM
  • I have the same problem of you. I tried most of the solutions proposed in this topic with no success:

     - Unregister and register again the actxprxy.dll (inside Windows\WoW64, once my system is x64)
     - To merge the two .reg files proposed (one at a time, and both failed to solve the issue)
     - Run SSMS as an administrator
     - Repair instalation of SQL Server

    I didn't try these:

     - Uninstall IE8 (because I want to use IE8)
     - Uninstall the Vault client (because I don't know what the ____ that is...)


    I am trying to manage my SQL Server remotely using the SSMS.

    The client machine is:

    Windows 7 Professional x64 (en-us) Build 7600 (genuine and updated)
         .NET Framework 3.5 SP1
         Visual Studio 2008 Professional Edition SP1

    The server machine is:

    Windows Server 2008 x86 (en-us) with SP2 Build 6002 (genuine and updated)
         .NET Framework 3.5 SP1
         SQL Server 2008 Developer Edition (en-us)


    Important:
    1. I don't have problem accessing and managing the SQL Server locally, the issue only happens in the SSMS when I execute it in the client machine;
    2. I had the same problem with SQL Server 2008 Express x64 (en-us, with or without SP1)  and SQL Server 2008 Developer Edition in x64 (en-us, with or without SP1) when I installed then in the client machine. That's why now I am trying to access the database remotely;

    I don't know if this is important:
    1. I am connecting to the server using TCP/IP;
    2. SQL Browser is running;

    Here is the error report:

    ***************************************************************************************************************************

    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.RootNavigableItem.GetService(Type serviceType)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NodeContext.GetService(Type serviceType)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.<GetColumnsFromNavigationService>d__0.MoveNext()
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.GetMinimumColumnList(INodeInformation source, Dictionary`2& allValidColumns)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.GetFields(INodeInformation source)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.GetChildren(IGetChildrenRequest request)
       at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)

    ****************************************************************************************************************************

    It was caught immediately after the connection had been established. It also happens when I try to navigate in the databases of the SQL Server instance.


    Okay, I hope I had give you enough information.

    Could someone please guide me to a solution? I would really appreciate.

    And sorry if I have committed some english mistakes. I am still learning...


    Regards, Felipe Aburaya.
    Sunday, December 06, 2009 3:57 AM
  • Okay, I have tried everything on this thread, without success. Installed, uninstalled I don't know how many times.
    For those you who have installed Sourcegear Vault at any point, check out this link:
    http://support.sourcegear.com/viewtopic.php?f=5&t=12680&p=52790&hilit=management+studio#p52790

    The following worked for me:

    regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"

    if you are running 64 bit windows, try this:

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    I'm still having some weird Windows 7 issues due to something that Vault caused, (explorer windows open in a new window everytime, but I'm going to try nuking my profile and starting again.

    HTH,

    Mark


    Tuesday, December 08, 2009 1:53 PM
  • I too found SSMS broken with the same error after installing VS2008 and VAULT.   Uninstalling VS2008 didn't fix it.   I read your post, and uninstalled Vault client (3.1.8) and presto!   SSMS was back in business again.

    Thanks!
    Order Processing Technologies
    Friday, January 15, 2010 6:48 PM
  • Hello again, four years later.

    I have an addin for Outlook, and when Outlook tries to show calendar view, this message appears:

    "Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Interop.Outlook.CalendarView'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{00063099-0000-0000-C000-000000000046}' failed due to the following error: Interfaz no compatible (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))."

    I've tried to re-register ieproxy.dll and actxprxy.dll
    I've reinstalled Outlook and the addin.

    I've used the CCleaner tool to clean the whole registers.

    What else can I try?

    Thanks a lot.
    Tuesday, January 26, 2010 8:54 AM
  • This worked for me on Win7 Professional 64-bit

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
    Monday, February 01, 2010 7:03 PM
  • Thanks Mark! Re-registering ieproxy.dll worked for me. 
    Wednesday, March 31, 2010 3:12 AM
  • Thanks Mark,

     

    This worked for me. I was desperately looking for a solution for this frustrating issue.

     

    Abdalla

    Saturday, May 01, 2010 2:13 PM
  • Thanks! That is the only fix that worked for me.

    Win7 x64, VS2010, SQL 2008 R2 x64

    Wednesday, June 02, 2010 5:59 PM
  •  We had a few reports from SourceGear Vault/Fortress version control users who were encountering this error when using an earlier version of our software:

    http://support.sourcegear.com/viewtopic.php?f=5&t=12680&p=52790&h

    Running this command should fix the problem:

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    Contact support at sourcegear.com if you continue to experience the error.

    Note that Vault 4.x and earlier versions are not supported on Windows 7, Windows 2008 or VS 2010.

    The latest release, Vault 5.x is fully supported on Windows 7 and Windows 2008, SQL Server 2008 and VS 2010. We have not had any reports of the COM error in the latest version, which was released a year ago.

     

    Wednesday, June 09, 2010 4:45 PM
  • It was uninstalling Vault (not sure what version, but pre 4.x) that caused this problem for be. Running

    regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"

    fixed the problem (I'm on a 32-bit machine, rather than a 64-bit which the command line above assumes).

    Tuesday, June 29, 2010 10:58 AM
  • worked for me

    Thanks

    Wednesday, September 29, 2010 6:01 PM
  • I had the error:

    Object reference not set to an instance of an object. (AppIDPackage)Microsoft.SqlServer.Management.UI.VSIntegration.AppIDPackage.AppIDPackage.ConnectToOe()

    SSMS would fail to load the server/object explorer.

    This happened on my Windows Server 2008 x64 system after manaully installing the Visual Studio profiler and then mucking with various things to try and repair something that broke as a result of the installation.

    I tried the following but none helped:

     - Unregister and register again the actxprxy.dll (inside Windows\WoW64, once my system is x64; also tried the system32 version)
     - To merge the two .reg files proposed (one at a time, and both failed to solve the issue)
     - Run SSMS as an administrator
     - Uninstall/Reinstall SQL Server

    The fix that ended up working was the following.  Use at your own risk!

    *First*, uninstall SQL Server

    cd c:\windows\assembly

    del /s *sqlman*

    del /s *sqlmgmt*

    del /s *microsoft.sql*

    Reinstall SQL Server

    • Proposed as answer by Kris Ganjam Wednesday, November 24, 2010 7:20 AM
    Wednesday, November 24, 2010 7:20 AM
  • Hey it worked for me.Actualy i am using x64 OS i used ThirdParty Uninstaller to uninstall IDM and accedently i removed few registry using that uninstaller from that point my x86 IE was not working as well as the subjected issue caused.

    Thank you for help Mark.

     

    -----Mukesh------

     

     

     

    Tuesday, January 04, 2011 12:15 PM
  • Vault hosed mine, too, and the regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll" fixed it.  Thanks!
    Tuesday, January 18, 2011 8:42 PM
  • I am on Windows 2008 R2 Enterpeise and suddenly SQL 2008 gave me the same error :- running the command below got it all worlking again.

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll

    Cheers
    Gregor

    Thursday, April 14, 2011 7:51 AM
  • Thanks. This did the trick,
    Thursday, May 05, 2011 9:50 AM
  • 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

    Wednesday, May 11, 2011 9:27 PM
  • hi Norm

                     runninng SSMS as an administrator worked for me . thank  you

    Wednesday, June 08, 2011 6:17 PM
  • Bingo! Thanks for the help - the command you listed for 64 bit windows did the trick for me.
    Wednesday, June 22, 2011 1:54 PM
  • Thanks, Scott!  This worked perfectly for me.  IE 9 was just loaded on my system lately and it must have killed the registry setting.
    Friday, July 22, 2011 3:26 AM
  • 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

    Thank you very much for that hint. For me this solved the problem also!!!
    Friday, July 22, 2011 9:17 AM
  • Solution can be found at this link ....

     

    http://www.davidmoore.info/2009/08/19/solution-explorer-open-each-folder-in-same-window-error-and-sql-management-studio-ie-and-team-explorer-errors/comment-page-3/#comment-3601


    DA
    • Proposed as answer by KuduHunter Tuesday, July 26, 2011 2:59 AM
    Tuesday, July 26, 2011 2:59 AM
  • Oi people

    Today install the software GED for studing in my machine and for coincidence my SQL SERVER 2008 R2 Express beginning this error.

    This article help me to resolve this problem.

    I execute regsvr32.exe /u actxprxy.dll and regsvr32.exe actxprxy.dll, after register the dll the SQL Server Management returned to work.

    I used Windows XP, service pack 3, SQL Server 2008 R2 Express

    Thank you for help.

     

    Thursday, August 11, 2011 12:43 AM
  • Okay, I have tried everything on this thread, without success. Installed, uninstalled I don't know how many times.
    For those you who have installed Sourcegear Vault at any point, check out this link:
    http://support.sourcegear.com/viewtopic.php?f=5&t=12680&p=52790&hilit=management+studio#p52790

    The following worked for me:

    regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"

    if you are running 64 bit windows, try this:

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
     

     

    This worked for me!!! Thank You :)

     

    Wednesday, September 21, 2011 1:27 PM
  • Encountered the problem on XP SP3. Solution worked like a charm.
    Tuesday, November 22, 2011 8:36 AM
  • This regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll" worked for me with Windows 2008_R2 and SQL2008_R2 Thank you.
    Friday, March 02, 2012 1:20 PM
  •            I am using Windows 7 Pro. Got into this issue after installing Source Gear version 3.5.2

               The folders not opening in the same window issue went away after updating the registry keys as per this post.

    http://support.sourcegear.com/viewtopic.php?f=5&t=12332

               The issue with the SSMS explorer throwing error went away along with the "No Interface Found error" while deploying mobile project  in VS2008 after following this post.

    http://support.microsoft.com/kb/2517589

               Please do not forget to RESTART the OS after applying each of the above fixes.

    Saturday, April 07, 2012 6:17 PM
  •  Thanks a lot !!

    I am using Windows 7 Professional With SQL2008. I am not using Vault.

    regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"

    This tweak worked for me. Now SQL is back in business. Thanks !!! :)

    Wednesday, May 16, 2012 4:31 AM
  • Same problem.  Following tips from the answers here solved it:

    Uninstall Vault

    regsvr32 /u "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    Install Vault

    The Vault people should be notofied about this.

    Tuesday, May 22, 2012 11:35 AM
  • On a lovely morning my management studio started to do the same... Nothing has helped from the solutions here. What did help though was installing SQL 2008 SP3 :S
    Thursday, June 21, 2012 2:12 PM
  • 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.

     

    Perfect ... I tried every thing mentioned here ... only this worked out !

    Thanks a lot .

    Friday, July 20, 2012 11:47 PM
  • Thank you so much for the solution.

    In my case non of the solution worked for me in this thread.

    Here was my original scenario.

    Everything was working fine when i ran/tested a registry cleaner software named "Registry Kit". I had to test each of its features one of which was "Privacy Cleaner" which cleaned out something when a specific web browser was selected such "AOL Explorer", "IE", Mozilla Firefox, "Netscape Navigator".

    After this, SQL Server Management studio started giving this error (as mentioned by several people above) while attempting to browse SQL Server 2008 R2 databases. The applications depending on the database kept working fine though.

    I performed an SQL Server 2008 R2 repair install but nothing changed.

    Finally i ran this command (thinking that maybe IE /Privacy Cleaner had something to do with my problem)

    regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

    (I have a Windows 7 Ultimate x64 based system)

    and the problem went away instantly!

    MY problem might have also solved if i had done a repair install of my Windows OS but then i would have never known what was the problem and what caused it. I am happy that i know that now and maybe the above scenario may help someone else too!.

    Thanks


    ~~ A man's dreams are an index to his Greatness ~~

    Tuesday, August 21, 2012 10:09 PM
  • Thanks Mark Hickin!!!...

    This works for me: regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"
     

    Friday, August 24, 2012 10:39 PM
  • This works for me: regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll"
    Wednesday, September 05, 2012 10:49 AM
  • Thank you to the 10th power!  This fixed my problem.
    Thursday, September 20, 2012 3:10 PM
  • Please specify exactly what solved your problem when thanking.

    Thanks.


    Kalman Toth SQL SERVER 2012 & BI TRAINING
    New Book: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012

    Thursday, September 20, 2012 6:40 PM
    Answerer