E
Earl
Interesting connection issue to SQL Server:
I have several apps that connect to the same server, albeit different
databases. One app is VB6, the others are VB.Net (VS2003). On the
development system, and on two separate test systems at different locations,
no problem connecting to the server and the database.
However, on one of my customer's system, the VB6 app will connect, but the
only .Net app I have installed will not connect to the same server
(different database).
VB6 connection string (this works on all systems):
strCN = "Provider=sqloledb;" & _
"Data Source=" & strDBServer & ";" & _
"Initial Catalog=" & strDBName & ";" & _
"Integrated Security=SSPI"
VB.Net connection string (this works on all systems except the one
customer's):
strCN = "data source=" & strDBServer & ";" & _
"initial catalog=" & strDBName & ";integrated security=SSPI;"
I've looked at the firewall, the IP settings, reinstalled the server,
reinstalled the databases, tried both NamedPipes and IP, this app just flat
will not connect. Any ideas on what I'm overlooking? Any method of testing
for connection to a server beyond the obvious SQLDMO timeout? Is it possible
that the network is blocking me (SQL2k is installed on an XP box, not the
company server)?
I have several apps that connect to the same server, albeit different
databases. One app is VB6, the others are VB.Net (VS2003). On the
development system, and on two separate test systems at different locations,
no problem connecting to the server and the database.
However, on one of my customer's system, the VB6 app will connect, but the
only .Net app I have installed will not connect to the same server
(different database).
VB6 connection string (this works on all systems):
strCN = "Provider=sqloledb;" & _
"Data Source=" & strDBServer & ";" & _
"Initial Catalog=" & strDBName & ";" & _
"Integrated Security=SSPI"
VB.Net connection string (this works on all systems except the one
customer's):
strCN = "data source=" & strDBServer & ";" & _
"initial catalog=" & strDBName & ";integrated security=SSPI;"
I've looked at the firewall, the IP settings, reinstalled the server,
reinstalled the databases, tried both NamedPipes and IP, this app just flat
will not connect. Any ideas on what I'm overlooking? Any method of testing
for connection to a server beyond the obvious SQLDMO timeout? Is it possible
that the network is blocking me (SQL2k is installed on an XP box, not the
company server)?