Cannot connect to VaultService

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

Moderator: SourceGear

Post Reply
Krillan
Posts: 3
Joined: Fri Sep 17, 2004 1:05 pm

Cannot connect to VaultService

Post by Krillan » Fri Sep 17, 2004 1:12 pm

I just installed 2.0.6 vault server w/ the admin tool, and the setup went smoothly. I am running a windows 2003 server box as the domain controller, w/ .NET 1.1 SP1.

I ran the install (this is the Demo Server/Client/Admin installer) and installed the server and admin tool. During install, it asked for a username/password, so I tried many things, and admin/admin happened to work (no where did it ask me what I wanted to make the admin password).

After the install completed, I went to the Admin Tool to login, and I entered admin/admin and localhost for my server, and clicked ok to connect. It ended up failing to connect because of a "Web Exception: The request failed with HTTP status 401: Unauthorized".

Does anyone have a solution to this problem of mine? I installed using a "Custom User", which I set to my Domain's Administrator account. So the permissions should be fine. I did, just for kicks, uninstall and reinstall using the NETWORK SERVICE and the "middle" option, and neither worked as well. I chose to enable permissions for VaultService, VaultShadowFolder, etc.

Thanks in advance.

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Fri Sep 17, 2004 1:46 pm

Was this a fresh install or an upgrade from a previous version?

Were there any errors logged to the vault_install.log file (located in your windows temp %temp% directory)? It may be helpful if you sent me the install log. You can email to me directly using the email link at the bottom of this message.

Are there any errors logged to the server log file? The server log is located in the %windir%\temp\sgvault directory.

During an install the installer *should* prompt you to set an admin password, and whatever you type in there is used for the admin login.

If you chose to install using a custom account, verify that the account you are using has all the permissions it needs as described in the KB article below:

http://support.sourcegear.com/viewtopic.php?t=1528

Also, verify that you have asp.net set up correctly on the server machine:

http://support.sourcegear.com/viewtopic.php?t=185
Mary Jo Skrobul
SourceGear

Post Reply