Objects related to DB: error

Showing posts with label error. Show all posts

Friday, March 30, 2012

ODBC Error

Does anyone have idea on how to reslove this error message
below.
Error Source 4, code 01000 10054
[microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
ConnectionRead (recv())
Hello!
This could be due to multiple reasons. Can you locate the ERRORLOG.* files
(found in the LOG sub-folder under the SQL Server installation folder) and
send it across? That might help establish if anything's wrong on the server
side.
Also:
- do you get this issue from all clients or is it specific to a set of
client(s)?
- do you receive this issue only when running a specific query? what are you
trying to execute when you experience this issue?
- are the client and server separated by any kind of network equipment like
a router / firewall?
- will the issue occur if you run the query locally on the server?
Thanks!
Arvind.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
This posting is provided "AS IS" with no warranties, and confers no rights.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
"Aboki" <hcokoli@.yahoo.com> wrote in message
news:6b8301c475a3$bfab9a70$a401280a@.phx.gbl...
> Does anyone have idea on how to reslove this error message
> below.
>
> Error Source 4, code 01000 10054
> [microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
> ConnectionRead (recv())
>
sql

ODBC error

Dear all,
We are using Ipswitch email application “ICS 2006’ with SQL 2000
enterprise edition as database. Occasionally web mail users are facing the
below
error on their web page.
‘ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not enough space on
temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Driver’s
SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft Access
Driver] Not enough space on temporary disk.’
The problem gets rectified only after we restart the IIS service on the mail
server. What could be the reason for this problem? Kindly provide me with
your suggestions.
Regards
Ram
It's an error from MS Access - the cause depends on what you
are doing in Access, what version of Access, etc.
Try posting on one of the Access forums or newsgroups.
-Sue
On Sat, 17 Feb 2007 20:59:08 -0800, Ram
<Ram@.discussions.microsoft.com> wrote:

>Dear all,
> We are using Ipswitch email application ICS 2006 with SQL 2000
>enterprise edition as database. Occasionally web mail users are facing the
>below
>error on their web page.
> ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not enough space on
>temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Drivers
>SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft Access
>Driver] Not enough space on temporary disk.
>The problem gets rectified only after we restart the IIS service on the mail
>server. What could be the reason for this problem? Kindly provide me with
>your suggestions.
>Regards
>Ram
>

ODBC Error

