Connfig Replication via Internet

I want to replicate data via Internet using FTP Server, i have SQL 2K with SP3. i set up client network as
- Server alias: my local server's name
- Server Name: ip address on internet
- Network libraries: TCP/IP
- Port : 1433
But i connect using Enterprise Manage to SQL Server then it errors:
A Connection could not be established to Dis-server ( Dis-server is my servername)
Reason: SQL Server does not exist or accessed denied
ConnectionOpen(Connect())..
please help me..tks
Regards
NBtri
from the subscriber can you ping your publisher?
On your publisher and subscriber you have to configure the subsciber and
publisher using client network utility.
Make sure that the publsiher and subscriber are listed in the hosts file
(thanks Paul Ibison for this tidbit of tidbitosity)
Then on your Publisher go to Tools - replication - Configure Publishers,
subscribers, distributors, click on the subscribers tab, and click on the
check box to the right of your subscriber server name. Ensure you are using
a SQL Server account, and enter the subscriber sa (or an account in the
system administrator role) onthe subscriber and its password.
Then on your subscriber, set up a pull subscription.
"NBTri" <anonymous@.discussions.microsoft.com> wrote in message
news:8ABF42AE-6921-4A63-8479-CD7910909F89@.microsoft.com...
> I want to replicate data via Internet using FTP Server, i have SQL 2K with
SP3. i set up client network as
> - Server alias: my local server's name
> - Server Name: ip address on internet
> - Network libraries: TCP/IP
> - Port : 1433
> But i connect using Enterprise Manage to SQL Server then it errors:
> A Connection could not be established to Dis-server ( Dis-server is my
servername)
> Reason: SQL Server does not exist or accessed denied
> ConnectionOpen(Connect())..
>
> please help me..tks
> Regards
> NBtri
>

connectivity only installation

Is the "connectivity only installation" is equvilant to installing MDAC on
the client machines, or the "connectivity only installation" has more
functionality to do.
Thanks
It is basically an MDAC installation.
Rand
This posting is provided "as is" with no warranties and confers no rights.
sqlsql

connectivity only installation

Is the "connectivity only installation" is equvilant to installing MDAC on
the client machines, or the "connectivity only installation" has more
functionality to do.
ThanksIt is basically an MDAC installation.
Rand
This posting is provided "as is" with no warranties and confers no rights.

connectivity of the db

Hi,
Want to check connectivity from IIS Server to SQL Server but without using
SQL Client .. Is there any way
Thanks
ARR
From the command prompt
telnet IPAddress 1433
If it returns an error, connectivity can not be established, it fyou get a
blank screen, it means you are conencted. Replace 1433 with the port number
if the port number is not the default.
If
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mark" wrote:

> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>
|||Configure an ODBC DSN and click test.
"Mark" <ajuonline@.yahoo.com> wrote in message
news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
|||Hi
Just check this one. It might be useful for you
http://msdn.microsoft.com/library/en...asp?frame=true
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
"Mark" wrote:

> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>
|||Thanks for the reply .
Do we get sql server driver in ODBC without installing sql server client
itself ...!
Thanks
Mark
"Danny" <someone@.nowhere.com> wrote in message
news:l9_ke.227$Pm3.128@.trnddc08...
> Configure an ODBC DSN and click test.
>
> "Mark" <ajuonline@.yahoo.com> wrote in message
> news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
>
|||The SQL Server drivers are part of the OS since (at least) W2K.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mark" <ajuonline@.yahoo.com> wrote in message news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client itself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message news:l9_ke.227$Pm3.128@.trnddc08...
>
|||To add to Tibor's response, SQL Server connectivity components are bundled
as part of MDAC (Microsoft Data Access Components).
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <ajuonline@.yahoo.com> wrote in message
news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client
> itself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message
> news:l9_ke.227$Pm3.128@.trnddc08...
>

connectivity of the db

Hi,
Want to check connectivity from IIS Server to SQL Server but without using
SQL Client .. Is there any way
Thanks
ARRFrom the command prompt
telnet IPAddress 1433
If it returns an error, connectivity can not be established, it fyou get a
blank screen, it means you are conencted. Replace 1433 with the port number
if the port number is not the default.
If
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mark" wrote:

> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>|||Configure an ODBC DSN and click test.
"Mark" <ajuonline@.yahoo.com> wrote in message
news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>|||Hi
Just check this one. It might be useful for you
http://msdn.microsoft.com/library/e...asp?frame=true
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
---
"Mark" wrote:

> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>|||Thanks for the reply .
Do we get sql server driver in ODBC without installing sql server client
itself ...!
Thanks
Mark
"Danny" <someone@.nowhere.com> wrote in message
news:l9_ke.227$Pm3.128@.trnddc08...
> Configure an ODBC DSN and click test.
>
> "Mark" <ajuonline@.yahoo.com> wrote in message
> news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
>|||The SQL Server drivers are part of the OS since (at least) W2K.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mark" <ajuonline@.yahoo.com> wrote in message news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...[
vbcol=seagreen]
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client i
tself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message news:l9_ke.227$Pm3.128@.trnd
dc08...
>[/vbcol]|||To add to Tibor's response, SQL Server connectivity components are bundled
as part of MDAC (Microsoft Data Access Components).
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <ajuonline@.yahoo.com> wrote in message
news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client
> itself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message
> news:l9_ke.227$Pm3.128@.trnddc08...
>

connectivity of the db

Hi,
Want to check connectivity from IIS Server to SQL Server but without using
SQL Client .. Is there any way
Thanks
ARRFrom the command prompt
telnet IPAddress 1433
If it returns an error, connectivity can not be established, it fyou get a
blank screen, it means you are conencted. Replace 1433 with the port number
if the port number is not the default.
If
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mark" wrote:
> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>|||Configure an ODBC DSN and click test.
"Mark" <ajuonline@.yahoo.com> wrote in message
news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>|||Hi
Just check this one. It might be useful for you
http://msdn.microsoft.com/library/en-us/xmlsql/ac_xml1_8e7t.asp?frame=true
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
---
"Mark" wrote:
> Hi,
> Want to check connectivity from IIS Server to SQL Server but without using
> SQL Client .. Is there any way
>
> Thanks
> ARR
>
>|||Thanks for the reply .
Do we get sql server driver in ODBC without installing sql server client
itself ...!
Thanks
Mark
"Danny" <someone@.nowhere.com> wrote in message
news:l9_ke.227$Pm3.128@.trnddc08...
> Configure an ODBC DSN and click test.
>
> "Mark" <ajuonline@.yahoo.com> wrote in message
> news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> Want to check connectivity from IIS Server to SQL Server but without
>> using SQL Client .. Is there any way
>>
>> Thanks
>> ARR
>|||The SQL Server drivers are part of the OS since (at least) W2K.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mark" <ajuonline@.yahoo.com> wrote in message news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client itself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message news:l9_ke.227$Pm3.128@.trnddc08...
>> Configure an ODBC DSN and click test.
>>
>> "Mark" <ajuonline@.yahoo.com> wrote in message news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> Want to check connectivity from IIS Server to SQL Server but without using SQL Client .. Is
>> there any way
>>
>> Thanks
>> ARR
>>
>|||To add to Tibor's response, SQL Server connectivity components are bundled
as part of MDAC (Microsoft Data Access Components).
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <ajuonline@.yahoo.com> wrote in message
news:unSAA4aYFHA.3620@.TK2MSFTNGP09.phx.gbl...
> Thanks for the reply .
> Do we get sql server driver in ODBC without installing sql server client
> itself ...!
> Thanks
> Mark
> "Danny" <someone@.nowhere.com> wrote in message
> news:l9_ke.227$Pm3.128@.trnddc08...
>> Configure an ODBC DSN and click test.
>>
>> "Mark" <ajuonline@.yahoo.com> wrote in message
>> news:Od2b2rRYFHA.3540@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> Want to check connectivity from IIS Server to SQL Server but without
>> using SQL Client .. Is there any way
>>
>> Thanks
>> ARR
>>
>

Connectivity from Client to Server

Hai,

I am often getting the message

"SQL Server does not exist or access denied (Connection Open (Connect())"

when connecting from the client sql 2000 to the server and at sometimes it gets connected and it still exists/persists for some time.

though i checked the user rights, client server network utility where tcp/ip is the first protocol.

Give a (me) way to connect to the server, though the user iam trying to connect works in the Query Analyser in the Server

here,
vijayanand.gI know this a post from a previous post. I would try sql profiler and monitor the connections to see if the server is rejecting you or are you not getting there at all. You can use vnc or terminal services to connect to the server (for a good connection) and monitor your connection status.

Let me know.|||Hai,

Though i connect from the profiler the Server gives an error


here,
vijayanand.g|||Is the server behind any firewall?
Originally posted by g_vijayanand
Hai,

Though i connect from the profiler the Server gives an error


here,
vijayanand.g|||You need to execute the profiler either on the sql server or through a remote connection (using vnc or terminal services). Then try to connect on your machine and see what the profiler shows.|||Sorry - I just received your emails - I only have access to my email at home. Basically, you will need to find a machine that has access to the sql server (or login to the actual sql server) and run the profiler and see if at least the server sees that you are attempting to hit it.|||Hai,

