Unable to connect to ... No server was found ...

If you are having a problem using Vault, post a message here.
Post Reply
j.askey
Posts: 4
Joined: Mon Apr 18, 2016 11:26 am

Unable to connect to ... No server was found ...

Post by j.askey » Mon Apr 18, 2016 11:31 am

I have had a working standalone client/server installation for about 3 months now. About two days ago, I started getting this error trying to connect. Both client and server are co-hosted on my workstation.


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 the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/VaultService/VaultWeb/Login.aspx?ReturnUrl=%2fVaultService%2fVaultService.asmx">here</a>.</h2>
</body></html>


- I can connect to http://localhost/VaultService using the web client.
- I have very recently changed my account password in Windows.

Any help would be appreciated.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Unable to connect to ... No server was found ...

Post by Beth » Mon Apr 18, 2016 1:07 pm

We would need to look at a Vault Server Log. You can either post the errors or the log (you'll be able to remove them when we're done) or send the log to support at sourcegear.com.
Beth Kieler
SourceGear Technical Support

j.askey
Posts: 4
Joined: Mon Apr 18, 2016 11:26 am

Re: Unable to connect to ... No server was found ...

Post by j.askey » Mon Apr 18, 2016 3:10 pm

It looks like an invalid password.

# SourceGear Vault Server
----4/13/2016 8:53:45 AM sgvaultsystem--()--
System Started
Version 9.1.0.30584
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = IIS APPPOOL\VaultAppPool
----4/13/2016 8:53:46 AM joel--::1(::1)--SSL Disabled Login
----4/13/2016 8:54:23 AM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 8:54:27 AM joel--::1(::1)--SSL Disabled Login
----4/13/2016 8:54:32 AM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 8:54:36 AM joel--::1(::1)--SSL Disabled Login
----4/13/2016 8:54:40 AM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 8:54:46 AM joel--::1(::1)--SSL Disabled Login
----4/13/2016 8:54:55 AM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 3:22:00 PM joel--::1(::1)--SSL Disabled Login
----4/13/2016 3:22:34 PM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 3:22:41 PM joel--::1(::1)--SSL Disabled Login
----4/13/2016 3:23:15 PM joel--::1(::1)--SSL Disabled Logout
----4/13/2016 3:23:15 PM joel--::1(::1)--SSL Disabled Login failed: FailInvalidPassword
----4/13/2016 3:23:25 PM joel--::1(::1)--SSL Disabled Login
----4/13/2016 3:23:43 PM joel--::1(::1)--SSL Disabled Logout
----4/15/2016 4:23:27 PM sgvaultsystem--()--
System Started
Version 9.1.0.30584
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = IIS APPPOOL\VaultAppPool
----4/18/2016 8:13:48 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 8:13:48 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 8:14:01 AM j.askey--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailNotValidLogin
----4/18/2016 8:14:25 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 8:14:25 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 8:15:26 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 8:15:26 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 8:19:38 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 8:19:38 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:34:39 AM j.askey--::1(::1)--SSL Disabled Login
----4/18/2016 9:34:39 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:42:55 AM j.askey--::1(::1)--SSL Disabled Login
----4/18/2016 9:42:55 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:43:02 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:43:02 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 9:47:18 AM sgvaultsystem--()--
System Started
Version 9.1.0.30584
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 10080
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL =
Identity = IIS APPPOOL\VaultAppPool
----4/18/2016 9:47:47 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 9:47:47 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:47:49 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 9:47:49 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:48:27 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Logout
----4/18/2016 9:48:27 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Logout. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:48:29 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 9:48:29 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 9:48:46 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Logout
----4/18/2016 9:48:46 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Logout. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:19:26 AM j.askey--::1(::1)--SSL Disabled Login
----4/18/2016 10:19:26 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:20:48 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 10:20:48 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:20:56 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:20:56 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 10:25:03 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Logout
----4/18/2016 10:25:03 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Logout. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:32:39 AM joel--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailInvalidPassword
----4/18/2016 10:32:47 AM joel--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailInvalidPassword
----4/18/2016 10:32:57 AM j.askey--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailNotValidLogin
----4/18/2016 10:33:07 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 10:33:07 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:33:27 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Logout
----4/18/2016 10:33:27 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Logout. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:33:35 AM joel--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailInvalidPassword
----4/18/2016 10:33:47 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Login. Exception: The request failed with HTTP status 401: Unauthorized.
----4/18/2016 10:33:47 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login
----4/18/2016 10:44:12 AM admin--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Logout
----4/18/2016 10:44:12 AM --()-- The Plugin at http://127.0.0.1/VaultNotifyService/Vau ... rvice.asmx was not called with Event Logout. Exception: The request failed with HTTP status 401: Unauthorized.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Unable to connect to ... No server was found ...

Post by Beth » Mon Apr 18, 2016 4:10 pm

I see two issues.

One is the invalid password:
----4/18/2016 10:32:39 AM joel--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailInvalidPassword
----4/18/2016 10:32:47 AM joel--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailInvalidPassword
----4/18/2016 10:32:57 AM j.askey--IC08088.co.island.wa.us(192.168.70.120)--SSL Disabled Login failed: FailNotValidLogin

The other is the notify service failing.

When you say you can connect to the web client, are you just pulling up the login page, or can you fully log in?

Close your Vault GUI client and any other programs that may be integrated with it such as Visual Studio. Then go to your Vault admin web page and click on Vault Professional Plugins. In the plugins, you only need 4 valid True URLs. Two for notify (one for source control and one for work item tracking), one for the Vault index service, and one for shadow folders. Delete any that are either set to False or is just an extra one. You can check which ones work by clicking on the magnifying glass. It looks like 127.0.0.1 won't work for any. For the ones remaining, if they don't work, edit the URL to a working path. You should not have any that have vaultservice as part of the path.

More information on plugins can be found in this KB article: http://support.sourcegear.com/viewtopic.php?t=21347

When finished, open up your Vault client and try logging in again.
Beth Kieler
SourceGear Technical Support

j.askey
Posts: 4
Joined: Mon Apr 18, 2016 11:26 am

Re: Unable to connect to ... No server was found ...

Post by j.askey » Mon Apr 18, 2016 4:18 pm

I can log in via the web client.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Unable to connect to ... No server was found ...

Post by Beth » Tue Apr 19, 2016 7:51 am

Did you get your plugins updated? If so, was there any change?
Beth Kieler
SourceGear Technical Support

j.askey
Posts: 4
Joined: Mon Apr 18, 2016 11:26 am

Re: Unable to connect to ... No server was found ...

Post by j.askey » Tue Apr 19, 2016 9:51 am

I think I got the issue figured out.

I was getting an AD challenge on navigating to the Admin home page. The logins worked past that challenge, but I think my user needed to be set up to authenticate with Active Directory.

I can connect with the desktop client now.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Unable to connect to ... No server was found ...

Post by Beth » Tue Apr 19, 2016 10:14 am

Thank you for the update.
Beth Kieler
SourceGear Technical Support

Post Reply