Home Dashboard Directory Help
Search

SQL Server 2005 Management Studio on Windows 7 by ggreaves


Status: 

Closed
 as Won't Fix Help for as Won't Fix


2
0
Sign in
to vote
Type: Bug
ID: 504896
Opened: 10/28/2009 1:56:11 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

The error message is below. So far I have installed all Windows 7 updates, installed SQL SP3 tried the registry hacks in the Microsoft forums and manually tried registering the DLLs two of which does fails at point mshtml and shdocvw.

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.Navigab
Details
Sign in to post a comment.
Posted by Microsoft on 11/11/2010 at 12:12 AM
Hi ggreaves,

We're unable to reproduce this in our test environment. Please also consider using a new release of SSMS (2008 R2) as there are lot of enhancements and bug fixes that you can benefit from. Thanks!

Regards,
Deepak Ananth
Posted by ggreaves on 12/1/2009 at 4:05 AM
Hi Bill,

Our SQL setup is as follows:

Servers:
SQL Server 2005 64bit latest Sp and patches with SSMS installed on Windows Server 2003 64bit.

Client:
Windows 7 64bit with latest Sp and patches.

What happens:
When the SSMS is launched on Windows 7, there isn’t a problem. When I try to connect to the server the Object Explorer window dies. The first call stack is below.

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
------------------------------
It dies usually but sometimes, like today, you get that bit further. Probably because I restarted on this morning.
Once you clear the first error message you have to have to refresh the Object Browser to get the navigation tree symbol. I’ve managed to get one level down i.e. to see the Database, Security, etc folders. Expanding database folder any of those generates the call stack below and it dies. The other folders open without any problems and I can navigate further down.

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

If I hit the refresh button again, it completely kills the Object Explorer window. All you see is the word expanding... Call stack is the same as the ones above.
Posted by Microsoft on 11/30/2009 at 9:22 AM
Hi GGreaves,
Thank you for your updates regarding getting SSMS 2005 running against 2005 SP3. I have a follow up question for you. Did you have SSMS 2005 installed on the same server as the database? I'm putting together a repro environment and I want to make sure I get this right. My first inclination is to install SQL Server 2005 with SSMS in the same machine as the server and see how things work.
Thank you,
Bill Ramos
Posted by ggreaves on 11/9/2009 at 3:51 AM
More Windows 7 updates came down and the problem has not been fixed.
Posted by ggreaves on 11/9/2009 at 3:50 AM
Its the 2005 version with SP3. Now I'd say be very careful using SSMS 2008 to manage SQL 2005. I had to recover a corrupted test database after a developer installed SSMS 2008 on his machine and used it.
Posted by AaronBertrand on 10/30/2009 at 8:19 AM
What version of Visual Studio do you have installed? Have you considered using SSMS 2008 instead of 2005? You can still manage 2005 instances with a newer version of the tools (in addition to potentially avoiding this issue, you get a bunch of other bug fixes and enhancements as well).
Posted by ggreaves on 10/29/2009 at 7:25 AM
Just got more Windows updates. None of them resloved this issue.
Sign in to post a workaround.