[SQL Server]Login failed for user

I am using Crystal Reports, VB.net, SQL Server 2000sp3, MDAC 8.0, and Windows XP. When I try to make a connection from a Crystal Report to SQL Server via an ODBC connection, I get the following message:

Details: 28000:[Microsoft][SQL Server Driver][SQL Server]Login failed for user domain/username

In the odbc, I specify SQL Server authentication and provide a username and password but these are being ignored. Why is Windows authentication being used in place of the SQL Server authentication that I specify in my odbc?

Thanks in advance,

MattThat's Crystal for you :)|||What version of Crystal Reports are you using?|||Originally posted by awsterling
What version of Crystal Reports are you using?

I am the version that came with Visual Studio .Net 2003. I don't know how to get the version number from it.

Thanks.|||Get ActiveReport from DataDynamics and you won't have to deal with these issues any more :)

[ODBC SQL Server Driver]Connot generate SSPI Context Anybody ...

We get the following error: Connection Failed:
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : Windows 2000 sql server 7.x
but on Windows XP it goes very well.
any ideas ?Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:

>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : Windows 2000 sql server 7.x
>
>but on Windows XP it goes very well.
>any ideas ?

[ODBC SQL Server Driver]Connot generate SSPI Context Anybody ...

We get the following error: Connection Failed:
SQLState: 'HY000' SQL Server Error:
1060 [microsoft][ODBC SQL Server Driver]Connot generate
SSPI Context Anybody ...
client : windows nt4
server : windows 2000 sql server 7.x
but on windows xp it goes very well.
any ideas ?
Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541
-Sue
On Fri, 2 Apr 2004 08:36:22 -0800, "amichaud"
<anonymous@.discussions.microsoft.com> wrote:

>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>client : windows nt4
>server : windows 2000 sql server 7.x
>
>but on windows xp it goes very well.
>any ideas ?

[ODBC SQL Server Driver]Communication Link Failure

I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?
You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:

>I have a third party Client (Rational Clearquest) connecting to a SQL server
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?
|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:

> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:

> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:

[ODBC SQL Server Driver]Communication Link Failure

I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:

>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:

> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:

> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>

[MSSQL + VS.NET] Connection - sleeping

Hello
I've prepared a small aplication in VS.NET and I use SqlConnection class.
Everything is ok, but when I'm trying to disconnect from server using
if (cnSQL->State != ConnectionState::Closed) cnSQL->Close()
there is still connection do server present. I have to close connection
because I'm trying to drop this database.
Have you ever heard about this kind of problem??

Trociu

--
Plain-text over all!!!
/**********/
write me : trociu@.autonom ict pwr wroc pl
search me : gg: 1382729"Trociu" <trociu@.autonom.ict.pwr.wroc.pl> wrote in message
news:slrncmhvuv.14n.trociu@.autonom.ict.pwr.wroc.pl ...
> Hello
> I've prepared a small aplication in VS.NET and I use SqlConnection class.
> Everything is ok, but when I'm trying to disconnect from server using
> if (cnSQL->State != ConnectionState::Closed) cnSQL->Close()
> there is still connection do server present. I have to close connection
> because I'm trying to drop this database.
> Have you ever heard about this kind of problem??
> Trociu
> --
> Plain-text over all!!!
> /**********/
> write me : trociu@.autonom ict pwr wroc pl
> search me : gg: 1382729

I have no idea, unless perhaps you're using connection pooling, and the pool
is still active? You might get a better response in a VB or .NET group.

From the server side, you can use ALTER DATABASE to disconnect all users
from a database - see Books Online:

ALTER DATABASE MyDB SET OFFLINE WITH ROLLBACK IMMEDIATE

Simon

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advance
Please post your connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance
|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
"Dan Guzman" wrote:

> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>
>
|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> "Dan Guzman" wrote:
|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
|||Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNECTION capability to validate the attributes.
Sincerely,
Anthony Thomas

