August 22, 2014 at 3:12 am
Good morning,
On our SQL Server 2005 box when someone is connecting to the SQL Server Management Studio they are getting the below error message - but I don't.
I am however a domain admin on the domain and an admin on the SQL Server.
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)
The only thing I have done on this PC recently was upgrade from IE7 to IE8 I have also tried what this link recommends, but again it didn't work.
Running out of ideas as to why that particular user is getting the error, but I'm not.
Thanks
August 22, 2014 at 3:19 am
Quick thought, are the SSMS versions 2008 or later and could the backward compatibility be missing?
😎
August 22, 2014 at 3:45 am
Sorry not sure I understand you comment.
The server is Windows Server 2008 and SQL Server Management Studio information is below -
Microsoft SQL Server Management Studio - 9.00.4035.00
Microsoft Analysis Services Client Tools - 2005.090.4035.00
Microsoft Data Access Components (MDAC) - 6.0.6001.18000 (longhorn_rtm.080118-1840)
Microsoft MSXML - 3.0 6.0
Microsoft Internet Explorer - 8.0.6001.18702
Microsoft .NET Framework - 2.0.50727.3074
Operating System - 6.0.6001
August 22, 2014 at 3:56 am
If I remember correctly, there is a backward compatibility components option in the SQL install, seen this problem when trying to access earlier versions of SQL Server without having the components installed.
😎
August 22, 2014 at 4:22 am
But I don't get the error - wouldn't I get the error too if it was a compatibility issue?
The user who is getting the error appears to have never got the issue until I upgraded Internet Explorer to 8.
All they do is open the Management Studio in order to check that all our "Jobs" have run and they are presented with that error.
August 22, 2014 at 4:59 am
Guys - had to re-register a bunch of dlls. All now working. Thanks for your help.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply