SourceGear Support

Is the client install only failing on your machine? Are there any differences in the setup of the machines that succeed and your machine? Is there a Vault_client_install.log file in your %temp% directory? If so, does it have any more information about the error? The machine keys on Vista are in (sor...

The installer uses WMI to create virtual directories in IIS and that is failing for some reason. Errors like that usually indicate a problem with IIS. Try re-installing IIS. You may need to re-install the .NET 2.0 framework after re-installing IIS also.

Verify that the following files that are needed for the client custom actions are in the client folder when you get the error message: VaultVsipRegistry64.xml VaultVsipRegistry64_9.xml VaultVsipRegistry.xml VaultVsipRegistry_9.xml FortressConnectionRegistry64.xml FortressConnectionRegistry64_9.xml F...

We are still trying to reproduce this. Can you send me the fortress_install.log located in your %temp% directory? That way I can see exactly how you installed the server so we can choose the same options as you did and also see if there were any problems reported. You can send it to maryjo at source...

So far we haven't been able to reproduce this in house. The existing permissions remain unchanged after the install on the machines we have tested. How are you logged onto the machine during the install process (as "Administrator" or as another user)? Is this an upgrade from a previous ver...

We will look into it. I just need a little more information.

Did you install the Client or Server (or both) on that machine? Is this Fortress 1.1.1?

What operating System are you using?

Note that unlike IIS <= 6, IIS 7 can run 32-bit and 64-bit programs simultaneously. The fact that the Vault server is currently a 32-bit application shouldn't necessarily hold you back from moving to Windows Server 2008. Each App Pool in IIS 7 can be set to allow 32-bit applications (or not). The 4....

Adding items via email is already on our list of feature requests. I will had your vote. Many of our users have written their own program to parse email and add items to Fortress using either the WebService or the Fortress API. For Fortress, we recommend using the API for programming any additional ...

That is very weird. I will log a bug. Thanks for the report. It doesn't seem to happen on the query page when you are "inside" a project.

I have just been informed that older versions of the installer would remove some of the default page values on uninstall :oops: , so if you had an older version of Vault installed that explains your issue. The newer installers do not do that, so it should no longer be a problem after the defaults ar...

IIS typically has Default.aspx already listed if you have ASPNET enabled (just like it has typically has index.htm and default.htm and such listed as default pages). This has been the case on every machine we have ever tested. What OS is Vault installed on? What version of IIS are you using? Is ASPN...

We have reproduced it and it will be fixed for 1.1.1.

Which issue are you asking about? The GUI client enabling the update bugs section only when there is a valid transaction is by design. I can log a request to change that behavior, but that wasn't something we were planning on changing for the next release. The Classic IDE client not enabling the upd...

Another user just reported your database connection problem. It is all our fault

http://support.sourcegear.com/viewtopic.php?p=39625

OK, it seems that there is a problem with SQL auth and 64-bit machines. The Crypto Keys in the registry SQL auth needs to decrypt the password are being put in the wrong hive for some reason. There are a couple of ways you can get around this: - Export the SourceGear\Vault (or Fortress) Server regis...