The profiler does not connect and trace the required samples.

here,
vijayanand.g|||Hai,

I tried to connect from other machine in sql enterprise manager and query analyser for the specified user, it connects - but through my login in the domain it does not connect.

For the past 1 week iam trying to connect from a XP Machine , it does not connect, i tried to connect from a Windows 98 machine it connects, from a machine that has been logged as an administrator it connects, now i've changed my machines OS to Windows NT Server - now also not connecting .

here,
vijayanand.g|||Hai,

Connected to the Server. It was due to the entry that did not exist for the specified machine in the Hosts file or LmHosts file for the specified machine name.

The connectivity came when the connection was tested with the server by registering the Client by giving the ip address of the machine.

here,
vijayanand.g

Connections to SQL server are slow on one machine

Hi all,
My client PC is very slow to connect to all SQL server databases.
Other client machines are having no problem at all. I even tried
connecting to my local MSDE database, and the same behavior results.
If I try to connect via a .NET application it is also slow.

The connection is always made if I wait long enough, but then when I go
to query a table it is very slow again, even if I'm only returning one
row from a table with 5 fields.

Does anyone have any suggestions on how to troubleshoot this?

Thanks.check whether the ping time are different too ...
try switching off local firewall ...

"foreman_bob" <smhceh@.gmail.com> schrieb im Newsbeitrag
news:1137940934.406196.284270@.g47g2000cwa.googlegr oups.com...
> Hi all,
> My client PC is very slow to connect to all SQL server databases.
> Other client machines are having no problem at all. I even tried
> connecting to my local MSDE database, and the same behavior results.
> If I try to connect via a .NET application it is also slow.
> The connection is always made if I wait long enough, but then when I go
> to query a table it is very slow again, even if I'm only returning one
> row from a table with 5 fields.
> Does anyone have any suggestions on how to troubleshoot this?
> Thanks.|||What net library are you using? Is it the same net lib as the other
people that don't have issues? Are you authenticating the same way?Are
you requesting SSL or multiprotocol encryption from the client? Are
you located on the same LAN as the other users or do you dialup through
your 28KB modem into a VPN connection?

Greg|||I found out what was causing my problem today. I had ODBC tracing
turned on. As soon as I turned it off everything was fine.

Thanks for your replies.

Greg wrote:
> What net library are you using? Is it the same net lib as the other
> people that don't have issues? Are you authenticating the same way?Are
> you requesting SSL or multiprotocol encryption from the client? Are
> you located on the same LAN as the other users or do you dialup through
> your 28KB modem into a VPN connection?
> Greg|||wow.

Thank you! I am filing this one off!!!! I can totally see myself
turning it on, wandering off and forgetting it is on.

ick.

Connectiong to MSDE 2000

I installed MSDE 2000 on my machine running XP home
edition.
I can connect with all client utilities, include, query
analiser, enterprise manager, odbc, etc if i use the
builtin/administrator id, but i cant connect in the SQL
MODE.
If i set up an odbc connection for test, i get the
following error
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.
The ODBC error returns a state 28000 error, with is an
authenticaton error, please how can i correct thisMSDE is installed by default with Windows authentication, not with mixed
authentication, so you can't login with a SQL login, like 'sa'. You can
change this from Enterprise Manager by rightclicking the server, choosing
properties, and change the Authentication on the Security tab. You ahve to
restart SQL Server for the setting to take effect.
Jacco Schalkwijk
SQL Server MVP
"Lanre" <larry548997@.yahoo.com_anonymous> wrote in message
news:1b8701c3fc16$8a0ec650$a401280a@.phx.gbl...
> I installed MSDE 2000 on my machine running XP home
> edition.
> I can connect with all client utilities, include, query
> analiser, enterprise manager, odbc, etc if i use the
> builtin/administrator id, but i cant connect in the SQL
> MODE.
> If i set up an odbc connection for test, i get the
> following error
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user 'sa'. Reason: Not associated with a
> trusted SQL Server connection.
> The ODBC error returns a state 28000 error, with is an
> authenticaton error, please how can i correct this|||If you don't have Enterprise Manager, you can change the setting with the
steps from this article:
285097 INF: How to Change the Default Login Authentication Mode to SQL While
http://support.microsoft.com/?id=285097
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection without MDAC2.6

Hello Faculties
If a client is not upgraded with MDAC 2.6, is it still possible to
connect to SQL Server 2000 from that client?

Thanks in advance
Debashishdebashish (debashish_majumdar@.rediffmail.com) writes:
> Hello Faculties
> If a client is not upgraded with MDAC 2.6, is it still possible to
> connect to SQL Server 2000 from that client?

