Hi all,
I currently have an ASP .Net project running locally,
and accessing a local SQL server 2000 database. The
project runs fine since it is able to open the connection to the database,
and perform operations on it locally using
a connection dtata string pointing to the local data source.
However, when I wanted to point to a different server
using the same definitions, the connection did not work.
The only changes have been the name of the data source.
From (local) to SQL9, and the catalog from openhouse to srm. A user with the
same ID, and password was defined
in the target SQl server using the same permissions, and the authentication
is windows and SQL server.
I am able to ping to the server, and access the tables of this database
using enterprise manager using the user
that was defined. At this point I do not know what to
do. Any suggestion is greatly appreciated.
Thanks,
Carlos.
Can you post the error/exception you get?
Vikram Vamshi
Eclipsys Corporation
"Carlos" <chsanin@.earthlink.net> wrote in message
news:u52OyjIGFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I currently have an ASP .Net project running locally,
> and accessing a local SQL server 2000 database. The
> project runs fine since it is able to open the connection to the database,
> and perform operations on it locally using
> a connection dtata string pointing to the local data source.
> However, when I wanted to point to a different server
> using the same definitions, the connection did not work.
> The only changes have been the name of the data source.
> From (local) to SQL9, and the catalog from openhouse to srm. A user with
> the
> same ID, and password was defined
> in the target SQl server using the same permissions, and the
> authentication
> is windows and SQL server.
> I am able to ping to the server, and access the tables of this database
> using enterprise manager using the user
> that was defined. At this point I do not know what to
> do. Any suggestion is greatly appreciated.
> Thanks,
> Carlos.
>
Showing posts with label accessing. Show all posts
Showing posts with label accessing. Show all posts
Sunday, February 19, 2012
connection string does not work for a different server
Hi all,
I currently have an ASP .Net project running locally,
and accessing a local SQL server 2000 database. The
project runs fine since it is able to open the connection to the database,
and perform operations on it locally using
a connection dtata string pointing to the local data source.
However, when I wanted to point to a different server
using the same definitions, the connection did not work.
The only changes have been the name of the data source.
From (local) to SQL9, and the catalog from openhouse to srm. A user with the
same ID, and password was defined
in the target SQl server using the same permissions, and the authentication
is windows and SQL server.
I am able to ping to the server, and access the tables of this database
using enterprise manager using the user
that was defined. At this point I do not know what to
do. Any suggestion is greatly appreciated.
Thanks,
Carlos.Can you post the error/exception you get?
Vikram Vamshi
Eclipsys Corporation
"Carlos" <chsanin@.earthlink.net> wrote in message
news:u52OyjIGFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I currently have an ASP .Net project running locally,
> and accessing a local SQL server 2000 database. The
> project runs fine since it is able to open the connection to the database,
> and perform operations on it locally using
> a connection dtata string pointing to the local data source.
> However, when I wanted to point to a different server
> using the same definitions, the connection did not work.
> The only changes have been the name of the data source.
> From (local) to SQL9, and the catalog from openhouse to srm. A user with
> the
> same ID, and password was defined
> in the target SQl server using the same permissions, and the
> authentication
> is windows and SQL server.
> I am able to ping to the server, and access the tables of this database
> using enterprise manager using the user
> that was defined. At this point I do not know what to
> do. Any suggestion is greatly appreciated.
> Thanks,
> Carlos.
>
I currently have an ASP .Net project running locally,
and accessing a local SQL server 2000 database. The
project runs fine since it is able to open the connection to the database,
and perform operations on it locally using
a connection dtata string pointing to the local data source.
However, when I wanted to point to a different server
using the same definitions, the connection did not work.
The only changes have been the name of the data source.
From (local) to SQL9, and the catalog from openhouse to srm. A user with the
same ID, and password was defined
in the target SQl server using the same permissions, and the authentication
is windows and SQL server.
I am able to ping to the server, and access the tables of this database
using enterprise manager using the user
that was defined. At this point I do not know what to
do. Any suggestion is greatly appreciated.
Thanks,
Carlos.Can you post the error/exception you get?
Vikram Vamshi
Eclipsys Corporation
"Carlos" <chsanin@.earthlink.net> wrote in message
news:u52OyjIGFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I currently have an ASP .Net project running locally,
> and accessing a local SQL server 2000 database. The
> project runs fine since it is able to open the connection to the database,
> and perform operations on it locally using
> a connection dtata string pointing to the local data source.
> However, when I wanted to point to a different server
> using the same definitions, the connection did not work.
> The only changes have been the name of the data source.
> From (local) to SQL9, and the catalog from openhouse to srm. A user with
> the
> same ID, and password was defined
> in the target SQl server using the same permissions, and the
> authentication
> is windows and SQL server.
> I am able to ping to the server, and access the tables of this database
> using enterprise manager using the user
> that was defined. At this point I do not know what to
> do. Any suggestion is greatly appreciated.
> Thanks,
> Carlos.
>
Friday, February 10, 2012
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
Joe
Hi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
Joe
Hi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Connection Problem accessing a SQL server
Hello,
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
I have a PC with an application using SQL on a SBS 2003 server and the SQL
database is on a SBS 2000 server. I get from the SBS 2003 server to the SBS
2000 server through a router. The IP address are non-routable so it does
not go out over the internet. When I execute the application on the SBS
2003 the first couple of screens that access the database work just fine and
the response time is good. I then try another transaction and I get the
Connection failed: SQLState '01000' SQL Server Error: 10060 followed by
Connection failed: SQLState '08001' SQL Server Error: 17. I do not have a
clue what is causing this problem nor can I find a reason. If I reply
'yes' to the connection boxes that come up on the screen eventually the
connection is re-instated and I can do a couple more transactions before the
failure occurs again. I am using ODBC to connect any help would be
appreciated. I am wondering if the topology of the network is an issue.
The sequence of events is PC --> Switch --> SBS 2003 Server --> Router -->
SBS 2000 Server --> SQL 2000. I do not think this is the problem but I
thought I mention it. I also thought about ISA but I can do the
transactions initially that must mean the ports are opened. If I direct
connect the PC to the SBS 2000 server I do not have a problem with the
transactions timing out..
Thank You,
JoeHi
You may want to look at SQL profiler to see what statements are being
executed by the SQL Server and if the statements complete after the client
has timed out. You may also want to look for blocking.
If you are getting timeout errors, have you configured the timeout? What
time does it take to timeout?
You may also want to look at the protocols you are using and try a different
one.
John
"Joe Bucar" <jbucar@.hotmail.com> wrote in message
news:uLVa%234HlFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I have a PC with an application using SQL on a SBS 2003 server and the
> SQL database is on a SBS 2000 server. I get from the SBS 2003 server to
> the SBS 2000 server through a router. The IP address are non-routable so
> it does not go out over the internet. When I execute the application on
> the SBS 2003 the first couple of screens that access the database work
> just fine and the response time is good. I then try another transaction
> and I get the Connection failed: SQLState '01000' SQL Server Error: 10060
> followed by Connection failed: SQLState '08001' SQL Server Error: 17. I
> do not have a clue what is causing this problem nor can I find a reason.
> If I reply 'yes' to the connection boxes that come up on the screen
> eventually the connection is re-instated and I can do a couple more
> transactions before the failure occurs again. I am using ODBC to connect
> any help would be appreciated. I am wondering if the topology of the
> network is an issue. The sequence of events is PC --> Switch --> SBS 2003
> Server --> Router --> SBS 2000 Server --> SQL 2000. I do not think this
> is the problem but I thought I mention it. I also thought about ISA but I
> can do the transactions initially that must mean the ports are opened. If
> I direct connect the PC to the SBS 2000 server I do not have a problem
> with the transactions timing out..
> Thank You,
> Joe
>
Subscribe to:
Posts (Atom)