3.5.3 install problem

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
mlippert
Posts: 252
Joined: Wed Oct 06, 2004 10:49 am
Location: Cambridge, MA

3.5.3 install problem

Post by mlippert » Mon Jan 28, 2008 3:15 pm

Hi,
We had a catastophic failure of our Vault machine.

I'm trying to get the rebuilt machine up and running again.

The new machine is running:
Windows Server 2003, Standard Edition (5.2.3790 Service Pack 2)
and
SQL Server 2005

I ran the VaultServer 3.5.3 install which seemed to run successfully.
I used SYSTEM for the IIS process model (which is what we had used before)
I used "SQL Server authentication" with the sa user & password.

everything seems to be running fine (there is mcafee running if that could be an issue) EXCEPT:

when I run the Vault Admin Tool:
Unable to connect to http://localhost/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 404: Not Found.
However IIS seems to be up and working as I can access
http://localhost/VaultService/ from a browser (the web client link on that page leads to a 404 page as might be expected from the previous datapoint)

All of this is w/o having changed anything from the normal Vault install (ie I haven't attempted to restore the backup of the old database yet, or modify any of the config files).

Help! I'm not sure what to try next.

Mike

[edit] Just saw the sticky http://support.sourcegear.com/viewtopic.php?t=185
trying that now.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Mon Jan 28, 2008 3:45 pm

Check this KB article for more ideas:
http://support.sourcegear.com/viewtopic.php?t=185
Linda Bauer
SourceGear
Technical Support Manager

mlippert
Posts: 252
Joined: Wed Oct 06, 2004 10:49 am
Location: Cambridge, MA

Post by mlippert » Mon Jan 28, 2008 4:01 pm

That helped, but I'm still not quite up and running.

You should update that page however to mention that v2.0 must also be enabled (the KB article only mentions 1.0) (see attached image)

Now however I run into the error
Could not get public key from server
I thought that the install dealt with that (but perhaps not if ASP.NET wasn't installed when the install was running?)
Attachments
W2003WebServiceExtASP.PNG
Windows Server 2003 IIS Web Service Extensions ASP.NET 2.0 must be enabled
W2003WebServiceExtASP.PNG (7.94 KiB) Viewed 1714 times

mlippert
Posts: 252
Joined: Wed Oct 06, 2004 10:49 am
Location: Cambridge, MA

Post by mlippert » Mon Jan 28, 2008 4:09 pm

OK, I can log in with the Admin Tool now.

This last problem was solved when I saw the following line in the log file:
----1/28/2008 4:51:06 PM --()-- Failed to delete crypto key. Make sure that the NT AUTHORITY\NETWORK SERVICE account has full control of the %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys directory and all of the files in it.
I went to that directory and added NETWORK SERVICE giving it full control, and now I can get in.

Thanks :)

mlippert
Posts: 252
Joined: Wed Oct 06, 2004 10:49 am
Location: Cambridge, MA

Post by mlippert » Mon Jan 28, 2008 5:29 pm

Final note:
Restore was successful, Vault is back and fully operational.

Thanks for your help, and an awesome tool.

Mike

Post Reply