"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
>
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
>
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
|||Can I remove the MDAC?
"AnthonyThomas" wrote:

> Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNEC
TION capability to validate the attributes.[vbcol=seagreen]
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advancePlease post your connection string.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
"Dan Guzman" wrote:
> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > Could anyone help?
> >
> > "Connection failed:
> > SQLState: '01S00'
> > SQL Server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > Connection failed:
> > SQLState: 'S1T00'
> > SQL server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >
> > Thanks in advance
>
>|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> "Dan Guzman" wrote:
>> Please post your connection string.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
>> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>> > Could anyone help?
>> >
>> > "Connection failed:
>> > SQLState: '01S00'
>> > SQL Server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
>> > Connection failed:
>> > SQLState: 'S1T00'
>> > SQL server Error: 0
>> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
>> >
>> > Thanks in advance
>>|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:
> The 'invalid connection string attribute' informational error is due to the
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also check
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > Here is the connection string:
> >
> > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> >
> > "Dan Guzman" wrote:
> >
> >> Please post your connection string.
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> >> > Could anyone help?
> >> >
> >> > "Connection failed:
> >> > SQLState: '01S00'
> >> > SQL Server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> >> > Connection failed:
> >> > SQLState: 'S1T00'
> >> > SQL server Error: 0
> >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >> >
> >> > Thanks in advance
> >>
> >>
> >>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>|||Can I remove the MDAC?
"AnthonyThomas" wrote:
> Try changing the order of the parameters. Normally, the DSN will have a designated DATABASE parameter, although this can be overridden. But how could it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the client. This has a nasty habit of messing with ODBC. You might want to use the ODBC Administrator and recheck the DSN attributes. When you're done, use the TEST CONNECTION capability to validate the attributes.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:
> > The 'invalid connection string attribute' informational error is due to the
> > extraneous 'OPEN=ODBC' specification. Try removing it:
> >
> > DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> >
> > I don't know what API you are using but the default command timeout is 30
> > seconds. In the case of ADO, you can specify a longer interval with the
> > CommandTimeout command object property. Specify 0 for unlimitted. You
> > might also consider query/index tuning to speed up the query and also check
> > for blocking.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
> > > Here is the connection string:
> > >
> > > OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> > >
> > > "Dan Guzman" wrote:
> > >
> > >> Please post your connection string.
> > >>
> > >> --
> > >> Hope this helps.
> > >>
> > >> Dan Guzman
> > >> SQL Server MVP
> > >>
> > >> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> > >> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> > >> > Could anyone help?
> > >> >
> > >> > "Connection failed:
> > >> > SQLState: '01S00'
> > >> > SQL Server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > >> > Connection failed:
> > >> > SQLState: 'S1T00'
> > >> > SQL server Error: 0
> > >> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> > >> >
> > >> > Thanks in advance
> > >>
> > >>
> > >>
> >
> >
> >

[Microsoft][ODBC SQL Server Driver]Timeout expired"

Could anyone help?
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribu
te
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
Thanks in advancePlease post your connection string.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
> Could anyone help?
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attri
bute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> Thanks in advance|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
"Dan Guzman" wrote:

