Install of Vault Server 3.1.8 fails to connect to SQL Srv
Moderator: SourceGear
Install of Vault Server 3.1.8 fails to connect to SQL Srv
Hi,
I'm trying to install Vault Server 3.1.8.
I have SQL Server 2005 (shows up in the Windows.Services as "SQLEXPRESS" and this was installed by Visual Studio 2005, I'm guessing it's the Express version).
When the installl gets past the point of choosing Windows or SQL security/authenticaion it fails to connect to the SQL Server.
I didn't see anything in the instructions about configuring SQL Srvr.Do I need to config it?
FYI, I tried installing the MS Desktop SQL Server (MSDE2000A) and that failed to install. SQL Express 2005 was installed by VS 2005 RC1.
Thanks!
I'm trying to install Vault Server 3.1.8.
I have SQL Server 2005 (shows up in the Windows.Services as "SQLEXPRESS" and this was installed by Visual Studio 2005, I'm guessing it's the Express version).
When the installl gets past the point of choosing Windows or SQL security/authenticaion it fails to connect to the SQL Server.
I didn't see anything in the instructions about configuring SQL Srvr.Do I need to config it?
FYI, I tried installing the MS Desktop SQL Server (MSDE2000A) and that failed to install. SQL Express 2005 was installed by VS 2005 RC1.
Thanks!
Is SQL Server Express installed on the same machine as the Vault Server? Also, can you verify the SQL Server Express service is running?
If this all checks out, it could just be a named instance issue. SQL Express will install under a named instance. Try the isntall with "(local)\SQLEXPRESS" - without the quotes in the Vault Server database connection.
If this all checks out, it could just be a named instance issue. SQL Express will install under a named instance. Try the isntall with "(local)\SQLEXPRESS" - without the quotes in the Vault Server database connection.
Jeff Clausius
SourceGear
SourceGear
problem solved. Thanks!
SQLexpress was running. However,changing the login name to (local)\sqlexpress did the trick.
Install proceeded. Now I just need to configure it.
Thanks!
Install proceeded. Now I just need to configure it.
Thanks!
Still can't get Vault to connect to the database
CONFIGURATION
Everything is on one machine, Winxp pro.
I've installed SQL Express that comes with VS 2005. (No change from previous post).
When I get to the step of runnign the Admin program, I get the following error message.
---------------------------
SourceGear Vault
---------------------------
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 401: Access Denied.
---------------------------
OK
---------------------------
I'm loggintg in with my user name and pw (Admin account).
For Vault Server, I've tried:
localhost
localhost/sqlexpress - this is what I used originally ot get Vault to connect to the SQL Server
clay2/localhost
clay2/localhost/sqlexpress
http://localhost/VaultService
vaultservice (that one took a while...to fail. I got hopeful thinkign "could it be THAT easy?). Nope.
OTHER THINGS I TRIED
I read the support note at:
http://support.sourcegear.com/viewtopic.php?t=736
I'm able to view via IE browser to:
http://localhost/VaultService/vaultservice.asmx
I got as far as #3 OK. I don't know how to test for what the problem is beyond that. (Naturally, I'd like to know what the problem is before applying solutions).
What might be the problem?
How can I test to find how which problem I've got?
Thanks!
-Clay
Everything is on one machine, Winxp pro.
I've installed SQL Express that comes with VS 2005. (No change from previous post).
When I get to the step of runnign the Admin program, I get the following error message.
---------------------------
SourceGear Vault
---------------------------
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 401: Access Denied.
---------------------------
OK
---------------------------
I'm loggintg in with my user name and pw (Admin account).
For Vault Server, I've tried:
localhost
localhost/sqlexpress - this is what I used originally ot get Vault to connect to the SQL Server
clay2/localhost
clay2/localhost/sqlexpress
http://localhost/VaultService
vaultservice (that one took a while...to fail. I got hopeful thinkign "could it be THAT easy?). Nope.
OTHER THINGS I TRIED
I read the support note at:
http://support.sourcegear.com/viewtopic.php?t=736
I'm able to view via IE browser to:
http://localhost/VaultService/vaultservice.asmx
I got as far as #3 OK. I don't know how to test for what the problem is beyond that. (Naturally, I'd like to know what the problem is before applying solutions).
What might be the problem?
How can I test to find how which problem I've got?
Thanks!
-Clay
What operating system is the Vault server installed on?
If it's Windows 2003 Server, is Anonymous access enabled?
Is ASPNET allowed?
http://support.sourcegear.com/viewtopic.php?t=185
If it's Windows 2003 Server, is Anonymous access enabled?
Is ASPNET allowed?
http://support.sourcegear.com/viewtopic.php?t=185
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
No, it's on Win XP Pro
CONFIGURATION
Everything (Vault Client & Server) is on one machine, Winxp pro.
I've installed SQL Express that comes with VS 2005. (No change from previous post).
I followed the link. It says it appies to win server 2003. Does it also apply to Win XP Pro?
Everything (Vault Client & Server) is on one machine, Winxp pro.
I've installed SQL Express that comes with VS 2005. (No change from previous post).
I followed the link. It says it appies to win server 2003. Does it also apply to Win XP Pro?
On the machine, if you start up the Vault GUI Client, log in with "admin", the password, and "localhost".
Once you have done that, let's take a look at the Vault Server Log. If you rename it with .txt, you can post it to this forum - or at least the tidbits related to any error.
Once you have done that, let's take a look at the Vault Server Log. If you rename it with .txt, you can post it to this forum - or at least the tidbits related to any error.
Jeff Clausius
SourceGear
SourceGear
Same results. Here's the log
Here's the sgvault.log
# SourceGear Vault Server
----4/11/2006 12:24:25 AM sgvaultsystem--()--
System Started
Version 3.1.8.3771
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 = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://clay2/VaultService
Identity = CLAY2\ASPNET
# SourceGear Vault Server
----4/11/2006 12:24:25 AM sgvaultsystem--()--
System Started
Version 3.1.8.3771
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 = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://clay2/VaultService
Identity = CLAY2\ASPNET
Do you get the same error if you use the Vault GUI Client to attempt the login?
The log file shows no web service method is being hit.
Again, if you browse to http://localhost/vaultservice/vaultservice.asmx, you get a Vault Service Description page? If that page comes up, can you click the Ping method and then invoke the method? What result does that produce?
The log file shows no web service method is being hit.
Again, if you browse to http://localhost/vaultservice/vaultservice.asmx, you get a Vault Service Description page? If that page comes up, can you click the Ping method and then invoke the method? What result does that produce?
Jeff Clausius
SourceGear
SourceGear
Yes
yes, I get the same error loggin in with the client.
Yes, I can get the above web page and see the 'ping' option.
When I click"invoke" I get a page of xml:
<?xml version="1.0" encoding="utf-8" ?>
<int xmlns="http://www.sourcegear.com/schemas/vault">1</int>
Yes, I can get the above web page and see the 'ping' option.
When I click"invoke" I get a page of xml:
<?xml version="1.0" encoding="utf-8" ?>
<int xmlns="http://www.sourcegear.com/schemas/vault">1</int>
You're getting a 401 error, correct? Something is preventing the client Web Service call from getting through.
Can you verify the VaultService Directory security allows anonymous connections? Is there a "root" web.config that may be interferring with the authentication / authorization of Vault Service? Anything that would be interferring with a normal anonymous web connection?
BTW - I'm signing off for now, but I'll be back in 8 hours or so.
Can you verify the VaultService Directory security allows anonymous connections? Is there a "root" web.config that may be interferring with the authentication / authorization of Vault Service? Anything that would be interferring with a normal anonymous web connection?
BTW - I'm signing off for now, but I'll be back in 8 hours or so.
Jeff Clausius
SourceGear
SourceGear
To check if anonymous access is enabled go to IIS and choose the website where Vault is located and then choose Properties->Directory Security then choose to EDIT Anonymous access and authentication control. In the Authentication methods dialog make sure Anonymous access is checked.
Do you have SharePoint installed on the server machine? Share Point installs a web.config file under c:\inetpub\wwwroot which override some of Vault's web.config settings and causes authentication problems.
If you do have SharePoint installed, see the following KB article for more information on how to work around that:
http://support.sourcegear.com/viewtopic.php?t=3147
Did you install IIS on the Vault machine before you installed the .NET framework? If you installed IIS after the .NET framework (this happens a lot on XP pro, since IIS in the machine, but not "turned on" by default) see the following KB article:
http://support.sourcegear.com/viewtopic.php?t=22
Do you have SharePoint installed on the server machine? Share Point installs a web.config file under c:\inetpub\wwwroot which override some of Vault's web.config settings and causes authentication problems.
If you do have SharePoint installed, see the following KB article for more information on how to work around that:
http://support.sourcegear.com/viewtopic.php?t=3147
Did you install IIS on the Vault machine before you installed the .NET framework? If you installed IIS after the .NET framework (this happens a lot on XP pro, since IIS in the machine, but not "turned on" by default) see the following KB article:
http://support.sourcegear.com/viewtopic.php?t=22
Mary Jo Skrobul
SourceGear
SourceGear
Sharepoint not installed. Also I verified that the web.config file is not in C:\Inetpub\wwwroot.
IIS was running before I uninstalled the .net framework and reinstalled it last time, I think.
I'd be happy to do the hour of work involved in uninstallig and reinstalling the .net framework if there's some way to verify that this is the problem.
How can I test whether the ".net /IIS install" is a problem?
IIS was running before I uninstalled the .net framework and reinstalled it last time, I think.
I'd be happy to do the hour of work involved in uninstallig and reinstalling the .net framework if there's some way to verify that this is the problem.
How can I test whether the ".net /IIS install" is a problem?
You don't need to re-install the .NET framework (that would be a last resort). Just try repairing the IIS mappings (in suggestion number 2 of the above KB article). It only takes a minute.
http://support.microsoft.com/default.as ... us;q306005
Is anonymous access enabled in IIS? Are the clients going through a proxy server?
http://support.microsoft.com/default.as ... us;q306005
Is anonymous access enabled in IIS? Are the clients going through a proxy server?
Mary Jo Skrobul
SourceGear
SourceGear