Upgrade to Vault 2.01 Failing...

patrickc · Post by **patrickc** » Fri Mar 19, 2004 4:31 pm

Selected the default Machine - NT AUTHORITY\NETWORK SERVICE for IIS Process Model

Selected Windows Auth for SQL Server connection

Succesfully entered the Vault Admin password

Alllowed Vault Setup to set the read/write permissions...

Got the following output from the Vault Server Configuration:

Upgrading your Vault configuration.
Checking for IIS Version...OK
Connecting to the SQL Server...OK
Requesting Vault Admin user password...OK
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Upgrading SourceGear Vault database schema...OK
Upgrading SourceGear Vault stored procedures...OK
Database upgrade succeeded!
Checking permissions on local folders...Checking for IIS Version...OK
OK
OK
Looking for websites on this machine...
Found website - 'Default Web Site'
Found website - 'NetDA Staging'
Found website - 'Administration'
Creating the Virtual Directory, VaultShadowFolder...Already Exists.
Creating the Vault Server Home Page...Failed.
Your Vault Server configuration has been successfully upgraded.

Please press OK to continue installing the Client and Admin Tools (if selected).

At which point I responded OK and got the Error 1722 dialogue (There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected....)

Can anyone assist?

mskrobul · Post by **mskrobul** » Fri Mar 19, 2004 4:59 pm

It looks like for some reason the server home page didn't get written. It is difficult to say why this happened without looking at the server log file.

The server *should* still work even if it couldn't write the server home page.

Can you send the error specific parts of vault_install.log file located in your %temp% directory?

In the meantime, until we can figure out what exacty happened, you *should* be able to install the Admin Tool and Cleint on the server machine with their seperate installers and connect to the Server.

The Admin tool and Client installers can be dowloaded from the following URL:
http://www.sourcegear.com/vault/downloads.asp

patrickc · Post by **patrickc** » Fri Mar 19, 2004 5:55 pm

Tried repeatedly to send this message with an attacment of the entire Vault_Install.log, using the link in the notification mail. Appears to fail every time.

Trying to do so from the forum pages, produces the result: "The extension log is not allowed", which strikes me as incredible. But the forum seems to like the extension .txt just fine, so the log does seem to now be attached, albeit renamed to vault_install_log.txt.

Here is the vault server install error:

Creating the Vault Server Home Page...Read serverInstall.html from our resources.
Entered GetAssemblyVersion()
GetAssemblyVersion completed successfully.
Failed.
Error trying to write serverInstall.html: Access to the path "C:\Inetpub\wwwroot\VaultService\serverInstall.html" is denied.
Your Vault Server configuration has been successfully upgraded.

Now a new problem. Went ahead as you suggested and separately installed the new admin client. Install proceeded without incident. However, when I executed the new admin client, (using SSL) it popped a dialogue which seemed to be questioning the default cert I was executing with. I think I told it to accept the cert. Then it responded, "The Vault Server uses a protocol this is not supported by this client."

I cannot use the new Admin client at all at this point....

patrickc · Post by **patrickc** » Sun Mar 21, 2004 10:30 am

"The Vault Server uses a protocol this is not supported by this client."

mskrobul · Post by **mskrobul** » Mon Mar 22, 2004 9:14 am

What version is your Server?

That message usually means the Server and Client are different versions. The current version of the Server and Clients is 2.01.

patrickc · Post by **patrickc** » Mon Mar 22, 2004 9:17 am

I attempted to upgrad from 1.2.2 to 2.01, and unfortunatley, my backup is not as current as i would like, so falling back to backup, while i can do it, will be painful.

mskrobul · Post by **mskrobul** » Mon Mar 22, 2004 9:27 am

Try uninstalling the 2.01 Server (and keep your database) then re-install the 2.01 server. You shouldn't need to re-install the clients.

From your log file it looks like the installer didn't have permissions to write to severinstall.html file. Verify that you are logged in as an admin user on the machine when you run the installer.

patrickc · Post by **patrickc** » Mon Mar 22, 2004 9:31 am

Already tried this, and I am admin.

patrickc · Post by **patrickc** » Mon Mar 22, 2004 9:53 am

So I tried it again, uininstalled, and re-installed. It may be that I did not do this specific sequence before, that the first time I upgraded without uninstalling, found a problem, uninstalled 2.01 and tried to go back to 1.2.2. Anyway, uninstalling 1.2.2 and doing a fresh install of 2.01 seems to have done the trick. Thanks for the hand-holding.

SourceGear Support

Upgrade to Vault 2.01 Failing...

Upgrade to Vault 2.01 Failing...

No one can access the Vault server by any means now!