> Please post your connection string.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:9F8B08B1-26CF-4601-8457-C7E810149812@.microsoft.com...
>
>|||The 'invalid connection string attribute' informational error is due to the
extraneous 'OPEN=ODBC' specification. Try removing it:
DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
I don't know what API you are using but the default command timeout is 30
seconds. In the case of ADO, you can specify a longer interval with the
CommandTimeout command object property. Specify 0 for unlimitted. You
might also consider query/index tuning to speed up the query and also check
for blocking.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
> "Dan Guzman" wrote:
>|||It hs been always working with that string. Anyway, I'm going to try to see
if it works.
Thanks
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to th
e
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also chec
k
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>|||It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to th
e
> extraneous 'OPEN=ODBC' specification. Try removing it:
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
> I don't know what API you are using but the default command timeout is 30
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also chec
k
> for blocking.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>|||Try changing the order of the parameters. Normally, the DSN will have a des
ignated DATABASE parameter, although this can be overridden. But how could
it be if it hasn't loaded from the DSN yet.
Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM
_CALLISTO'
Another possibility is that a recent MDAC release or patch has been applied
to the client. This has a nasty habit of messing with ODBC. You might want
to use the ODBC Administrator and recheck the DSN attributes. When you're
done, use the TEST CONNECTION capability to validate the attributes.
Sincerely,
Anthony Thomas
--
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
It didn't connect when I remove 'OPEN=ODBC'
"Dan Guzman" wrote:

> The 'invalid connection string attribute' informational error is due to
the
> extraneous 'OPEN=ODBC' specification. Try removing it:
>
> DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO
>
> I don't know what API you are using but the default command timeout is 3
0
> seconds. In the case of ADO, you can specify a longer interval with the
> CommandTimeout command object property. Specify 0 for unlimitted. You
> might also consider query/index tuning to speed up the query and also ch
eck
> for blocking.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in messag
e
> news:4A6C5752-A705-40CC-81B7-8FAAF54F2AE8@.microsoft.com...
>
>
>|||In my ADO test, ODBC ignored the ODBC attribute in the connection string,
returned an informational message and successfully connected. Without the
attribute, the connection was successful without the message. What API are
you using? Perhaps the ODBC attribute is required by a high-level API that
you are using. I'd expect the API to remove the attribute before passing it
to ODBC, though.
In any case, I suggest you follow the suggestions in my earlier response to
resolve the timeout problem.
Hope this helps.
Dan Guzman
SQL Server MVP
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>|||Can I remove the MDAC?
"AnthonyThomas" wrote:

> Try changing the order of the parameters. Normally, the DSN will have a d
esignated DATABASE parameter, although this can be overridden. But how coul
d it be if it hasn't loaded from the DSN yet.
> Try 'OPEN=ODBC;DSN=AFM_CALLISTO;DATABASE=AFM
_CALLISTO'
> Another possibility is that a recent MDAC release or patch has been applied to the
client. This has a nasty habit of messing with ODBC. You might want to use the OD
BC Administrator and recheck the DSN attributes. When you're done, use the TEST CON
NEC
TION capability to validate the attributes.[vbcol=seagreen]
> Sincerely,
>
> Anthony Thomas
>
> --
> "Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in messag
e news:87584EDE-BCFE-401D-81DF-38A260BFD0D5@.microsoft.com...
> It didn't connect when I remove 'OPEN=ODBC'
>
> "Dan Guzman" wrote:
>