Yes, but you may experience limitations in functionality. For instance,
MDAC 2.5 and earlier does not support named instances. You may not be able
to use the bigint data type, or XML data.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Connection with Sql 2000

Hi,
My client is using window's 95 but we have SQL 2000, we are getting trouble to connect with SQL 2000 from Window's '95 operating system.If you dont mind can you elaborate on what error exactly you are getting ? and what exactly you are trying to do ?

Thanks.|||Originally posted by Decastod
If you dont mind can you elaborate on what error exactly you are getting ? and what exactly you are trying to do ?

Thanks.

Actually I have Widows'95 operating system and with that ay application tried to connect with SQL 2000, but it is giving me error and connection failed.|||Like Decastod stated earlier, the question is a little vague. A couple of things:

1) Can you ping the Server by name and/or ip address
2) Is the client utilities for SQL Server installed on the client PC
3) If the client utilities are installed verify the Enabled Protocols using the 'Client Network Utility'

Connection to SQL Server 2005 lost

We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?
Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?
|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:

> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>
|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||We upgraded to SNAC, but still experience the very same error. The text of
the error message reported is a little bit different, thought. It now says
"Named Pipes Provider: No process is on the other end of the pipe." We did
get rid of the error message when we changed the recordsets cursor from
server-side to client-side (CursorLocation = adUseClient).
"William Vaughn" wrote:

> Ah, I would STILL upgrade to SNAC. I agree that if the application is
> working and deployed it should not be disturbed, but yours is not working
> and SNAC solves any number of issues like this.
> --
> __________________________________________________ ________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
> __________________________________________________ __________________________________________
> "Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
> message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...
>
|||You are putting less work on the SQL Server by doing that and is generally a
good idea anyway. But you should also think about changing to TCP instead of
using named pipes.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:
|||It sounds like the server is rejecting the Open. Make sure that the server
configuration is not limiting the total number of connections in any way.
These might have been configured to comply with license or other artifical
constraints.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:

Connection to SQL Server 2005 lost

We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist
or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsis
t or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations
,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:

> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
________________________________________
__________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
________________________________________
____________________________________
________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>

Connection to remote server using VPN

