Home All Groups Group Topic Archive Search About

SQL Server Management Studio error on connection

Author
17 Mar 2006 12:29 AM
some guy
Hi,

Whenever I connect to a server, I get this error message:

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)

Also, nothing but the root server node appears in the Object Explorer, but
everything appears to be normal in the Summary window.

I'm connecting to a remote server with a SQL Login. I am running SSMS under
a local non-administrative account.

Thanks in advance!
Author
1 Apr 2006 9:00 AM
some guy
Can anyone help me with this?

Show quoteHide quote
"some guy" wrote:

> Hi,
>
> Whenever I connect to a server, I get this error message:
>
> 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)
>
> Also, nothing but the root server node appears in the Object Explorer, but
> everything appears to be normal in the Summary window.
>
> I'm connecting to a remote server with a SQL Login. I am running SSMS under
> a local non-administrative account.
>
> Thanks in advance!
Are all your drivers up to date? click for free checkup

Author
1 Apr 2006 9:30 AM
Erland Sommarskog
some guy (some***@discussions.microsoft.com) writes:
Show quoteHide quote
> Can anyone help me with this?
>
> "some guy" wrote:
>
>> Whenever I connect to a server, I get this error message:
>>
>> 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)
>>
>> Also, nothing but the root server node appears in the Object Explorer,
>> but everything appears to be normal in the Summary window.
>>
>> I'm connecting to a remote server with a SQL Login. I am running SSMS
>> under a local non-administrative account.

Apparently. something is abnormal on your machine, but what that would
be, I have no idea.

I will ask some questions, although I don't expect that the answsrs
would give me more clues. But maybe someone else get's an idea.

1) You say "whenever I connect to a server" - does this also include
   when you try to open a Query Window, or is it only when you connect
   to Object Explorer?

2) You say Summary works OK, only Object Explorer is wacko. Does this
   mean that you after all manages to connect?

3) Which operating system (including service pack) are you using?

4) Which edition of SQL Server are you using?

5) Do you have Visual Studio installed on the machine as well? In such
   case which version(s) of Visual Studio?

6) Do you know if you have made any manual edits to the registry?

7) Did you ever have a beta version of SQL Server or Visual Studio 2005
   installed?

8) If you search for 6D5140C1-7436-11CE-8034-00AA006009FA in the
   registry, do you find it? You should find an entry that has two
   subkeys: NumMethods and ProxyStudClsid32.

9) If you find it, do you also find {B8DA6310-E19B-11D0-933C-00A0C90DCAA9}
   with an InProcServer32 in System32\actxprxy.dll?

The one suggestion I can give at this point is to try to repair the
installation, possibly by uninstalling and reinstalling.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
1 Apr 2006 9:58 AM
some guy
It seems you just replying to my question fixes the problem :D.

The only change I made that I think could have affected it (can't remember
when I did it, it could have been before I reported this issue) was
installing SQL Server itself locally - before, I was connecting to a remote
server. It seems that it is now working OK for both local and remote
connections.

Thanks for your help!
Author
1 Apr 2006 6:13 PM
Erland Sommarskog
some guy (some***@discussions.microsoft.com) writes:
> It seems you just replying to my question fixes the problem :D.
>
> The only change I made that I think could have affected it (can't
> remember when I did it, it could have been before I reported this issue)
> was installing SQL Server itself locally - before, I was connecting to a
> remote server. It seems that it is now working OK for both local and
> remote connections.

Weird. I guess that by installing the engine, you also repaired whatever
that was broken.

I very glad to hear that you got it working!


--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Bookmark and Share