OLEDB Provider for SQL Server Errors

Hi Yosh,
I saw a number of posting relating to the Jet database but I am not using
the Jet database in any way do I doubt that is the source. This app has
been installed on 20 Windows XP PCs for the last six months and the today is
the first time we have seen this happen. It is also occuring on multiple
PCs.
Thanks for your help,
Darrel
"Yosh" <yoshi@.nospam.com> wrote in message
news:Opnsn6twFHA.2072@.TK2MSFTNGP14.phx.gbl...
> Actually it sounds more like a JET error. Download and install the latest
> JET 4.0.
> That should fix the problem. It sounds like a JET 3.5 problem.
> Yosh
>Hello Darrel,
It seems to be a timeout issue. For example:
-3633 - Microsoft OLE DB Provider for SQL Server: Timeout expired
Error : 3633 : Microsoft OLEDB provider for ODBC drivers : Oracle ODBC ORA
ORA-01013 : User requested cancel of the current operation.
It is usually caused by performance or network issue. You could set
CommandTimeout of ADODB.command in client application to 0 if you never
want a command to timeout.
Also, it could be a driver related issue though it does not seem to be true
for this specific case.
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: "Darrel Miller" <darrel@.tavis.ca>
| References: <OQo8uXrwFHA.2228@.TK2MSFTNGP11.phx.gbl>
<#h6aRbrwFHA.612@.TK2MSFTNGP10.phx.gbl>
<#4wDOoswFHA.2312@.TK2MSFTNGP14.phx.gbl>
<eGkZa0twFHA.1996@.TK2MSFTNGP10.phx.gbl>
<Opnsn6twFHA.2072@.TK2MSFTNGP14.phx.gbl>
| Subject: Re: OLEDB Provider for SQL Server Errors
| Date: Mon, 26 Sep 2005 20:27:49 -0400
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Response
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <enHbMpvwFHA.3756@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.programming
| NNTP-Posting-Host: toronto-hse-ppp3944778.sympatico.ca 70.49.61.98
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.programming:120894
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| Hi Yosh,
|
| I saw a number of posting relating to the Jet database but I am not using
| the Jet database in any way do I doubt that is the source. This app has
| been installed on 20 Windows XP PCs for the last six months and the today
is
| the first time we have seen this happen. It is also occuring on multiple
| PCs.
|
| Thanks for your help,
|
| Darrel
|
| "Yosh" <yoshi@.nospam.com> wrote in message
| news:Opnsn6twFHA.2072@.TK2MSFTNGP14.phx.gbl...
| > Actually it sounds more like a JET error. Download and install the
latest
| > JET 4.0.
| >
| > That should fix the problem. It sounds like a JET 3.5 problem.
| >
| > Yosh
| >
|
|
||||You may want to check the SQL Server "Maximum concurrent user connections"
value under the SQL Server Properties Connection tab.
This variable states the following:
"Specify the maximum concurrent user connections. Entering zero means there
can be an unlimited number of concurrent user connections."
If the number of users trying to connect to the SQL Server instance exceeds
this value, you will have experience sporadic errors like the one you've
described. This includes the connections your application makes along with
all the other applications connecting to the SQL Server instance. Also,
think about all the developers or users using the query analyzer. Each query
window is a seperate connection.
One thing developers do is open multiple connections within their
application. If your application opens 3 connections and you have 20 users,
that will be 60 SQL Server connections.
Yosh
"Darrel Miller" <darrel@.tavis.ca> wrote in message
news:enHbMpvwFHA.3756@.tk2msftngp13.phx.gbl...
> Hi Yosh,
> I saw a number of posting relating to the Jet database but I am not using
> the Jet database in any way do I doubt that is the source. This app has
> been installed on 20 Windows XP PCs for the last six months and the today
> is the first time we have seen this happen. It is also occuring on
> multiple PCs.
> Thanks for your help,
> Darrel
> "Yosh" <yoshi@.nospam.com> wrote in message
> news:Opnsn6twFHA.2072@.TK2MSFTNGP14.phx.gbl...
>|||Hi Peter,
Thanks for the info. I was starting to expect it to be a timeout problem.
Now I just have to find out what is causing it. I don't suppose you can
point me to a place where I can see a list of the errors that the Microsoft
OLE DB Provider for SQL Server can generate? I would like to set traps for
these errors so that I can handle them properly.
Thanks,
Darrel
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:Ty7XIMxwFHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hello Darrel,
> It seems to be a timeout issue. For example:
> -3633 - Microsoft OLE DB Provider for SQL Server: Timeout expired
> Error : 3633 : Microsoft OLEDB provider for ODBC drivers : Oracle ODBC ORA
> ORA-01013 : User requested cancel of the current operation.
> It is usually caused by performance or network issue. You could set
> CommandTimeout of ADODB.command in client application to 0 if you never
> want a command to timeout.
>
> Also, it could be a driver related issue though it does not seem to be
> true
> for this specific case.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>|||Hi Yosh,
On the recommendation of another forum member I checked the max connections
property and it is set to zero.
Thanks for the suggestion,
Darrel
"Yosh" <yoshi@.nospam.com> wrote in message
news:uvhYDkxwFHA.3904@.TK2MSFTNGP10.phx.gbl...
> You may want to check the SQL Server "Maximum concurrent user connections"
> value under the SQL Server Properties Connection tab.
> This variable states the following:
> "Specify the maximum concurrent user connections. Entering zero means
> there can be an unlimited number of concurrent user connections."
> If the number of users trying to connect to the SQL Server instance
> exceeds this value, you will have experience sporadic errors like the one
> you've described. This includes the connections your application makes
> along with all the other applications connecting to the SQL Server
> instance. Also, think about all the developers or users using the query
> analyzer. Each query window is a seperate connection.
> One thing developers do is open multiple connections within their
> application. If your application opens 3 connections and you have 20
> users, that will be 60 SQL Server connections.
> Yosh
>
> "Darrel Miller" <darrel@.tavis.ca> wrote in message
> news:enHbMpvwFHA.3756@.tk2msftngp13.phx.gbl...
>|||Hello Darrel,
Sorry there are no document on this error at present, and your feedback on
this is routed to the proper channel. Also, if you want to trace the error
via live debug or user dump, we recommend that you contact Microsoft
Product Support Services and open a support incident and work with a
dedicated Support Professional.
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
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: "Darrel Miller" <darrel@.tavis.ca>
| References: <OQo8uXrwFHA.2228@.TK2MSFTNGP11.phx.gbl>
<#h6aRbrwFHA.612@.TK2MSFTNGP10.phx.gbl>
<#4wDOoswFHA.2312@.TK2MSFTNGP14.phx.gbl>
<eGkZa0twFHA.1996@.TK2MSFTNGP10.phx.gbl>
<Opnsn6twFHA.2072@.TK2MSFTNGP14.phx.gbl>
<enHbMpvwFHA.3756@.tk2msftngp13.phx.gbl>
<Ty7XIMxwFHA.768@.TK2MSFTNGXA01.phx.gbl>
| Subject: Re: OLEDB Provider for SQL Server Errors
| Date: Tue, 27 Sep 2005 01:34:48 -0400
| Lines: 41
| 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
| X-RFC2646: Format=Flowed; Original
| Message-ID: <#MwkvUywFHA.2960@.tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.programming
| NNTP-Posting-Host: locweld.com 69.70.2.194
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.programming:120918
| X-Tomcat-NG: microsoft.public.sqlserver.programming
|
| Hi Peter,
|
| Thanks for the info. I was starting to expect it to be a timeout
problem.
| Now I just have to find out what is causing it. I don't suppose you can
| point me to a place where I can see a list of the errors that the
Microsoft
| OLE DB Provider for SQL Server can generate? I would like to set traps
for
| these errors so that I can handle them properly.
|
| Thanks,
|
| Darrel
|
|
| "Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
| news:Ty7XIMxwFHA.768@.TK2MSFTNGXA01.phx.gbl...
| > Hello Darrel,
| >
| > It seems to be a timeout issue. For example:
| >
| > -3633 - Microsoft OLE DB Provider for SQL Server: Timeout expired
| >
| > Error : 3633 : Microsoft OLEDB provider for ODBC drivers : Oracle ODBC
ORA
| > ORA-01013 : User requested cancel of the current operation.
| >
| > It is usually caused by performance or network issue. You could set
| > CommandTimeout of ADODB.command in client application to 0 if you never
| > want a command to timeout.
| >
| >
| > Also, it could be a driver related issue though it does not seem to be
| > true
| > for this specific case.
| >
| > Best Regards,
| >
| > Peter Yang
| > MCSE2000/2003, MCSA, MCDBA
| > Microsoft Online Partner Support
| >
|
|
|