I am trying to reinstall MSQL Server 2000, but the
installation fails. The sqlstp.log has the message
below. I have reinstalled MDAC and the error persists. Can someone tell me
what is wrong and how to fix
it?
Sincerely,
Alvin
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
driver={sql
server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
on SQL_HANDLE_ENV failed
SQL Server configuration failed.Hi
What OS and Edition are you trying to install SQL Server on? Do you have
admin rights on the machine?
Regards
Mike
"Alvin" wrote:
> I am trying to reinstall MSQL Server 2000, but the
> installation fails. The sqlstp.log has the message
> below. I have reinstalled MDAC and the error persists. Can someone tell me
> what is wrong and how to fix
> it?
> Sincerely,
> Alvin
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> driver={sql
> server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> on SQL_HANDLE_ENV failed
> SQL Server configuration failed.
>|||I am installing it on Server 2003 and yes, I have admin rights.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What OS and Edition are you trying to install SQL Server on? Do you have
> admin rights on the machine?
> Regards
> Mike
> "Alvin" wrote:
> > I am trying to reinstall MSQL Server 2000, but the
> > installation fails. The sqlstp.log has the message
> > below. I have reinstalled MDAC and the error persists. Can someone tell me
> > what is wrong and how to fix
> > it?
> >
> > Sincerely,
> > Alvin
> >
> > Starting Service ...
> >
> > SQL_Latin1_General_CP1_CI_AS
> >
> > -m -Q -T4022 -T3659
> >
> > Connecting to Server ...
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > driver={sql
> > server};server=DENISPUTNAMTOSH;UID=sa;PWD=;databas e=master
> >
> > [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle
> > on SQL_HANDLE_ENV failed
> >
> > SQL Server configuration failed.
> >
> >

ODBC Error

Hi All,
I am getting the following error message when I am trying to connect to SQL 2000 Server from SQL 7 Server using BCP/OSQL/ISQL etc., Can any one help me in fixing this problem.
NULL
COULD NOT CONNECT TO SQL SERVER
NULL
SQLState: 08001 Native Error: 6
Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL server not found.
NULL
SQLState: 01000 Native Error: 53
Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (CreateFile()).
Thanks & Regards
Balaji Prabhu.TBalaji,
What is the respective OS?Do you have only 'Named pipes' enabled?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Balaji Prabhu.T" <Balaji Prabhu.T@.discussions.microsoft.com> wrote in
message news:C15C3280-F0A5-418B-912B-018EE518AF14@.microsoft.com...
> Hi All,
> I am getting the following error message when I am trying to connect to
SQL 2000 Server from SQL 7 Server using BCP/OSQL/ISQL etc., Can any one help
me in fixing this problem.
> NULL
> COULD NOT CONNECT TO SQL SERVER
> NULL
> SQLState: 08001 Native Error: 6
> Info. Message: [Microsoft][ODBC SQL Server Driver][Named Pipes]Specified
SQL server not found.
> NULL
> SQLState: 01000 Native Error: 53
> Info. Message: [Microsoft][ODBC SQL Server Driver][Named
Pipes]ConnectionOpen (CreateFile()).
> Thanks & Regards
> Balaji Prabhu.T
>

Odbc error

Dear all
My one user has installed sql server 2000 enterprise edition , SP3
(8.00.0860) on my computer.
I have created one odbc connection to sql server.
When he want to connect to sql user via odbc in application he gets
following error
Statement(s) could not be prepared
Unable to close cursor
[Microsoft][ODBC SQL Server Driver]Invalid cursor stat
What can be the problem?
RegardsWhat language is the application written in? At least the failing module?
I have seen similar errors in both T/SQL (implying a Stored Procedure) and C
(api level calls) modules.
I suspect it needs to be relinked with your new modules. To me, it sounds
like the api calls either are for a different ODBC release or have messed up
pointers.
If you can supply error numbers and complete error messages, it woulld help
--
Joseph R.P. Maloney, CSP,CCP,CDP
"amish" wrote:
> Dear all
> My one user has installed sql server 2000 enterprise edition , SP3
> (8.00.0860) on my computer.
> I have created one odbc connection to sql server.
> When he want to connect to sql user via odbc in application he gets
> following error
> Statement(s) could not be prepared
> Unable to close cursor
> [Microsoft][ODBC SQL Server Driver]Invalid cursor stat
> What can be the problem?
> Regards
>

ODBC Error

Does anyone have idea on how to reslove this error message
below.
Error Source 4, code 01000 10054
[microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
ConnectionRead (recv())Hello!
This could be due to multiple reasons. Can you locate the ERRORLOG.* files
(found in the LOG sub-folder under the SQL Server installation folder) and
send it across? That might help establish if anything's wrong on the server
side.
Also:
- do you get this issue from all clients or is it specific to a set of
client(s)?
- do you receive this issue only when running a specific query? what are you
trying to execute when you experience this issue?
- are the client and server separated by any kind of network equipment like
a router / firewall?
- will the issue occur if you run the query locally on the server?
Thanks!
Arvind.
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
This posting is provided "AS IS" with no warranties, and confers no rights.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
"Aboki" <hcokoli@.yahoo.com> wrote in message
news:6b8301c475a3$bfab9a70$a401280a@.phx.gbl...
> Does anyone have idea on how to reslove this error message
> below.
>
> Error Source 4, code 01000 10054
> [microsoft][ODBC SQL SERVER Driver] [ TCP/IP Sockets]
> ConnectionRead (recv())
>sql

odbc error

Getting the following error:
SQL error. Stmt #: 1568 Error Position: 0 Return: 8602 -
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
provider returned message: Errors occurred] (SQLSTATE
01000) 7312
Scenario: application/database sitting on win nt4 server
running sql7 linked to a Windows 2000 server running sql
2000. Trigger on serverA trying to update table on
ServerB via linked server.Turn on trace flag 7300 to try to get better information.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

ODBC error

Hi,
I've a Third-Party application using a ODBC connection on a remote Acces fil
e (mdb file) (the file reside on a other server, so I map a drive).
I got this error
[[Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and that you a
re connected to the server on which the file resides.-1023]
Does someone have hints?
ThanksI'm not real clear on what is using what and where but in
general, you want to avoid mapped drives. Try using a UNC
path instead of a mapped drive.
-Sue
On Tue, 20 Apr 2004 07:51:05 -0700, RemCgi
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I've a Third-Party application using a ODBC connection on a remote Acces fi
le (mdb file) (the file reside on a other server, so I map a drive).
>I got this error
>[[Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a
valid path. Make sure that the path name is spelled correctly and that you
are connected to the server on which the file resides.-1023]
>Does someone have hints?
>Thanks

ODBC ERROR

We have a DTS package to upload data from SQL to PARADOX. We are using the
Microsoft Paradox- treiber driver. Data is uploaded from 2 sql tables to 2
paradox tables. Upload for one table works, but for the other one, we get
the following error message.
Microsoft [ODBC Paradox Driver]
Could not decrypt file.
Help!Hello,
As you mentioned in other post, you may want to enable odbc tracing
tempoarily to see if you could find any clue.
Control Panel->Administrative tools->Tracing
Based on my experience, this kind of issue is usually caused by some
special data type that cannot be converted properly by ODBC driver. You may
also want to check suspect datatype and try to use a different one to work
around the problem.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "docsql" <docsql@.noemail.nospam>
| Subject: ODBC ERROR
| Date: Wed, 10 Aug 2005 09:25:33 -0700
| Lines: 11
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <#AovigcnFHA.3316@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.odbc
| NNTP-Posting-Host: 206.170.189.88
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2576
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| We have a DTS package to upload data from SQL to PARADOX. We are using
the
| Microsoft Paradox- treiber driver. Data is uploaded from 2 sql tables to
2
| paradox tables. Upload for one table works, but for the other one, we
get
| the following error message.
|
| Microsoft [ODBC Paradox Driver]
| Could not decrypt file.
|
| Help!
|
|
||||Following is the exact error message.
--
Package Error
--
Error Source : Microsoft OLE DB Provider for ODBC Drivers
Error Description : [Microsoft][ODBC Paradox Driver] Could not decry
pt file.
OK
--
I tried turning on the ODBC tracing, but the log file is empty.
Help!
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message news:NW0TJ%23hnFHA.36
72@.TK2MSFTNGXA01.phx.gbl...
> Hello,
>
> As you mentioned in other post, you may want to enable odbc tracing
> tempoarily to see if you could find any clue.
>
> Control Panel->Administrative tools->Tracing
>
> Based on my experience, this kind of issue is usually caused by some
> special data type that cannot be converted properly by ODBC driver. You ma
y
> also want to check suspect datatype and try to use a different one to work
> around the problem.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ========================================
=============
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> --
> | From: "docsql" <docsql@.noemail.nospam>
> | Subject: ODBC ERROR
> | Date: Wed, 10 Aug 2005 09:25:33 -0700
> | Lines: 11
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> | Message-ID: <#AovigcnFHA.3316@.tk2msftngp13.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.odbc
> | NNTP-Posting-Host: 206.170.189.88
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2576
> | X-Tomcat-NG: microsoft.public.sqlserver.odbc
> |
> | We have a DTS package to upload data from SQL to PARADOX. We are using
> the
> | Microsoft Paradox- treiber driver. Data is uploaded from 2 sql tables t
o
> 2
> | paradox tables. Upload for one table works, but for the other one, we
> get
> | the following error message.
> |
> | Microsoft [ODBC Paradox Driver]
> | Could not decrypt file.
> |
> | Help!
> |
> |
> |
>|||Hello,
Since the issue only occurs on a specific table, live debug/user dump
analysis might be the efficient method to find clues. I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
If MS confirmed this is issue inside the product, they may consider a fix
or workaround for you. Also, support incident will be refunded.
Have a great day!
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| From: "docsql" <docsql@.noemail.nospam>
| References: <#AovigcnFHA.3316@.tk2msftngp13.phx.gbl>
<NW0TJ#hnFHA.3672@.TK2MSFTNGXA01.phx.gbl>
| Subject: Re: ODBC ERROR
| Date: Tue, 16 Aug 2005 11:20:30 -0700
| Lines: 208
| MIME-Version: 1.0
| Content-Type: multipart/alternative;
| boundary="--=_NextPart_000_0008_01C5A254.86DC1510"
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <ed9c08ooFHA.3996@.TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.odbc
| NNTP-Posting-Host: 206.170.189.88
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2593
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| Following is the exact error message.
| --
| Package Error
| --
| Error Source : Microsoft OLE DB Provider for ODBC Drivers
| Error Description : [Microsoft][ODBC Paradox Driver] Could not dec
rypt
file.
| --
| OK
| --
| I tried turning on the ODBC tracing, but the log file is empty.
| Help!
| "Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:NW0TJ%23hnFHA.3672@.TK2MSFTNGXA01.phx.gbl...
| > Hello,
| >
| > As you mentioned in other post, you may want to enable odbc tracing
| > tempoarily to see if you could find any clue.
| >
| > Control Panel->Administrative tools->Tracing
| >
| > Based on my experience, this kind of issue is usually caused by some
| > special data type that cannot be converted properly by ODBC driver. You
may
| > also want to check suspect datatype and try to use a different one to
work
| > around the problem.
| >
| > Best Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner Support
| >
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| >
| > ========================================
=============
| >
| >
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | From: "docsql" <docsql@.noemail.nospam>
| > | Subject: ODBC ERROR
| > | Date: Wed, 10 Aug 2005 09:25:33 -0700
| > | Lines: 11
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| > | X-RFC2646: Format=Flowed; Original
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| > | Message-ID: <#AovigcnFHA.3316@.tk2msftngp13.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.odbc
| > | NNTP-Posting-Host: 206.170.189.88
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.odbc:2576
| > | X-Tomcat-NG: microsoft.public.sqlserver.odbc
| > |
| > | We have a DTS package to upload data from SQL to PARADOX. We are
using
| > the
| > | Microsoft Paradox- treiber driver. Data is uploaded from 2 sql
tables to
| > 2
| > | paradox tables. Upload for one table works, but for the other one,
we
| > get
| > | the following error message.
| > |
| > | Microsoft [ODBC Paradox Driver]
| > | Could not decrypt file.
| > |
| > | Help!
| > |
| > |
| > |
| >
|

odbc error

Windows 2000 sp 3, sql 7.0 sp 4. When I try to go into
odbc under Admin tools, I get the following error:
Unable to load sql server odbc driver resource dll. The
application cannot continue.
I am not seeing any error in event viewer.
ThanksThe error is generally due to either a missing .rll file -
file is sqlsrv32.rll - or a version mismatch with the
corresponding dll file (sqlsrv32.dll).
Try running the component checker tool to verify your mdac
installation. It will help in diagnosing installation
issues. You can download the tool from:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Mon, 24 May 2004 18:53:49 -0700, "Sue"
<anonymous@.discussions.microsoft.com> wrote:

>Windows 2000 sp 3, sql 7.0 sp 4. When I try to go into
>odbc under Admin tools, I get the following error:
>
>Unable to load sql server odbc driver resource dll. The
>application cannot continue.
>I am not seeing any error in event viewer.
>Thanks|||It listed Mdac 2.6 sp 2.
Sue
>--Original Message--
>The error is generally due to either a missing .rll
file -
>file is sqlsrv32.rll - or a version mismatch with the
>corresponding dll file (sqlsrv32.dll).
>Try running the component checker tool to verify your
mdac
>installation. It will help in diagnosing installation
>issues. You can download the tool from:
>http://msdn.microsoft.com/data/mdac/default.aspx
>-Sue
>On Mon, 24 May 2004 18:53:49 -0700, "Sue"
><anonymous@.discussions.microsoft.com> wrote:
>
The[vbcol=seagreen]
>.
>|||Mdac 2.8 fixed the problem.

>--Original Message--
>It listed Mdac 2.6 sp 2.
>Sue
>file -
>mdac
into[vbcol=seagreen]
>The
>.
>|||Thanks for posting back. Updating your version of MDAC is
probably easier than fixing the current installation
problems.
-Sue
On Tue, 25 May 2004 11:36:53 -0700,
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mdac 2.8 fixed the problem.
>
>into

ODBC error

Dear all,
We are using Ipswitch email application “ICS 2006’ with SQL 2000
enterprise edition as database. Occasionally web mail users are facing the
below
error on their web page.
‘ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not en
ough space on
temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Dr
iver’s
SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft
Access
Driver] Not enough space on temporary disk.’
The problem gets rectified only after we restart the IIS service on the mail
server. What could be the reason for this problem? Kindly provide me with
your suggestions.
Regards
RamIt's an error from MS Access - the cause depends on what you
are doing in Access, what version of Access, etc.
Try posting on one of the Access forums or newsgroups.
-Sue
On Sat, 17 Feb 2007 20:59:08 -0800, Ram
<Ram@.discussions.microsoft.com> wrote:

>Dear all,
> We are using Ipswitch email application ICS 2006 with SQL 2000
>enterprise edition as database. Occasionally web mail users are facing the
>below
>error on their web page.
> ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not en
ough space on
>temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] D
rivers
>SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsof
t Access
>Driver] Not enough space on temporary disk.
>The problem gets rectified only after we restart the IIS service on the mai
l
>server. What could be the reason for this problem? Kindly provide me with
>your suggestions.
>Regards
>Ram
>sql

ODBC Error

I'm getting an error message I've never seen before when I installed my
application on a client's machine.
I've got seven machines at this location that all work fine, when I install
on a new machine, I can connect through ODBC Administrator; but, when I try
to connect through the program I get this error message:
[ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
[ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
I've looked on KB and have not been able to find anything specific on this
problem.
Any ideas?
Thanks in advance.This might be the same issue reported in the KB article at the link
http://support.microsoft.com/defaul...b;en-us;Q322144
Regards,
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Dennis Powell" <dennis.powell@.monroe.XXXXXXXXX> wrote in message
news:OA6%23L0fYFHA.2128@.TK2MSFTNGP15.phx.gbl...
> I'm getting an error message I've never seen before when I installed my
> application on a client's machine.
> I've got seven machines at this location that all work fine, when I
install
> on a new machine, I can connect through ODBC Administrator; but, when I
try
> to connect through the program I get this error message:
> [ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
> [ODBC SQL Server Driver][TCP/IP
> Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
> I've looked on KB and have not been able to find anything specific on
this
> problem.
> Any ideas?
> Thanks in advance.
>

ODBC Error

I get the following error (from my front-end Access app AND Query Analyzer)
when accessing a particular table. It is a rather large table, ~1,750,000
rows in it. I tried looking through "limitations" in BOL and couldn't find
anything. Is this a server setting or ODBC setting or... ?
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionChe
ckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection BrokenWhat are you trying to do with that much data? Access isn't designed
to handle scrolling through millions of rows, although you may be
having network issues, as the error message suggests. Restrict the
data fetched with a WHERE clause, or if it's a report, write a stored
procedure and call it through a pass-through query.
--mary
On Thu, 15 Apr 2004 17:03:47 -0700, "Ron Hinds"
<__NoSpam@.__NoSpamramac.com> wrote:

>I get the following error (from my front-end Access app AND Query Analyzer)
>when accessing a particular table. It is a rather large table, ~1,750,000
>rows in it. I tried looking through "limitations" in BOL and couldn't find
>anything. Is this a server setting or ODBC setting or... ?
>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCh
eckForData
>(CheckforData()).
>Server: Msg 11, Level 16, State 1, Line 0
>General network error. Check your network documentation.
>Connection Broken
>|||What I'm trying to do is populate a local table (BackOrders) that's actually
used in the form from a server table (SalesDetail). There is a constraint
(WHERE Customer=x AND QtyAvailable>0) but using DAO it still tries to fetch
the entire table. Here is the original SQL (pure Access 97 app):
INSERT INTO BackOrders (InvoiceNumber, InvoiceDate, Part, Price, QtyOrdered,
QtyAvailable, Description) SELECT SalesDetail.InvoiceNumber,
SalesDetail.InvoiceDate, SalesDetail.Part, SalesDetail.Price,
SalesDetail.QtyOrdered, Inventory.QtyAvailable, Inventory.Description FROM
SalesDetail INNER JOIN Inventory ON SalesDetail.Part = Inventory.Part WHERE
SalesDetail.Customer=x AND SalesDetail.QtyOrdered > SalesDetail.QtyShipped
AND Inventory.Qty - Inventory.QtyCommitted > 0 AND SalesDetail.BackOrder > 0
ORDER BY SalesDetail.invoiceDate DESC
Even if this worked as-is with SQL Server (it doesn't - gives the same
error), it would be horribly slow, so I wanted to optimize it by creating a
View of the server tables. But I don't know the value of 'x' (Customer)
until run time. So I used the following DDL to create the View on SQL
Server:
USE Prototype
GO
IF EXISTS (SELECT TABLE_NAME FROM INFORMATION_SCHEMA.VIEWS
WHERE TABLE_NAME = 'vBackOrder')
DROP VIEW vBackOrder
GO
CREATE VIEW vBackOrder AS
SELECT TOP 100 PERCENT SalesDetail.invoiceNumber, SalesDetail.invoiceDate,
SalesDetail.Part, SalesDetail.Price, SalesDetail.QtyOrdered, Inventory.Qty -
Inventory.QtyCommitted AS QtyAvailable, Inventory.Description
SalesDetail.Customer FROM SalesDetail INNER JOIN Inventory ON
SalesDetail.itemID = Inventory.invItemID WHERE SalesDetail.QtyOrdered >
SalesDetail.QtyShipped AND Inventory.Qty - Inventory.QtyCommitted > 0 AND
SalesDetail.BackOrder > 0 ORDER BY SalesDetail.invoiceDate DESC
GO
I linked vBackOrder in Access then used this DAO code to populate local
table BackOrders:
INSERT INTO BackOrders (InvoiceNumber, InvoiceDate, Part, Price, QtyOrdered,
QtyAvailable, Description) SELECT vBackOrder.InvoiceNumber,
vBackOrder.InvoiceDate, vBackOrder.Part, vBackOrder.Price,
vBackOrder.QtyOrdered, vBackOrder.QtyAvailable, vBackOrder.Description FROM
vBackOrder WHERE vBackOrder.Customer=x
This also gives the same error, as does attempting to open the linked
vBackOrder in Access. I then went to QA and tried just the SELECT portion of
the CREATE VIEW with the same result. To narrow it down, I tried SELECTing *
FROM Inventory - a little slow but no problem. I then tried the same thing
with SalesDetail and again get the same error. I have >300 server tables of
varying sizes in this app. SalesDetail is by far the largest, and it is the
*only* one I get the error on. So I'm assuming it has something to do with
the size.
"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
news:pflv701qqge68qf7u94r6bnetfkb1iuc53@.
4ax.com...
> What are you trying to do with that much data? Access isn't designed
> to handle scrolling through millions of rows, although you may be
> having network issues, as the error message suggests. Restrict the
> data fetched with a WHERE clause, or if it's a report, write a stored
> procedure and call it through a pass-through query.
> --mary
> On Thu, 15 Apr 2004 17:03:47 -0700, "Ron Hinds"
> <__NoSpam@.__NoSpamramac.com> wrote:
>
Analyzer)[vbcol=seagreen]
find[vbcol=seagreen]
>|||DAO is the problem. You're loading the Jet engine and using it for SQL
Server data operations, something it was never designed or optimized
to do. Create a stored procedure instead of a buinch of views. Stored
procedures support parameters and complex logic, and return a
read-only result set which you can use to populate your local table.
Call the stored procedure from a pass-through query where you set the
SQL syntax to something like this in your code (you can use DAO to set
properties of a QueryDef object and execute it):
qdef.SQL = "EXEC myproc 'paramvalue1', val2" etc.
qdef.Execute
Pass-through queries bypass the Jet engine when they're executed and
are the most efficient way of getting back large result sets since all
of the processing takes place on the server, not in Jet. You then
create either an Insert or Update query that selects from your
pass-through query into the local table. When you call the
insert/update query it will automatically execute the pass-through
query to get the records.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Fri, 16 Apr 2004 17:09:15 -0700, "Ron Hinds"
<__NoSpam@.__NoSpamramac.com> wrote:

>What I'm trying to do is populate a local table (BackOrders) that's actuall
y
>used in the form from a server table (SalesDetail). There is a constraint
>(WHERE Customer=x AND QtyAvailable>0) but using DAO it still tries to fetch
>the entire table. Here is the original SQL (pure Access 97 app):
>INSERT INTO BackOrders (InvoiceNumber, InvoiceDate, Part, Price, QtyOrdered
,
>QtyAvailable, Description) SELECT SalesDetail.InvoiceNumber,
>SalesDetail.InvoiceDate, SalesDetail.Part, SalesDetail.Price,
>SalesDetail.QtyOrdered, Inventory.QtyAvailable, Inventory.Description FROM
>SalesDetail INNER JOIN Inventory ON SalesDetail.Part = Inventory.Part WHERE
>SalesDetail.Customer=x AND SalesDetail.QtyOrdered > SalesDetail.QtyShipped
>AND Inventory.Qty - Inventory.QtyCommitted > 0 AND SalesDetail.BackOrder >
0
>ORDER BY SalesDetail.invoiceDate DESC
>Even if this worked as-is with SQL Server (it doesn't - gives the same
>error), it would be horribly slow, so I wanted to optimize it by creating a
>View of the server tables. But I don't know the value of 'x' (Customer)
>until run time. So I used the following DDL to create the View on SQL
>Server:
>USE Prototype
>GO
>IF EXISTS (SELECT TABLE_NAME FROM INFORMATION_SCHEMA.VIEWS
> WHERE TABLE_NAME = 'vBackOrder')
> DROP VIEW vBackOrder
>GO
>CREATE VIEW vBackOrder AS
>SELECT TOP 100 PERCENT SalesDetail.invoiceNumber, SalesDetail.invoiceDate,
>SalesDetail.Part, SalesDetail.Price, SalesDetail.QtyOrdered, Inventory.Qty
-
>Inventory.QtyCommitted AS QtyAvailable, Inventory.Description
>SalesDetail.Customer FROM SalesDetail INNER JOIN Inventory ON
>SalesDetail.itemID = Inventory.invItemID WHERE SalesDetail.QtyOrdered >
>SalesDetail.QtyShipped AND Inventory.Qty - Inventory.QtyCommitted > 0 AND
>SalesDetail.BackOrder > 0 ORDER BY SalesDetail.invoiceDate DESC
>GO
>I linked vBackOrder in Access then used this DAO code to populate local
>table BackOrders:
>INSERT INTO BackOrders (InvoiceNumber, InvoiceDate, Part, Price, QtyOrdered
,
>QtyAvailable, Description) SELECT vBackOrder.InvoiceNumber,
>vBackOrder.InvoiceDate, vBackOrder.Part, vBackOrder.Price,
>vBackOrder.QtyOrdered, vBackOrder.QtyAvailable, vBackOrder.Description FROM
>vBackOrder WHERE vBackOrder.Customer=x
>This also gives the same error, as does attempting to open the linked
>vBackOrder in Access. I then went to QA and tried just the SELECT portion o
f
>the CREATE VIEW with the same result. To narrow it down, I tried SELECTing
*
>FROM Inventory - a little slow but no problem. I then tried the same thing
>with SalesDetail and again get the same error. I have >300 server tables of
>varying sizes in this app. SalesDetail is by far the largest, and it is the
>*only* one I get the error on. So I'm assuming it has something to do with
>the size.
>"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
> news:pflv701qqge68qf7u94r6bnetfkb1iuc53@.
4ax.com...
>Analyzer)
>find
>|||Hi Mary,
BTW I have your book and it is very good. Unfortunately, for this project I
am stuck with Access 97 and the book seems to reference Access 2000 +.
Thanks for your help and that not only works but it is *much* faster! Looks
like I'll be retrofitting all of those Views I created! Thanks again!
Regards,
Ron Hinds
"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
news:c7d280ledkacc75n7ugk5jgd8v7bibuepa@.
4ax.com...
> DAO is the problem. You're loading the Jet engine and using it for SQL
> Server data operations, something it was never designed or optimized
> to do. Create a stored procedure instead of a buinch of views. Stored
> procedures support parameters and complex logic, and return a
> read-only result set which you can use to populate your local table.
> Call the stored procedure from a pass-through query where you set the
> SQL syntax to something like this in your code (you can use DAO to set
> properties of a QueryDef object and execute it):
> qdef.SQL = "EXEC myproc 'paramvalue1', val2" etc.
> qdef.Execute
> Pass-through queries bypass the Jet engine when they're executed and
> are the most efficient way of getting back large result sets since all
> of the processing takes place on the server, not in Jet. You then
> create either an Insert or Update query that selects from your
> pass-through query into the local table. When you call the
> insert/update query it will automatically execute the pass-through
> query to get the records.
> -- Mary
> Microsoft Access Developer's Guide to SQL Server
> http://www.amazon.com/exec/obidos/ASIN/0672319446
> On Fri, 16 Apr 2004 17:09:15 -0700, "Ron Hinds"
> <__NoSpam@.__NoSpamramac.com> wrote:
>
actually[vbcol=seagreen]
fetch[vbcol=seagreen]
QtyOrdered,[vbcol=seagreen]
FROM[vbcol=seagreen]
WHERE[vbcol=seagreen]
SalesDetail.QtyShipped[vbcol=seagreen]
> 0
a[vbcol=seagreen]
SalesDetail.invoiceDate,[vbcol=seagreen]
Inventory.Qty -[vbcol=seagreen]
QtyOrdered,[vbcol=seagreen]
FROM[vbcol=seagreen]
of[vbcol=seagreen]
SELECTing *[vbcol=seagreen]
thing[vbcol=seagreen]
of[vbcol=seagreen]
the[vbcol=seagreen]
with[vbcol=seagreen]
~1,750,000[vbcol=seagreen]
Sockets]ConnectionCheckForData[vbcol=sea
green]
>|||Although the book is for a newer version, the basic concepts remain
the same, and always will, which are: fetch only needed data and
perform as much data processing on the back end. Let the FE do
presentation tasks like formatting, etc. All of the code in the
chapters for linked tables will work pretty much as-is in Access 97.
--Mary
On Mon, 19 Apr 2004 14:08:04 -0700, "Ron Hinds"
<__NoSpam@.__NoSpamramac.com> wrote:

>Hi Mary,
>BTW I have your book and it is very good. Unfortunately, for this project I
>am stuck with Access 97 and the book seems to reference Access 2000 +.
>Thanks for your help and that not only works but it is *much* faster! Looks
>like I'll be retrofitting all of those Views I created! Thanks again!
>Regards,
>Ron Hinds
>
>"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
> news:c7d280ledkacc75n7ugk5jgd8v7bibuepa@.
4ax.com...
>actually
>fetch
>QtyOrdered,
>FROM
>WHERE
>SalesDetail.QtyShipped
>a
>SalesDetail.invoiceDate,
>Inventory.Qty -
>QtyOrdered,
>FROM
>of
>SELECTing *
>thing
>of
>the
>with
>~1,750,000
>Sockets]ConnectionCheckForData
>|||Ron,
Switch to an Access 2002 data project and dump the mdb. You are looking at
a complete rewrite. Access 2002 ADPs are VERY EASY to use. Access linked t
ables create multiple connections and are prone to creating deadlocks and mu
ltitudes of other problems.
Linked tables in Access 97 worked 'OK', linked tables in 2000 and on are not
usable in a production system.
"Ron Hinds" wrote:

> I get the following error (from my front-end Access app AND Query Analyzer
)
> when accessing a particular table. It is a rather large table, ~1,750,000
> rows in it. I tried looking through "limitations" in BOL and couldn't find
> anything. Is this a server setting or ODBC setting or... ?
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionC
heckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
>

ODBC error

Problem: I came in this morning, and our SQL server's IP address was
changed from a static to dynamic IP. I changed it back, but not sure if
that is the cause of the problem I am having.
Running some reports in Access 2000 that queries through ODBC to our SQL
Server 2k. We are getting an error when attempting to run the report.
*start error message
Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver] Invalid connection string attrib
ute
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] General Netw
ork
Error
*end of error message
What is going on? How do I resolve it? Thanks in advance
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!Something was up with the network side of accessing the SQL Server.
Rebooting the server cleared up the connection issues.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Hi! Good Day!
I have problem with my ODBC Data Source(32bit) which cannot
add,configure existing database because it will come up system error
code 31 (Microsoft Access Driver (*.mdb)) was missing or unable to load
the setup or translator library as well as another Micorosoft Office
database.
I'm asking for ur help.
Thank you.
jcp
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message519054.html

