FailDbConn
Moderator: SourceGear
FailDbConn
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
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
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?
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
SourceGear
FailDBConn
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
- 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
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?
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
SourceGear
FailDBConn
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
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
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?
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
SourceGear
FailDBConn
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
I can connect to the sgvault DB via osql....any more ideas....Ive tried everything I can think of.
Thanks
Alex
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.
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
SourceGear
FailDBConn
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
Let me know.
Thanks
Alex