[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2

Heres my code:

<%
'Dimension variables
Dim adoCon 'Holds the Database Connection Object
Dim rsAddLinks 'Holds the recordset for the new record to be added
Dim strSQL 'Holds the SQL query to query the database

'Create an ADO connection object
Set adoCon = Server.CreateObject("ADODB.Connection")

'Set an active connection to the Connection object using a DSN-less connection
adoCon.Open "DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=" & Server.MapPath("links.mdb")

'Create an ADO recordset object
Set rsAddLinks = Server.CreateObject("ADODB.Recordset")

'Initialise the strSQL variable with an SQL statement to query the database
strSQL = "SELECT tblLinks.URL, tblLinks.Description FROM tblLinks;"

'Set the cursor type we are using so we can navigate through the recordset
rsAddLinks.CursorType = 2

'Set the lock type so that the record is locked by ADO when it is updated
rsAddLinks.LockType = 3

'Open the recordset with the SQL query
rsAddLinks.Open strSQL, adoCon

'Tell the recordset we are adding a new record to it
rsAddLinks.AddNew

'Add a new record to the recordset
rsAddLinks.Fields("URL") = Request.Form("url")
rsAddLinks.Fields("Description") = Request.Form("description")

'Write the updated recordset to the database
rsAddLinks.Update

'Reset server objects
rsAddLinks.Close
Set rsAddLinks = Nothing
Set adoCon = Nothing

'Redirect to the guestbook.asp page
Response.Redirect "links.asp"
%>

When i run the code I get: [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2

Can someone please help?

--NickTry replacing % in place of *.|||Ok, thanks, but now it says

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Can you help me on this?

--Nick

PS: If your wondering, im reletively new at asp thats why I havent been able to figure this out myself.|||By all means refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to get rid of the issues and follwup.|||That really didn't help me much.|||thanks for all your help. I figured it out! i was linking to the page directly when i should have been using the page b4 it that links to it...

if that makes any scence

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users &
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.
Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.
|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post the
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>
|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[Microsoft][ ODBC SQL Server Drive ] Timeout expired

I am running a VB application which makes connection to the SQL server
database using DSN connection using ODBC. This application pulls data using
stored procedure. The application does not insert / delete / update data.
The application was working fine since it has been installed (more than ONE
year). Suddendly it has started generating runtime error '-2147217871
(80040e31)'. I have taken the following actions so far to identify the
problem:
1. Checked user permission set on the database. Its fine. ODBC test
connection is successful.
2. Debugged VB source. It successfully makes connection to the database but
generated error while executing Command object which is using a stored
procedure which pulls the data into the grid.
3. Changed the timeout property of the Command object to 60 seconds. Still
generating error.
4. Copy pasted Query from stored procedure into Query Analyzer. The query
ran within 10 seconds generating desired resultset. Hence, Table index /
fragmentation problem is ruled out.
5. Copy data and Object from Live database into another database on the same
server using DTS wizard. Changed database name in the ODBC configuration
pointing it to the new database having same data & objects (including users
&
permissions). The application ran succussefully without generating any
error. Hence database server problem is ruled out.
6. The stored procedure used by the command object in VB code fails to
execute.
Any help on how to fix this problem?
Manish Acharya
Systems Analyst & database developer
Task Transactions Ltd., New Zealand.Have you considered taking ODBC or SQL Server Profiler traces? These might
give more clues.
"Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in message
news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>I am running a VB application which makes connection to the SQL server
> database using DSN connection using ODBC. This application pulls data
> using
> stored procedure. The application does not insert / delete / update data.
> The application was working fine since it has been installed (more than
> ONE
> year). Suddendly it has started generating runtime error '-2147217871
> (80040e31)'. I have taken the following actions so far to identify the
> problem:
> 1. Checked user permission set on the database. Its fine. ODBC test
> connection is successful.
> 2. Debugged VB source. It successfully makes connection to the database
> but
> generated error while executing Command object which is using a stored
> procedure which pulls the data into the grid.
> 3. Changed the timeout property of the Command object to 60 seconds.
> Still
> generating error.
> 4. Copy pasted Query from stored procedure into Query Analyzer. The query
> ran within 10 seconds generating desired resultset. Hence, Table index /
> fragmentation problem is ruled out.
> 5. Copy data and Object from Live database into another database on the
> same
> server using DTS wizard. Changed database name in the ODBC configuration
> pointing it to the new database having same data & objects (including
> users &
> permissions). The application ran succussefully without generating any
> error. Hence database server problem is ruled out.
> 6. The stored procedure used by the command object in VB code fails to
> execute.
> Any help on how to fix this problem?
> Manish Acharya
> Systems Analyst & database developer
> Task Transactions Ltd., New Zealand.|||Thanks Chris for your response. I have been working on SQL server profiler
traces to identify this problem. My experience on using SQL server profiler
is a bit limited and I see this as an opportunity to hone my skills in this
area. Your reply confirms that I am on the right direction. I will post th
e
solution in this discussion group once I crack it.
Cheers.
Manish Acharya.
"Chris Lee[MS]" wrote:

> Have you considered taking ODBC or SQL Server Profiler traces? These might
> give more clues.
> "Manish Acharya" <Manish Acharya@.discussions.microsoft.com> wrote in messa
ge
> news:B4ACB30B-2D2B-4473-A802-6CB2E145BD82@.microsoft.com...
>
>|||Hi Manish Acharya,
Had you find the solution for the problem above? I have the same problem
like you, so hope you can shared the solution with us.
Thank you.

[HELP!] How do you make the database path relative in the connection string?

Hi everyone,

I am working on a Hospital Information System project with a team of 6.Each one of us builds or modifies a part of the system and shares the project over a common repository. The problem here is that we use the absolute path of the database in our connection string. Although the directory structure of our project is the same for each member, since the main project folder itself is stored in different locations on each person's computer (for example, one may have it stored in c:\My Documents and the other in d:\ My Documents), we are forced to modify the connection string manually each time someone else from the team updates the repository with the database. How do we make the path of the database relative so that we don't have to modify the connection string manually each time after receiving an update from the repository?

Your help is greatly appreciated.

If you're referencing the path, then I wonder what database you are using. e.g. for MSSQL you would refer to a server and the database on that server, generally just '.' for a local server

Lot's of ways you could do this, e.g. I've just been playing with clickonce install and this is one I use;

connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\dbRaptor_Data.mdf;Integrated Security=True;User Instance=True"

[DBNETLIB][ConnectionWrite (send()).] General network error.

Hi,
in our environment
- Windows XP
- SQL Server Express 2005
- Internet connection via TCP/IP protocol

The described network error occurs, when we unplug the network cable:
[DBNETLIB][ConnectionWrite (send()).] General network error.

The affected database resides on the locally installed SQLExpress, it doesn't use any network connections. The error doesn't occur immediately, in most cases there are up to 30 seconds where data can be (correctly!) written to the recordset, but after that timeout the connetion is broken.

We already tried out the described workarounds:
- disable named pipes protocol
- set SynAttackProtect=0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The error doesn't occur with MSDE (SQL 2000) or under Vista.

Thanks for help!

Mathias

I suggest using shared memory to connect locally or making sure your server specification is one that correctly gets resolved to use the loopback (e.g. .\ or (local) or localhost). You may also want to see if your hosts file has an entry for the machine to make sure it resolves its own name. Right now, it appears as though your communications are going out over the network. You may have some amount of data transfer after unplugging the cable because the network connection is buffered, so the server still has that much data in its network buffer before it runs out. I think the connection timeout is consuming the bulk of that 30 seconds. Vista most likely has its own hostname in its hosts file, or has some other trick for self-resolving its computer name. More than likely, your instance of SQL 2000 is using shared memory to connect or using a different specification of the hostname.

Hope that helps,

John

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied - PLEASE

Hi have created an application in asp.net to connect to a sql database.
The reason why I am sooooo very confused is because the connection to the database works if i keep the project on my local machine and connect to the database on the server, but as soon as I upload the project to the server, I get the following error when I try to connect to the database:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
Can anyone tell me why this is happenning? - PLEASE - Any help will be appreciated
Thanks,
Danielle


you might want to check your connection string and make sure its pointing to the rigtht database server.

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake().]SSL Server error

For some reason, I'm no longer able to connect to any database on SQL Server.

If I click on the + sign before a Data Connection in Visual Studio Server Explorer, a Logon dialog opens. Whatever I enter in the dialog results in the following error message:

Connection failed.

Sql State: '0 80001'

Sql Server Error: 18

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake().] SSL Server error