Hi - I am a relative newbie to setting up and configuring servers so am a
bit baffled by all the server techno-speak.
My issue - I have a client who is based about 40 miles away who want me to
do some database work for them. I am a freelancer and he is a small company
who relies on a non sql server specific moonlighter for tech support (it's
not as wing and prayer as it might seem!).
They bought MS Small Biz server which includes SQL 2000. I tried to install
it on my XPHome pc but came to the view that you need a 2000/2003 server to
run anything bigger than a 4Gb database. Given that the db will be much
bigger than 4Gb we therefore need to install SQL Server on his server and
run it as a sql server with me installing query analyser and eneterprise
manager on my PC and connect. All fine in theory. Now for security I am
assuming the best way to connect is by using VPN? If this is so, can any
one point me to any info on setting up my end + his end and what may be
required h/w + s/w etc?
His moonlight techie says I need a static IP address... I think I have a
dynamic one, and that all he need to do is set up some filters his end. I
also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has router
and firewall his end.
I looked for past postings and find ref to this link
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
but now it's dead.
Any help much appreciated!
Happy New Year.
Andythere is a thread going on at www.sqlservercentral.com
http://www.sqlservercentral.com/forum/link.asp?TOPIC_ID=19507
maybe that will get you on track
jobi
"Andreww" <andrew@.fake.com> wrote in message
news:kwyIb.2561$tH.23625741@.news-text.cableinet.net...
> Hi - I am a relative newbie to setting up and configuring servers so am a
> bit baffled by all the server techno-speak.
> My issue - I have a client who is based about 40 miles away who want me to
> do some database work for them. I am a freelancer and he is a small
company
> who relies on a non sql server specific moonlighter for tech support (it's
> not as wing and prayer as it might seem!).
> They bought MS Small Biz server which includes SQL 2000. I tried to
install
> it on my XPHome pc but came to the view that you need a 2000/2003 server
to
> run anything bigger than a 4Gb database. Given that the db will be much
> bigger than 4Gb we therefore need to install SQL Server on his server and
> run it as a sql server with me installing query analyser and eneterprise
> manager on my PC and connect. All fine in theory. Now for security I am
> assuming the best way to connect is by using VPN? If this is so, can any
> one point me to any info on setting up my end + his end and what may be
> required h/w + s/w etc?
> His moonlight techie says I need a static IP address... I think I have a
> dynamic one, and that all he need to do is set up some filters his end. I
> also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has
router
> and firewall his end.
> I looked for past postings and find ref to this link
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> but now it's dead.
> Any help much appreciated!
> Happy New Year.
> Andy
>|||Jobi - thanks. I took a look and it seems more about how to set things up
once the VPN is set up... which helps.
In the firts instance, my question was about... is VPN the way to connect a
SQL client to server?
Help appreciated... even if it's that I'm in the wrong news group!
Regards
Andy
"jobi" <jobi@.reply2.group> wrote in message
news:bsud5v$fhp$1@.reader08.wxs.nl...
> there is a thread going on at www.sqlservercentral.com
> http://www.sqlservercentral.com/forum/link.asp?TOPIC_ID=19507
> maybe that will get you on track
> jobi
> "Andreww" <andrew@.fake.com> wrote in message
> news:kwyIb.2561$tH.23625741@.news-text.cableinet.net...
> > Hi - I am a relative newbie to setting up and configuring servers so am
a
> > bit baffled by all the server techno-speak.
> >
> > My issue - I have a client who is based about 40 miles away who want me
to
> > do some database work for them. I am a freelancer and he is a small
> company
> > who relies on a non sql server specific moonlighter for tech support
(it's
> > not as wing and prayer as it might seem!).
> >
> > They bought MS Small Biz server which includes SQL 2000. I tried to
> install
> > it on my XPHome pc but came to the view that you need a 2000/2003 server
> to
> > run anything bigger than a 4Gb database. Given that the db will be much
> > bigger than 4Gb we therefore need to install SQL Server on his server
and
> > run it as a sql server with me installing query analyser and eneterprise
> > manager on my PC and connect. All fine in theory. Now for security I am
> > assuming the best way to connect is by using VPN? If this is so, can
any
> > one point me to any info on setting up my end + his end and what may be
> > required h/w + s/w etc?
> >
> > His moonlight techie says I need a static IP address... I think I have a
> > dynamic one, and that all he need to do is set up some filters his end.
I
> > also have a Lynksys router (BEFSR41) and Norton Proff Fiewall. He has
> router
> > and firewall his end.
> >
> > I looked for past postings and find ref to this link
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> > but now it's dead.
> >
> > Any help much appreciated!
> >
> > Happy New Year.
> >
> > Andy
> >
> >
>|||"In the firts instance, my question was about... is VPN the way to connect a
SQL client to server?"
Given what little knowledge I have about your situation, I would say that VPN is your best bet. It's going to be the most economical, practical, and easiest way to connect to your client using SQL. Anything else would be expensive and/or unsecure.
But that's just my opinion...
Hope this helps.
Shaun

Connection to Analysis services from VB - very slow

Dear All,

I noticed a strange problem with one of my client's computers where in establishing a connection with Analysis services from VB takes 6 seconds, when the computer is not connected to network, but it takes only a fraction of a second when the computer is in networ. We use ADOMD to connect to Analysis server. Analysis services is installed in the local machine.

I ran dependency walker and found that the dll WS2_32.dll (winsock dll) is taking most of the time when establishing connection.

This issue is very important for us and it would be great, if someone could help me in this.

Thanks in advance,

Niyas

Have you tried to use aternative machine name when connecting locally?

Try connecting to your Analysis Server using "localhost" or "127.0.0.1"

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hi Edward,

Thanks for your reply. I did try connecting to Analysis services using localhost, but there is no difference in the performance. I also created a machine level account (not in any domain) and tried connecting to Analysis services. But still, it does not show any difference.

This problem occurs in our client's machine alone and not in my computer or in my colleagues computers.

Thanks,

Niyas

|||

This might be related to VB initialization. Try posting your question on VB forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=32&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I doubt whether this could be VB initialization problem, because the same problem occurred, when I tried to create a connection string using a .udl file. When I set the machine name, login credentials (Windows NT),driver and when I tested the conenction, it took 6 seconds, when I'm not in network and fraction of a second when I'm in network.

Thanks,

Niyas.

|||

Good. This is not VB related.

This is looks to be a general network problem. Try and see if you can find solution to this situation in windows networking forum. I doubt this is related to Analysis Services. Looks like generic connectivity problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection to Analysis services from VB - very slow

Dear All,

I noticed a strange problem with one of my client's computers where in establishing a connection with Analysis services from VB takes 6 seconds, when the computer is not connected to network, but it takes only a fraction of a second when the computer is in networ. We use ADOMD to connect to Analysis server. Analysis services is installed in the local machine.

I ran dependency walker and found that the dll WS2_32.dll (winsock dll) is taking most of the time when establishing connection.

This issue is very important for us and it would be great, if someone could help me in this.

Thanks in advance,

Niyas

