Vault 4 client failed install

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
bnott
Posts: 28
Joined: Thu Feb 15, 2007 10:03 am
Contact:

Vault 4 client failed install

Post by bnott » Thu Jun 07, 2007 11:27 am

I am trying to install the vault client on my Windows XP SP2 machine with VS05.

I have rebooted, and all applications are closed.

I get the error:

Error 1722: There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

And then the whole install rolls back.

Anything I can do to get past this?

Brian

bnott
Posts: 28
Joined: Thu Feb 15, 2007 10:03 am
Contact:

Post by bnott » Thu Jun 07, 2007 12:01 pm

Its actually worse than that.

SQL Management Studio is not working now. The error is:

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 stack trace given by SSMS is all in the namespace "Microsoft.SqlServer.Management.UI.VSIntegration". So I have to assume, since this started happening immediately after the failed valut client install, that somehow the install has broken some COM registrations for Visual Studio that SSMS also requires.

Brian

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Jun 07, 2007 12:44 pm

Email me using the button below this post with your phone number, and I'll call you. We've never seen the client failing this badly before, so I want to make sure we get it straightened out.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Jun 08, 2007 2:01 pm

Follow up:

It seems that there was a problem with the 2.0 framework in the machine where the client install failed. After uninstalling and re-installing the 2.0 framework the client was install was successful.
Mary Jo Skrobul
SourceGear

Post Reply