Help please.

What version of SQL Server are you using?

Have you tried connecting through some other method, such as using sqlcmd/osql or Management Studio/Query Analyzer?

What errors appear in the server errorlog?

Thanks
Laurentiu

|||

I'm using SQL Server 2000.

I've tried several ways to connect, all unsuccessful.

With Management Studio, I get the following error:

Cannot connect to COMPAC

Additional Information:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

With Query Analyzer

Unable to connect to server COMPAC

Server: Msg 18, level 16, State 1

[Microsoft]]ODBE SQL Server Driver]

[Shared Memory] SSL Security Error

With Enterprise Manager

A connection could not be established to (local)

Reason: SSL Security error

Connection Open (SECDoClientHandshake())

Please verify SQL Server is running and check your SQL Server registration properties(by right-clicking on the (local) node and try again.

(The Server was running according to SQL Service Manager, and right-clicking said node/properties returned the same error)

Thanks for your consideration.

|||

Is there an error in the server errorlog? Look into MSSQL\Log directory for the latest ERRORLOG files. If there is an error there, please add it to this thread.

I'll move the thread to the data access forum, where someone might be able to help with this issue.

Thanks
Laurentiu

|||

I'm not up on reading the errorlog, so I've posted it at

http://www.e-windowsonline.com/errorlog.html

Thanks again

|||

The errorlogs don′t show anything in this case, the database is started up just fine. Have a look at the articles [1] and [2] at KB. Seems that you are trying to use SSL top connect to the server. Did you make the appropiate settings for SSL ? If you do not want to use SSL you have to disable the enforcement of encryption at the client and server side, otherwise the connection will be refused if not encrypted.

The settgin is stored at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib as of [3].

[1] http://support.microsoft.com/default.aspx?scid=kb;en-us;309398
[2] http://support.microsoft.com/default.aspx?scid=kb;en-us;302409
[3] http://support.microsoft.com/default.aspx?scid=kb;en-us;841695

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

I am moving the thread to the data access forum, because there's no login failure message in the log.

Thanks
Laurentiu

|||

Thanks for your email.

I check the settings at the key referred to and found the following:

ab (Default) REG_SZ (value not set)

ab Protocolorder REG_MULTI_SZ tcp np

and the key contains a folder TDS with:

ab (Default) REG_SZ (value not set)

ab (local) REG_SZ 7.0

ab COMPAC REG_SZ 7.0

Do you see any changes that need to be made?

Thanks

|||

Hi,

It is possilbe that if you enabled client-side 'force encryption' option but the sql server does not support SSL from server-side.

Please open Client Network Utility, (you can run cliconfg.exe from the Run menu). Make sure that 'foce encryption' is not checked.

Thx, -Justin

|||

Mostlikely, this is because your server does not have trusted certificate and client driver is configured to "Force protocol encryption". If you truly need to force encryption, you can take a look at

http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

Otherwise, you can use cliconfg.exe to turn off "Force protocol encryption". option.

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

[DBNETLIB] 2147467259(80004005) [Connection Write (Send()),] General Network Error

HI all

I am facing a problem on sql server 7 Desktop Engine with front end VB6 and ADO 2.8 my OS is windows 2000 Professional.

ie. I am doing appendchunk to add image files on SQL Table it works fine for Approximately 130 MB, But i am trying to add 249 MB size file it will be showing these error Message.

[DBNETLIB] 2147467259(80004005) [Connection write(send()),] General Network Error check your network documentation.

I do so many way to correct this problem but it stuck up overthere.

In vb appendchunk is completed and the error when Updated command starts (update command also going a long way then show the above mentioned error.

Any body have any idea or clue just tel me for experiment. and complete my project.

Once again I request you please help me.

Thanks in advance.

Note : it is working with Access Database very fine I am tested it But in Access not allow me to store me lots of images its only allow 2 GB storage totally in a table.

Error code 0x80004005 is a generic error that indicates something failed. Either the client or server broke the connection.

Two things you should try:

1. Attach SQL Profiler to trace the execution to determine if it is the client or server that is terminating the connection.

2. Check the ERRORLOG if there are any problems with the server.