Have you tried to use aternative machine name when connecting locally?

Try connecting to your Analysis Server using "localhost" or "127.0.0.1"

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hi Edward,

Thanks for your reply. I did try connecting to Analysis services using localhost, but there is no difference in the performance. I also created a machine level account (not in any domain) and tried connecting to Analysis services. But still, it does not show any difference.

This problem occurs in our client's machine alone and not in my computer or in my colleagues computers.

Thanks,

Niyas

|||

This might be related to VB initialization. Try posting your question on VB forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=32&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I doubt whether this could be VB initialization problem, because the same problem occurred, when I tried to create a connection string using a .udl file. When I set the machine name, login credentials (Windows NT),driver and when I tested the conenction, it took 6 seconds, when I'm not in network and fraction of a second when I'm in network.

Thanks,

Niyas.

|||

Good. This is not VB related.

This is looks to be a general network problem. Try and see if you can find solution to this situation in windows networking forum. I doubt this is related to Analysis Services. Looks like generic connectivity problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection Timeout - Need Help

Hello,

My app uses sql express on the client work station and has been installed by our application installer as a part of the prerequisites. The sql express install in standard and we've not changed any settings or brought in any tweaks.

All is well in our dev center. However, some of our clients are experiencing a problem when the app starts up. After the PC has been restarted, running the application causes it to crash with a connection time out. However, running it a second time will work with absolutely no issues.

Overall - after a restart, the first sql express connection will time out. I had a post on this earlier here -> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93279&SiteID=1

MS Lee had suggested -- > "As for the first connection failing and subsequent connections succeeding, one potential cause is the cached last connect information. If you're connecting to a named instance and not specifying a port, then the client will determine the port by querying SQL Browser on the server"

I'm not using a remote sql express. It is running on the local machine. My connection string looks like -->

"Integrated Security=True;User Instance=True;Data Source=.\SQLExpress;AttachDBFilename=<%USERS_LOCAL_FOLDER%>;"

What may be the problem ? Any help/advise will be great. I'll need to sort this out ASAP.

Thanks,

Avinash

System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)

at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()

at System.Data.SqlClient.TdsParserStateObject.ReadByte()

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

at ***.**.Base.DataServices.DataFactory.SQLProvider.GetConnection(String connectionString) in c:\DevNet\SCAH\***.**.Base.DataServices\DataFactory\SQLProvider.cs:line 30

at ***.**.Base.DataServices.DalContext.OpenConnection() in c:\DevNet\SCAH\***.**.Base.DataServices\DALContext.cs:line 166

at ***.**.Base.DataServices.DataManager.GetTable(String sql, String tableName, DataSet dataSet) in c:\DevNet\SCAH\***.**.Base.DataServices\DataManager.cs:line 93

Hi Avinash,

I'd recommend setting the Connect Timeout or Connection Timeout values in the connection string to a higher value. I believe the default is 60 seconds.

The most likely cause of the problem you area seeing is a result of how User Instances work. User Instances launch a new process of SQL Server that runs in the context of the application user. In order to do this, we need to setup some directories in the user's profile and copy some files into that directory. This takes some time to do, and it can cause a timeout to occur the first time the User Instance is created.

That work only needs to be done once, so subsequent connection succed as you've found.

Regards,

Mike Wachal
SQL Express team

Mark the best posts as Answers!

|||

Hello Mike W,

Many thanks for your response. I'll go ahead and try that out.

Question - will the folders/files need to be set up each time the sql process is started ? Won't it use ones created from a previous run ?

Also - some of the clients experiencing this problem are running very modern laptops with generous amounts of RAM and Hard Disk space being available. They were found to be rather light and no heavy apps/processes were running when this occurred. In that light - I suppose 60 Seconds is reasonable time to get started. Thoughts ?

But, I'll go ahead and try it - we'll see how it goes with our next build.

Thanks again.

Regards,

Avinash

|||

Hi Avinash,

The files and folders only need to be created once per user. The second time you try to connect, the folders and files are there and those are used. This is why you're seeing the behavior of a timeout the first time, but success the second (and subsequent) times.

It doesn't really have much to do with how modern your computer is, it has to do with HD access time and how long it takes to copy a file. Simply put, the default timeout is too short to accomplish both the file copy and the connection. I believe the default timeout is 60 seconds, so I'd go with something longer. A little trial and error should get you the right time.

Regards,

Mike

Mark the best posts as Answers!

|||

One other possibility I can think of is: You have some network issue with slow DNS.

