IT SOLUTIONS
Your full service technology partner! 
-Collapse +Expand
DBA
Search DBA Group:

Advanced
-Collapse +Expand DBA Store
PRESTWOODSTORE

Prestwood eMagazine

September Edition
Subscribe now! It's Free!
Enter your email:

   ► KBSQL Servers   Print This    All Groups  
 
DBA SQL Servers:
SQL Server Nasty Crash - Vault?
 
Posted 10 years ago on 6/7/2011
Take Away:

The installation of the SourceGear Vault client control appears to trash SQL Server Management Studio and Visual Studio.

Here's the fix that worked for me.

KB102298

Thank God for Google!

This afternoon I had a rude awakening. I started SQL Server Management Studio and immediately received a most unwelcome 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: 080004002 (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)  

A Google search turned up scores of hits. Most blamed the installation of the SourceGear Vault client, but none were specific about how Vault had caused problems. 

When I attempt fixes I find via Google, my habit is to start with the simplest, most easily undone suggestions first.  In my case it took two of them:

The first was to get Vault "out of the way" without really getting rid of it. Make a copy of the vault installation folder, uninstall Vault, and from that point forward, launch the vault client from the copy folder. There is a downside: You'll probably not be able to integrate Vault with your IDE's version control features.  I can live with that.

That, along, didn't do the trick for me, but another simple suggestion did: Run SQL Server Management Studio as Administrator.  I used the Properties dialog of my SSMS shortcuts to specify Run as Administrator.

Bingo! Problem Solved.

Hindsight being 20/20 vision, if I had it to do over again, I would install the Vault client before installing SQL Server. I just have a hunch that would have prevented the problem in the first place.


Comments

0 Comments.
Share a thought or comment...
 
Write a Comment...
...
Sign in...

If you are a member, Sign In. Or, you can Create a Free account now.


Anonymous Post (text-only, no HTML):

Enter your name and security key.

Your Name:
Security key = P1283A1
Enter key:
KB Post Contributed By Wes Peterson:

Wes Peterson is a Senior Programmer Analyst with Prestwood IT Solutions where he develops custom Windows software and custom websites using .Net and Delphi. When Wes is not coding for clients, he participates in this online community. Prior to his 10-year love-affair with Delphi, he worked with several other tools and databases. Currently he specializes in VS.Net using C# and VB.Net. To Wes, the .NET revolution is as exciting as the birth of Delphi.

Visit Profile

 KB Article #102298 Counter
5718
Since 6/7/2011
Sales Website: www.prestwood.com Or visit our legacy sales site: 
legacy.prestwood.com


©1995-2021 Prestwood IT Solutions.   [Security & Privacy]