SourceGear Support

Thanks for the update. Glad you got it working:-) I really am not sure why Windows Auth worked but SQL didn't (not having SQL auth enabled in SQL server it could cause that, but the installer would have bombed in that case). We are working on a 64-bit server and installer which should make installin...

Vault uses MD5 for authentication and MD5 is not FIPS compliant so Vault authentication will not work if FIPS enforcement is enabled.

I can log a feature request to use a FIPS compliant algorithm for authentication, but right now Vault will not work with that option enabled.

Did you verify the permissions on the MachineKeys directory? %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys? NT Authority/Network Service needs read/write permissions to that directory in order to decrypt the password. If that still doesn't work, you could try re-installing just...

Thanks for the log file. In IIS 6.0 I think you can check which version of the framework an App Pool is running in the AppPool Properties. You may want to re-register the 32-bit 2.0 framework: Go to command line, browse to the 32-bit 2.0 .NET framework folder (%windir%\Microsoft.NET\Framework\v2.0.5...

It appears to be the "#" in the name that is causing the upload problem. I was able to reproduce the upload failure when I tried to upload an attachment with # in the name, but when I took it out the upload worked fine.

I will log a bug.

Thanks for the report.

Are there any error messages logged to the Fortress server log file
(on the server machine - %windir%\temp\sgfortress\fortress.log) ?

Is there anything weird about the filename or path that could be causing the http upload to choke?

Also, it may be helpful if you sent your install log (%temp%\vault_install.log) so I can see what options were chosen during the server install.

Is the VaultService running as an application in IIS? Is the Application Pool where Vault is installed using the 2.0 framework? Did you stop and restart the Application Pool after you put IIS in 32-bit mode?

Hmm... that is weird. Our Projects At A Glance page is displayed in the correct order.

We will look into it.

I see that the project drop down on the web pages is in a different order and I am not sure how or why that changed. I will log a bug for 1.1.1.

Which other 'projects window' are you referring to?

Can you email me directly using the email button at the bottom of the page so we can get the email address to send the script to?

We don't like to post SQL scripts on the forum.

Thanks!

The problem is specific to some temp tables we are using to search tags (tags are new).

We will get you a sql script to fix your issue today and this will be fixed in the 1.1.1. release which will be out soon.

Thanks for the report.

Is the default collation for your SQL installation a different collation from that of your Fortress databases?

It could be that the temp tables created for the query are using the default collation on your server instead of the collation for the Fortress databases thus causing problems.

What collation are you using?

That is the "Milestones.aspx" file.

The code is in the "Milestone.aspx" (no "s") file.