SourceGear Support

Hmmm...we haven't been able to reproduce that in house. What version if IE are you using? Does this only happen in IE? The information for Remember Login is stored in a cookie (as is authentication info etc.). Do you have IE configured to restrict cookies? Cookies need to be enabled (at least for th...

If this is a reproducible error and not just intermittent can you give me the exact steps (what page you are on, what buttons you are clicking etc. etc) to reproduce the error?

Thanks!

There are a many things that can cause view state issues. Some causes are: Application Pool Recycling, Session Timeout, Firewalls truncating it etc., etc. Here is a KB article that may help trouble shoot the issue http://support.microsoft.com/kb/555353 Do your users see the issue after an idle perio...

Thanks for the report. I have logged your bug and we will look into fixing it for an upcoming release.

Is the 4.1.4 installer package that doesn't work located at the same folder on disk as the 4.1.3 package? If not try moving it to that location. Or just try re-downloading the package from our site to a different location on disk and try installing from there. It sounds weird but sometimes the locat...

This information isn't displayed anywhere, but the project creator's user id and the creation time are both stored in the projects table in the sgdragnet database. I am not one of the SQL experts, but I think this query *should* work to get the basic information you need. use sgdragnet go select p.n...

A 4.x license will work in a 3.x server. The 4.x licenses are backwards compatible with 3.x so you can just purchase 4.x licenses (these will obviously also work with 4.x server when you do upgrade).

You are correct. The options you are referring to are only available and enabled in the Fortress client. Fortress bug tracking system integration is much tighter and more robust than Vaults/Dragnet integration. Pretty much all bug tracking functionality (query, add, edit, recent and at-a-glance view...

The code that is causing your problem doesn't get called on a fresh install only on an upgrade. A fresh install worked for the other person who was having your issue: http://support.sourcegear.com/viewtopic.php?f=5&t=10855&p=44782#p44782 A fresh install worked in house. You shouldn't need to...

This seems to be is specific to IIS 7 (without IIS 6 compatability turned on). You should be able to get around the issue one of two ways: - add string value called WebSite in your registry under the Vault Server folder: HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Fortress Server\WebSite and set its valu...

This seems to be is specific to IIS 7 (without IIS 6 compatability turned on). You should be able to get around the issue one of two ways: - add string value called WebSite in your registry under the Vault Server folder: HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Server\WebSite and set its value t...

Can you send the Fortress_install.log from the failed install located in your %temp% directory? You can use the email button on the side of this message to email me directly.

Do you have the Vault_Install.log from the failed install? (It should be in your %temp% directory)? That may help determine what went wrong. If so, please email it to me directly using the email button at the side of the post.

Are you using IIS 6 or IIS 7?

Glad to hear you worked around your install issue. This error *usually* occurs if the SYSTEM account doesn't have full control to the destination folder. If you encounter the problem again, make sure the folder location into which you are installing Vault has Full Control permissions for either the ...

Was VS2008 installed after Vault? If so, you will need to re-install the Vault Client so the proper registry entries are there for VS2008.