Error 1722 during Fortress Installation

Ralkarin · Post by **Ralkarin** » Mon Oct 15, 2007 7:30 am

During the installation of the Fortress client I get the following 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."

The installer windows says "Configuring VS.NET IDE. This may take a long time. Don't cancel".

The file structure has been created at "C:\Program Files\SourceGear\Fortress Client" with all of the assemblies and things, but I don't see an install log. I checked my %TEMP% directory for a fortress_client install log, but can't seem to find one.

I have no instances of visual studio, CC.NET, or Vault running.

Visual Studio Professional Edition version: 8.0.50727.762 (SP .050727-7600) with SP 1, GhostDoc, Windows WF Extensions, and .NET 3.0 Dev Tools Orcas CTP installed.

Any suggestions to solve this?
Thanks!

lbauer · Post by **lbauer** » Mon Oct 15, 2007 8:31 am

What operating system are you trying to install the Fortress Client on?

The file structure has been created at "C:\Program Files\SourceGear\Fortress Client" with all of the assemblies and things.

Can you launch the Fortress Client? Does it throw any errors?

Ralkarin · Post by **Ralkarin** » Mon Oct 15, 2007 8:46 am

Windows XP Pro SP 2

Actually I can launch the Fortress Client without error (while the error dialog is up).

The problem is, after the error, it rolls back the installation so I lose the file structure and all of the assemblies. They exist while the error message is displayed, but it rolls back after I click OK.

Perhaps it's bailing on installing the Visual Studio add-ins, but the application installation goes through smoothly. If I fire up Visual Studio while the error box is displayed, I don't see any modules in the About dialog of Visual Studio and I don't have any integreated IDE to Fortress.

Ralkarin · Post by **Ralkarin** » Mon Oct 15, 2007 8:52 am

Here's something else I just noticed:

In my Application Event Viewer log, I see these two Errors:

Source: .NET Runtime 2.0 Error Reporting

Faulting application vsipclientcustomactions.exe, version 1.0.4.15848, stamp 46b74316, faulting module gdiplus.dll, version 5.1.3102.2180, stamp 4110968b, debug? 0, fault address 0x000929b8.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Source: MsiInstaller

Product: SourceGear Fortress Client -- 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. Action AddVsipKeys, location: C:\Program Files\SourceGear\Fortress Client\VsipClientCustomActions.exe, command: -I

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Ralkarin · Post by **Ralkarin** » Tue Oct 16, 2007 7:57 am

Here's some more information that may be useful.

I ran the installation and left the error box up so I could use the client and got the latest source code from the repository using the Fortress GUI Client. I then closed out the installer by clicking OK, which rolled back my install.

When I opened visual studio and tried to load the solution that is now under Fortress source control, I get the following dialog for every project (.csproj) it tries to open:

Unexpected error encountered. It is recommended that you restart the application as soon as possible.

Error: The parameter is incorrect.
File: vsee\lib\xfcstr\winstrw.cpp
Line number: 166

Here is a reference link from Rational ClearCase explaining that these warnings come from a bad integration between Visual Studio and the Fortress extensions through VSIP: http://www-1.ibm.com/support/docview.ws ... wg21267165

These facts, along with the fact that the error occured in "vsipclientcustomactions.exe" from my previous post lead me to believe that it is strictly a problem with the Visual Studio extension installation. I have no problems using the fortress client stand-alone after it has been installed (with the error dialog up of course).

Beth · Post by **Beth** » Tue Oct 16, 2007 8:03 am

Did you still have Vault installed on your machine? If so, uninstall Vault and then try the Fortress install.

abova · Post by **abova** » Tue Oct 16, 2007 8:20 am

Ok maybe I'm panicing, but we need to have both vault and fortress installed. I think all of us here do this. Do you think he can reinstall vault after he installs fortress?

Ralkarin · Post by **Ralkarin** » Tue Oct 16, 2007 8:25 am

EDIT: Yes, I did have Vault installed.

No dice. I tried uninstalling Vault, rebooting, and rerunning the installation but got the same result.

