Here is the contents of the web page displayed upon logging out of the web browser access to Vault 3.0 server:
Server Error in '/VaultService' Application.
--------------------------------------------------------------------------------
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
Vault 3.0 web browser - error on logout
Moderator: SourceGear
Just to clarify, the error message occurs on any machine's browser I have when I access the Vault 3.0 server and logout. I can access the Dragnet 1.0 server from any machine browser and can logout without the error.
P.S. I posted a follow-up comment on our other thread. I got an error during the Vault server re-installation after changing the name of the server machine and in the database. The error says something about CEREBRALDEV\ASPNET not being a valid windows login on the machine, but it is. I did not actually go through and re-install SQL server; I followed the MSDN documented procedures for renaming a server (see sp_dropserver and sp_addserver). The Vault re-installation recognizes the previously existing database, I just get the error as it tries to use the new SQL server login.
P.S. I posted a follow-up comment on our other thread. I got an error during the Vault server re-installation after changing the name of the server machine and in the database. The error says something about CEREBRALDEV\ASPNET not being a valid windows login on the machine, but it is. I did not actually go through and re-install SQL server; I followed the MSDN documented procedures for renaming a server (see sp_dropserver and sp_addserver). The Vault re-installation recognizes the previously existing database, I just get the error as it tries to use the new SQL server login.