FailDbConn

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

Moderator: SourceGear

Post Reply
aritz

FailDbConn

Post by aritz » Sun Oct 02, 2005 8:40 am

Hi All,

I just installed a demo of sourcegear and cannot get it to connec to the DB. Here is the setup.
I have a winXP box with vault/client and admin tool installed...and a Win2K box that contains the SqlServer DB. Install went fine...created all the tables/sp. I can access both the .aspx and .asmx pages on the winXP box with no issues....but when I try to open up the admin tool...I put in the user/pass and get the following error in the log:

---10/2/2005 10:18:37 AM Admin--gcs1(192.168.168.170)--SSL Disabled System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

...so I changed the connection string in the web.config to reflect what I typically use...still not connecting.
then I opened up VS.NET and connected via the server manager no problem....so VS.NET sees it.....just not the admin/client tools.
When I installed it I selected the ASPNET as the user and in my processModel element I have

<processModel
<snip>
userName="machine"
password="AutoGenerate"

also....its IIS 5....
Any help would be greatly appreciated.
Thanks
Alex

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Sun Oct 02, 2005 12:40 pm

We'll need some more infor to accurately trouble shoot this problem.

What is the physical layout of SQL Server / Vault Server? Same machine? Different machines?

What does your connect string look like? How is SQL Server configured for accepting connections (named pipes, TCP/IP, Windows Auth)? Any firewall or other device which may require Authentication in between Vault Server / SQL Server?

How are you trying to connect to the SQL Server - Windows Auth / SQL Server Auth?

Also, are you using IP address or machine name for the SQL Server? If server name, can you try IP address?

Are you using a named instance?

Do you have any special SQL Server client configuration for connectivity?
Jeff Clausius
SourceGear

amritz

FailDBConn

Post by amritz » Sun Oct 02, 2005 6:07 pm

Thanks for the response....here are the answers to your queries.

- The SqlServer and Valut Server are on different machines

- ConnectString = <key="ConnectString" value="Server=2000Server;database=sgvault;uid=userid;pwd=password"/>

- There is no firewall between the two machines

- Sql is configured for TCP/IP Connections

- using SqlServer authentication

- Ive tried both the machine name and IP address

- It is the default instance

- no special sql client config

Thanks very much...please let me know if I can provide any other info.

Alex

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Sun Oct 02, 2005 8:37 pm

One thing I noticed is the use of "PWD=". By default, the Vault server will place an encrypted string in the connect string when the PWD attribute is used.

If you change the setting to a plain text password, you must change to use PASSWORD=.

Is there anything in your log regarding bad cryptography or anything else related to the connection?
Jeff Clausius
SourceGear

aritz

FailDBConn

Post by aritz » Mon Oct 03, 2005 5:51 am

Jeff.

here is the content from the log:

----10/3/2005 7:49:46 AM Admin--gcs1(192.168.168.170)--SSL Disabled Vault Failed to establish a connection to the database.
----10/3/2005 7:49:46 AM Admin--gcs1(192.168.168.170)--SSL Disabled System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn) at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn)


Thanks for the help.
Alex

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Oct 03, 2005 5:58 am

What if you try the IP address of the server instead of 2000Server in the connect string?

Also, you could fine tune the connect string using osql from a command line. Does something like connect

Code: Select all

osql -S 2000Server -U user -P passwd
?
Jeff Clausius
SourceGear

aritz

FailDBConn

Post by aritz » Mon Oct 03, 2005 12:22 pm

Jeff....I tried both the IP and the server name....both do not work.
I can connect to the sgvault DB via osql....any more ideas....Ive tried everything I can think of.

Thanks
Alex

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Oct 03, 2005 1:34 pm

There are a couple of different options. I'd like to try the easiest first.

Can you uninstall the Vault server, and then try re-installing? When you are finished, look for the vault_install.log file in your %TEMP% directory. We'll start with this to see what is being reported.
Jeff Clausius
SourceGear

aritz

FailDBConn

Post by aritz » Mon Oct 03, 2005 2:15 pm

Jeff....ok I reinstalled and looked at the log....I dont see any errors being reported. Should I email this log to you??

Let me know.
Thanks
Alex

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Oct 03, 2005 2:26 pm

Yes. I'll also need your web.config and sgvault.log (Vault server log ) as well.

Click the email button below this post to contact me.
Jeff Clausius
SourceGear

Post Reply