Every time you make a connection, we need to do a couple of DNS resolve (in some cases both directions, IP <--> DNS). The connection may timeout if you DNS is slow. The second, windows will pick up the DNS caches and you can get connected much faster. If you know a machine that can expecience this first-time-timeout issue for sure, you can try to ping the name of the server machine before you connect the server. If the issue is gone in this case, you know the reason is slow DNS.

Another way to verify, run "ipconfig /flushdns" from command window and try connect to the server afterwards. See whether you see the timeout issue this time.

|||

This may be a dumb question. But I'll go ahead and ask anyway.

Is this valid in the case of SQL Express and particularly when both the client application(C# Smart Client) accessing the express database and SQL Express itself are running on the same machine ? Cause this is the mode in which we are seeing this issue.

Will a DNS resolve be needed when we use ".\SQLExpress" in the connect string ?

Thanks,

Avinash

|||

I would guess that DNS has nothing to do with accessing a local instance of SQL Express. As I said in an earlier post, the most likely issue here is the delay caused by the file copy that is required the first time (and only the first time) you create a User Instance for a given user.

Has adjusting the timeout eliminated the problem?

Regards,

Mike

|||

Hello Mike,

The last build has just been shipped out. I've set the time out to 120 seconds. Should hear from our clients in a few days.

Will let you know how it goes.

Thanks for all the help,

Regards,

Avinash

|||

Hello Mike,

Just to let you know that increasing the connection time out has indeed solved the problem.

Thanks,

Avinash

Connection Timeout - Need Help

Hello,

My app uses sql express on the client work station and has been installed by our application installer as a part of the prerequisites. The sql express install in standard and we've not changed any settings or brought in any tweaks.

All is well in our dev center. However, some of our clients are experiencing a problem when the app starts up. After the PC has been restarted, running the application causes it to crash with a connection time out. However, running it a second time will work with absolutely no issues.

Overall - after a restart, the first sql express connection will time out. I had a post on this earlier here -> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93279&SiteID=1

MS Lee had suggested -- > "As for the first connection failing and subsequent connections succeeding, one potential cause is the cached last connect information. If you're connecting to a named instance and not specifying a port, then the client will determine the port by querying SQL Browser on the server"

I'm not using a remote sql express. It is running on the local machine. My connection string looks like -->

"Integrated Security=True;User Instance=True;Data Source=.\SQLExpress;AttachDBFilename=<%USERS_LOCAL_FOLDER%>;"

What may be the problem ? Any help/advise will be great. I'll need to sort this out ASAP.

Thanks,

Avinash

System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)

at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()

at System.Data.SqlClient.TdsParserStateObject.ReadByte()

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

at ***.**.Base.DataServices.DataFactory.SQLProvider.GetConnection(String connectionString) in c:\DevNet\SCAH\***.**.Base.DataServices\DataFactory\SQLProvider.cs:line 30

at ***.**.Base.DataServices.DalContext.OpenConnection() in c:\DevNet\SCAH\***.**.Base.DataServices\DALContext.cs:line 166

at ***.**.Base.DataServices.DataManager.GetTable(String sql, String tableName, DataSet dataSet) in c:\DevNet\SCAH\***.**.Base.DataServices\DataManager.cs:line 93

Hi Avinash,

I'd recommend setting the Connect Timeout or Connection Timeout values in the connection string to a higher value. I believe the default is 60 seconds.

The most likely cause of the problem you area seeing is a result of how User Instances work. User Instances launch a new process of SQL Server that runs in the context of the application user. In order to do this, we need to setup some directories in the user's profile and copy some files into that directory. This takes some time to do, and it can cause a timeout to occur the first time the User Instance is created.

That work only needs to be done once, so subsequent connection succed as you've found.

Regards,

Mike Wachal
SQL Express team

Mark the best posts as Answers!

|||

Hello Mike W,

Many thanks for your response. I'll go ahead and try that out.

Question - will the folders/files need to be set up each time the sql process is started ? Won't it use ones created from a previous run ?

Also - some of the clients experiencing this problem are running very modern laptops with generous amounts of RAM and Hard Disk space being available. They were found to be rather light and no heavy apps/processes were running when this occurred. In that light - I suppose 60 Seconds is reasonable time to get started. Thoughts ?

But, I'll go ahead and try it - we'll see how it goes with our next build.

Thanks again.

Regards,

Avinash

|||

Hi Avinash,

The files and folders only need to be created once per user. The second time you try to connect, the folders and files are there and those are used. This is why you're seeing the behavior of a timeout the first time, but success the second (and subsequent) times.

It doesn't really have much to do with how modern your computer is, it has to do with HD access time and how long it takes to copy a file. Simply put, the default timeout is too short to accomplish both the file copy and the connection. I believe the default timeout is 60 seconds, so I'd go with something longer. A little trial and error should get you the right time.