ODBC drivers errro '80040e14'

Hi Sir/Madam,
I have a error from my ASP, SQL application as :
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot sort a row
of size
8162, which is greater than the allowable maximum of 8094.
The SQL query in ASP code as:
SQL = "select * from Entry,Entrant where Entry.EntrantID=Entrant.EntrantID
and entry.Competition = 'MADC2004' order by CatID asc"
As long as I remove the 'order by CatID asc', the error gone. I don't
understand why the 'order by CatID' will cause the error. But I need to sort
the result.
Please help.....
Thank you very much
Ben LI'm guessing that the rows of your result set, since they come from two
tables, total more than 8094 bytes. Certainly you don't need to see
every column of each table, since at the least, you only need to display
EntrantID once, and if you can live with results without all the
columns, you may solve the problem. It's also possible that you really
don't ever have 8094+ bytes in any one row - this could be the case if
you have char or nchar columns where you might be fine with varchar or
nvarchar.
SK
B L wrote:

>Hi Sir/Madam,
>I have a error from my ASP, SQL application as :
>Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot sort a ro
w of size
>8162, which is greater than the allowable maximum of 8094.
>The SQL query in ASP code as:
>SQL = "select * from Entry,Entrant where Entry.EntrantID=Entrant.EntrantID
>and entry.Competition = 'MADC2004' order by CatID asc"
>As long as I remove the 'order by CatID asc', the error gone. I don't
>understand why the 'order by CatID' will cause the error. But I need to sor
t
>the result.
>Please help.....
>Thank you very much
>Ben L
>
>
>
>
>
>
>|||Hi Steve,
I selected less column and the query working now. Thank you very much for
the information.
Regards
Ben
"Steve Kass" <skass@.drew.edu> wrote in message
news:%23jGFhDZBEHA.3804@.TK2MSFTNGP09.phx.gbl...
> I'm guessing that the rows of your result set, since they come from two
> tables, total more than 8094 bytes. Certainly you don't need to see
> every column of each table, since at the least, you only need to display
> EntrantID once, and if you can live with results without all the
> columns, you may solve the problem. It's also possible that you really
> don't ever have 8094+ bytes in any one row - this could be the case if
> you have char or nchar columns where you might be fine with varchar or
> nvarchar.
> SK
> B L wrote:
>
Entry.EntrantID=Entrant.EntrantID
sort
>

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e rMaybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider no
w...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our
tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?[vbcol=seagreen]
>sql

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>
|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider now...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...[vbcol=seagreen]
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?
>

ODBC Drivers error '80004005'

Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
Danny
It looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>

ODBC Drivers error '80004005'

Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network er
ror.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
DannyIt looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General netwo
rk error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>

Friday, March 30, 2012

ODBC Error

ODBC Error

ODBC error

ODBC Error

ODBC Error

Odbc error

ODBC Error

odbc error

ODBC error

ODBC ERROR

odbc error

ODBC error

ODBC Error

ODBC Error

ODBC error

ODBC drivers errro '80040e14'

ODBC Drivers error '80040e31'

ODBC Drivers error '80040e31'

ODBC Drivers error '80004005'

ODBC Drivers error '80004005'

Objects related to DB

Blog Archive

About Me