Vault.config & web.config reset on 3.5.2 Upgrade

CT-Mike · Post by **CT-Mike** » Mon May 21, 2007 10:37 pm

I just upgraded tonight from v3.5.1 to 3.5.2. The upgrade ran smoothly with no errors reported, however when I tried to open the Admin Tool I received a database connection failure message.

I looked in vault.config and web.config and all my settings had been reset to what looked like empty values. For example:

Vault.config
<SMTPServer></SMTPServer>
<SMTPAuthUserName></SMTPAuthUserName>
<SMTPAuthPassWord></SMTPAuthPassWord>
<SMTPFromAddress></SMTPFromAddress>

Web.config
<appSettings>
<add key="ConfigPath" value="XXXXXXXXVault.config" />


</appSettings>

I was able to restore the files from tape to a separate folder then run a WinDiff on the files and restore the missing settings.

Both the Client and the Admin Tools seem to be working OK now. Is there anything else that I need to check since the installation appears to have failed at some point?

lbauer · Post by **lbauer** » Tue May 22, 2007 9:44 am

Check the Vault_install.log file in your user's temp directory -- %temp% to see if any errors were logged there during the installation. Some errors are benign -- like error granting permission to accounts other than the one you chose for the IIS process mode.

CT-Mike · Post by **CT-Mike** » Tue May 22, 2007 11:22 am

I don't see any errors in the log file except errors related to granting permissions to other accounts.

The only reference to the config files that I see are these that completed successfully:

Upgrading Vault Service web.config file
Upgrading Vault Service web.config...OK
Updating shadow folder web.config file
Updating Vault Shadow Folder web.config...OK

And at the end:
Your Vault Server configuration has been successfully upgraded.

lbauer · Post by **lbauer** » Tue May 22, 2007 12:11 pm

The other thing I would check is the schema version, to make sure the database got upgraded:

Run this SQL query:

Select * from tblschemaversion

The result should be 3.5.2.2

CT-Mike · Post by **CT-Mike** » Tue May 22, 2007 7:25 pm

The result from tblschemaversions is 3.5.2.2
I guess we just chalk this up to a glitch in the upgrade?

lbauer · Post by **lbauer** » Tue May 22, 2007 7:33 pm

If all is running fine, then I don't think there's anything to worry about.