Regards,

Mike

Mark the best posts as Answers!

|||

One other possibility I can think of is: You have some network issue with slow DNS.

Every time you make a connection, we need to do a couple of DNS resolve (in some cases both directions, IP <--> DNS). The connection may timeout if you DNS is slow. The second, windows will pick up the DNS caches and you can get connected much faster. If you know a machine that can expecience this first-time-timeout issue for sure, you can try to ping the name of the server machine before you connect the server. If the issue is gone in this case, you know the reason is slow DNS.

Another way to verify, run "ipconfig /flushdns" from command window and try connect to the server afterwards. See whether you see the timeout issue this time.

|||

This may be a dumb question. But I'll go ahead and ask anyway.

Is this valid in the case of SQL Express and particularly when both the client application(C# Smart Client) accessing the express database and SQL Express itself are running on the same machine ? Cause this is the mode in which we are seeing this issue.

Will a DNS resolve be needed when we use ".\SQLExpress" in the connect string ?

Thanks,

Avinash

|||

I would guess that DNS has nothing to do with accessing a local instance of SQL Express. As I said in an earlier post, the most likely issue here is the delay caused by the file copy that is required the first time (and only the first time) you create a User Instance for a given user.

Has adjusting the timeout eliminated the problem?

Regards,

Mike

|||

Hello Mike,

The last build has just been shipped out. I've set the time out to 120 seconds. Should hear from our clients in a few days.

Will let you know how it goes.

Thanks for all the help,

Regards,

Avinash

|||

Hello Mike,

Just to let you know that increasing the connection time out has indeed solved the problem.

Thanks,

Avinash

Connection Timeout

Hi, I have a client application that submits heavy processing query to an instance of Sql Server 2005 (Enteriprise Edition). After a few seconds the following exception is raised: "The time available has expired before the completion of the operation or the server is not responding". If I submit to the same application light processing queries the exception is not raised.
The client application is written in VB.net and uses ADO.net. (SqlConnection, SqlCommand,.. classes). The "Timeout connection" property is set to 1000.
Any suggestion?
Thank you.

Hi Ivan,

The ConnectionTimeout property of SqlConnection defines the time boundaries to open a physical connection to the SQL Server. In your case, the physical connection seems to be established within a reasonable frame. However, after the connection is up, the client and the server begin exchanging security information as part of the login process. This is related to a different "login timeout", which unfortunately you don't seem to be able to control from SqlClient.

What is happening on the server during the login process is related to the SOS scheduler operations - I won't go into deep detail, but in a nutshell all the tasks (including processing of login information) are queued. If the queue length is very long, the login information processing may be delayed beyond the login timeout and you will experience your symptoms above. There could also be other factors - the login processing makes calls to the security subsystem, if the entire SQL machine is under heavy stress, those may take longer time, too. You should approach this as a perf problem and use appropriate tools like perfmon, the SOS DMVs, etc.

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Connection Timeout is the timeout for connecting to SQL Server. What you need is COMMAND timeout. Set COMMAND timeout=0 for indefinite period.

Command timeout has to be set on the command object - because it is related to a particular SQL processing.

Connection Timeout

Hello,
We have a sitaution at a client site where the connection string in the our
application times-out on 2 of the PC's yet 2 other PC's work fine and the
server works fine. I tried altering the Remote Connection Timeout in the SQL
Express properties from the default of 20 seconds to 60 seconds and
restarting the SQL Server but it doesn't appear to have made a difference.
They are not stopped from working, after the connection timeout box appears
the user can click Okay and bingo they are connected.
Where else should we be looking?
Thank you!
ChrisAs far as I recall, remote connection timeout was an option removed in
SQL2000. You may want to look into the connection string used by the app to
connect to the SQL instance. For instance, if it is using the .NET provider
for SQL Server, the connection timeout is set in the
System.Data.SqlClient.Connection.Timeout property.
Linchi
"Chris Marsh" wrote:
> Hello,
> We have a sitaution at a client site where the connection string in the our
> application times-out on 2 of the PC's yet 2 other PC's work fine and the
> server works fine. I tried altering the Remote Connection Timeout in the SQL
> Express properties from the default of 20 seconds to 60 seconds and
> restarting the SQL Server but it doesn't appear to have made a difference.
> They are not stopped from working, after the connection timeout box appears
> the user can click Okay and bingo they are connected.
> Where else should we be looking?
> Thank you!
> Chris
>
>|||Chris,
you could change the timeout property of the connection string / command
object to overcome the issue. However I'd start by looking at network
connectivity between the 2 PCs and the main box. You could start with
ping -t but your network admin guys might have some better tools for this.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .