Troubleshooting "Error in the application" msg from Admin

[mrthomas]

I need to ad a new user... after logging into the admin site, I clicked on "users" and immediately received the error msg "Error in the application". I have the server log available upon request as the "log" extension is apparently not supported.

[lbauer]

The first step is to restart IISon the Vault Server machine with an iisreset command from a command prompt.

If that does not resolve the problem, Send the sgvault.log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[mrthomas]

We tried restarting IIS and it did not work. I have attached the zipped log file.

[lbauer]

I don't see a system restart in the log. Did IIS not restart?

What operating system is the Vault Server on?

You could try manually stopping and starting the website where the Vault Service is installed.

[mrthomas]

The log is before the restart. Regardless, it contains the error occurred. I have attached the updated log file.

[lbauer]

The main error seems to be this:

----1/13/2010 1:28:05 PM mrthomas--192.168.12.116(192.168.12.116)--SSL Disabled System.Data.SqlClient.SqlException: The server principal "sgvaultuser" is not able to access the database "sgdragnet" under the current security context.

According to the log, you are using Vault 5.0.2, there is no sgdragnet database used by Vault, only sgvault and sgmaster. Had you previously been using Fortress? Fortress has an sgvault, sgmaster and sgdragnet database.

Do you see an sgdragnet database in SQL Server?

[mrthomas]

We had been (and I still believe) are using DragNET but it is really old... I think before you guys renamed it or merged it to Fortress. When we upgraded to 5.0.2 did we need to do something else with DragNET?

[lbauer]

As of Vault 4.x, Vault database and a Dragnet database can no longer be on the same SQL Server machine. We share a lot of code between Vault and Fortress, so it could be that when you installed Vault the installer detected the sgdragnet database and tried to do make some Fortress changes. In Fortress, the same user database (sgmaster) is shared between the bug tracking (sgdragnet) and source control side (sgvault).

If you're still using Dragnet, our recommendation would be to upgrade to Fortress, which integrates item tracking with source code control. The Fortress installer will use your existing sgdragnet and sgvault databases.

If for some reason you can't upgrade to Fortress, I would move the Dragnet database to a different SQL Server machine. If you leave Vault where it is uninstall Vault, leaving the databases when prompted. Then backup the sgdragnet, sgmaster and sgvault databases. Drop the sgdragnet database in SQL Server, then reinstall Vault.