Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have an instance of SQL Server 2008 running on a Windows 2008 server. I am able to connect to this SQL server from several machines on my network. However, I cannot connect using SQL Management Studio on the SQL Server itself.

When I hit "Connect" I get this 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)). (Microsoft.VisualStudio.OLE.Interop)

Server config:

  • SQL Server 2005
  • Windows Server 2008 Std 32-bit
  • Also runs SQL Server 2000 on port 1444

I tried:

for %1 in (%windir%\system32*.dll) do regsvr32 /s %1

for %1 in (%windir%\system32*.ocx) do regsvr32 /s %1

  • Running regsvr32 actxprxy.dll, which produced an error

Any ideas?

Justin

share|improve this question
1  
Do you have Visual Studio installed too? Which version, I have seen this product cause problems with SQL Server 2008 Management Tools IF it was installed AFTER installing SQL Server 2008. –  Jeff May 21 '09 at 20:12
    
@JD - Thanks. I have SQL Server 2005 installed, not 2008. And I do have VS 2005 installed. –  Justin May 21 '09 at 20:34

2 Answers 2

up vote 2 down vote accepted

unregister actxprxy.dll then reregister it

run

regsvr32.exe –r c:\windows\system32\actxprxy.dll
regsvr32.exe c:\windows\system32\actxprxy.dll

run these in a command prompt as administrator

On Windows2008 server, the command for unregister is:

 regsvr32.exe /u c:\windows\system32\actxprxy.dll
share|improve this answer
    
No. SQL Server Management Studio 9 (which is 2005) –  Justin May 21 '09 at 20:42
    
Yah! Thanks. That did it. –  Justin May 21 '09 at 20:49
    
+1 Vote for a correct answer!:-) –  MarlonRibunal May 23 '09 at 7:56

Sounds like you need to do a repair on your SSMS on your server (if I'm understanding you correctly). I appears that the COM Interfaces need repaired/reinstalled.

-JFV

share|improve this answer
    
Modify the install from add/remove and remove. Then install workstation components if you don't see repair. –  Sam May 21 '09 at 19:43
    
I tried a repair on Native Client and 2005 itself. Neither worked. –  Justin May 21 '09 at 19:44
    
@Sam - Duh, right. Thanks. –  Justin May 21 '09 at 19:47
    
OK, that didn't work. Any other ideas? –  Justin May 21 '09 at 20:33

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.