Beth · Post by **Beth** » Tue Oct 16, 2007 8:54 am

abova: Why would you need both Vault and Fortress? Is it a case of where one of your customers uses Vault or are you using both internally? Fortress has all the SCC capabilities that Vault does.

Technically, you could have both clients installed, but when there's a problem, getting one out of the picture can sometimes help in pinpointing the problem.

Ralkarin · Post by **Ralkarin** » Tue Oct 16, 2007 9:17 am

We use both clients right now because we have 2 source repositories and we haven't upgraded the other server yet (hopefully someday). But for the time being we still need to access the other Vault repository while having access to the Fortress repository on our other server...

That issue aside, I tried installing the latest version of Vault (4.0.4) and the installation bailed with the same exception when trying to configure Visual Studio IDE through VSIP.

Previously we were using 3.1.7 I think, so I reinstalled version 3.1.9 and it worked, giving me access to the Vault repository server.

Something with the visual studio integration is bailing...

Here is everything installed with Visual Studio from the About Box:

Microsoft Visual Studio 2005
Version 8.0.50727.762 (SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41120
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41120
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41120
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41120
Microsoft Visual J# 2005

Microsoft Visual Studio Tools for Office 77626-009-0000007-41120
Microsoft Visual Studio Tools for the Microsoft Office System

Microsoft Visual Web Developer 2005 77626-009-0000007-41120
Microsoft Visual Web Developer 2005

Microsoft Web Application Projects 2005 77626-009-0000007-41120
Microsoft Web Application Projects 2005
Version 8.0.50727.762

Microsoft Web Deployment Projects 2005 77626-009-0000007-41120
Microsoft Web Deployment Projects 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

Extensions for Windows WF
Windows Workflow Foundation Tools for Visual Studio

Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 (KB926601)
This service pack is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/926601

Orcas Technology Preview - .NET Framework 3.0 Development Tools 1.0
Microsoft Visual Studio Code Name Orcas Community Technology Preview - Development Tools for WinFX

Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB937061)
This Security Update is for Microsoft Visual Studio 2005 Professional Edition - ENU.
If you later install a more recent service pack, this Security Update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/937061

GhostDoc for Visual Studio 2005
For more information about GhostDoc, see the GhostDoc website
at http://www.roland-weigelt.de/ghostdoc
Copyright © 2003-2007 Roland Weigelt.

Beth · Post by **Beth** » Tue Oct 16, 2007 12:33 pm

It looks like this went offline for troubleshooting. We'll post back when resolved.

Ralkarin · Post by **Ralkarin** » Thu Oct 18, 2007 7:12 am

I wanted to follow up with the current status of my issue.

I attempted to uninstall and reinstall Visual Studio and the .NET framework 2.0 to see if this would solve this issue, but this caused a boatload of problems for my system. After doing some further research, it appears that my hard drive had bad sectors. Our IT Administrator ran some diagnostics and determined that my drive was indeed going bad.

Since then, I've installed Fortress successfully on a Windows Vista (!!!) desktop with VS2005 and have been using it quite successfully.

Thanks for all of the support from Sourcegear!

bclubb · Post by **bclubb** » Fri Oct 19, 2007 8:09 am

We had this same error with Fortress and Vault installed. The project had fortress bindings, but VS2005 was set to use vault. We changed to fortress and everything worked fine.

mcutter · Post by **mcutter** » Wed Nov 05, 2008 3:00 pm

I similarly got the error when trying to open a dbp
Error: The parameter is incorrect.
File: vsee\lib\xfcstr\winstrw.cpp

Turns out that the vs2008 source control plug-in had somehow gotten set to classic client.
Changing back to enhanced client allowed me to open the dbp without any problems.

Beth · Post by **Beth** » Thu Nov 06, 2008 1:29 pm

Thanks to everyone for the updates and good additional information. I'm sure other users will find this helpful.

SourceGear Support

Error 1722 during Fortress Installation

Error 1722 during Fortress Installation

Why uninstall Vault?

Fixed by changing the source provider

Re: Error 1722 during Fortress Installation

Re: Error 1722 during Fortress Installation