Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Let me share the Possibilities & fix of the following error:
The error appeares only peak hrs. (when more request comes)
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
/News/Home.asp, line 121
Thanks in Advance
Dil
From Dil :
> Hi
> Let me share the Possibilities & fix of the following error:
> The error appeares only peak hrs. (when more request comes)
>
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
> /News/Home.asp, line 121
> Thanks in Advance
> Dil
Well, since you're not sharing, how about
http://www.aspfaq.com/show.asp?id=2287

Microsoft Knowledge Base Article - 311111 Question

SQL 7.0 intermittently throws connection errors, the above
KB article seems to describe them.
Do I read the "FIX" correctly, that I should install SP1
for SQL2000 on my machine running SQL7.0?
Didn't make sense to me...
TIA
If you read the article more closely, you'll see that there is a recommended action for both SQL2K and for
SQL7.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tony" <awr@.shaw.ca> wrote in message news:ab5201c436ad$7afb53f0$a401280a@.phx.gbl...
> SQL 7.0 intermittently throws connection errors, the above
> KB article seems to describe them.
> Do I read the "FIX" correctly, that I should install SP1
> for SQL2000 on my machine running SQL7.0?
> Didn't make sense to me...
> TIA

Microsoft Knowledge Base Article - 311111 Question

SQL 7.0 intermittently throws connection errors, the above
KB article seems to describe them.
Do I read the "FIX" correctly, that I should install SP1
for SQL2000 on my machine running SQL7.0?
Didn't make sense to me...
TIAIf you read the article more closely, you'll see that there is a recommended
action for both SQL2K and for
SQL7.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tony" <awr@.shaw.ca> wrote in message news:ab5201c436ad$7afb53f0$a401280a@.phx.gbl...eagreen">
> SQL 7.0 intermittently throws connection errors, the above
> KB article seems to describe them.
> Do I read the "FIX" correctly, that I should install SP1
> for SQL2000 on my machine running SQL7.0?
> Didn't make sense to me...
> TIAsql

Microsoft Knowledge Base Article - 311111 Question

SQL 7.0 intermittently throws connection errors, the above
KB article seems to describe them.
Do I read the "FIX" correctly, that I should install SP1
for SQL2000 on my machine running SQL7.0?
Didn't make sense to me...
TIAIf you read the article more closely, you'll see that there is a recommended action for both SQL2K and for
SQL7.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Tony" <awr@.shaw.ca> wrote in message news:ab5201c436ad$7afb53f0$a401280a@.phx.gbl...
> SQL 7.0 intermittently throws connection errors, the above
> KB article seems to describe them.
> Do I read the "FIX" correctly, that I should install SP1
> for SQL2000 on my machine running SQL7.0?
> Didn't make sense to me...
> TIA

Microsoft JDBC Driver XA Problem

Hi,
I have applied XA support via the dll and script...but now I got the
following error. Anyone can point me a direction to fix this?
Thanks,
j-
20:44:06 [tyrex.resource.n3-db] [main] [transaction server is recovering] []
[] ERROR - Failed to create connection for default user
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC][SQLServer]xa_open (0) returns -3
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown
Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.exec uteUpdate(Unknown Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.open(Unknown Source)
at com.microsoft.jdbcx.base.BaseXAConnection.<init>(U nknown Source)
at com.microsoft.jdbcx.base.BaseXADataSource.getXACon nection(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerDataSource. getXAConnection(Unknown
Source)
at
tyrex.resource.jdbc.ConnectionPool.createPooledCon nection(ConnectionPool.java:841)
at
tyrex.resource.jdbc.ConnectionPool.completeInit(Co nnectionPool.java:256)
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:222)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:582)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
20:44:09 [tyrex.resource.n3-db] [main] [null] [] [] ERROR - Failed to create
connection for default user java.sql.SQLException: [Microsoft][SQLServer
2000 Driver for JDBC][SQLServer]xa_open (0) returns -3
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown
Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.exec uteUpdate(Unknown Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.executeXaRpc(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerImplXAResou rce.open(Unknown Source)
at com.microsoft.jdbcx.base.BaseXAConnection.<init>(U nknown Source)
at com.microsoft.jdbcx.base.BaseXADataSource.getXACon nection(Unknown
Source)
at
com.microsoft.jdbcx.sqlserver.SQLServerDataSource. getXAConnection(Unknown
Source)
at
tyrex.resource.jdbc.ConnectionPool.createPooledCon nection(ConnectionPool.java:841)
at
tyrex.resource.jdbc.ConnectionPool.completeInit(Co nnectionPool.java:256)
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:222)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:626)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
20:44:10 [n3.common.module] [main] [null] [] [] WARN - Failed the initialize
module 'TransactionManager'
20:44:10 [n3.common.module] [main] [null] [] [] FATAL - ModulesManager
tyrex.resource.ResourceException: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]xa_open (0) returns -3
at
tyrex.resource.jdbc.ConnectionPool.<init>(Connecti onPool.java:225)
at
tyrex.resource.jdbc.DataSourceConfig.createResourc e_(DataSourceConfig.java:237)
at
tyrex.resource.ResourceConfig.createResource(Resou rceConfig.java:390)
at tyrex.resource.Resources.getResource(Resources.jav a:235)
at
tyrex.tm.impl.TransactionServerImpl.recover(Transa ctionServerImpl.java:582)
at
com.intalio.n3.common.tyrex.TyrexModule.initialize (TyrexModule.java:130)
at
com.intalio.n3.common.module.ModulesManager.initia lizeModule(ModulesManager.java:373)
at
com.intalio.n3.common.module.ModulesManager.initia lizeAllModules(ModulesManager.java:263)
at com.intalio.n3.Main.start(Main.java:454)
at com.intalio.n3.Main.main(Main.java:239)
Jay Shen wrote:
> Hi,
> I have applied XA support via the dll and script...but now I got the
> following error. Anyone can point me a direction to fix this?
> Thanks,
> j-
> 20:44:06 [tyrex.resource.n3-db] [main] [transaction server is recovering] []
> [] ERROR - Failed to create connection for default user
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
> JDBC][SQLServer]xa_open (0) returns -3
> at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
Hi Jay,
Seems, that you haven't started the DTC (Distributed Transaction
Coordinator) service. This service is installed during the
MS SQL Server 2000 installation but with start type 'manual'.
BTW: which user do you use to connetc to the database ? If you don't
use sa (which would be a good idea) have in mind, that XA recovery is
only allowed for a system administrator. To allow all users to perform
XA recovery, you have to add the EXEC permission to PUBLIC for the
stored procedure xp_jdbc_recover (part of extended stored procedures) in
the master database.
Best,
Manfred
|||Thanks a lot, Manfred.
I did apply the suggestion to grant the rights. But for some reason, I am
still getting the same errors...weird...
"Manfred Rosenboom" <marochess@.gmx.de> wrote in message
news:d3dpcu$d6c$1@.nntp.fujitsu-siemens.com...
> Jay Shen wrote:
> Hi Jay,
> Seems, that you haven't started the DTC (Distributed Transaction
> Coordinator) service. This service is installed during the
> MS SQL Server 2000 installation but with start type 'manual'.
> BTW: which user do you use to connetc to the database ? If you don't
> use sa (which would be a good idea) have in mind, that XA recovery is
> only allowed for a system administrator. To allow all users to perform
> XA recovery, you have to add the EXEC permission to PUBLIC for the stored
> procedure xp_jdbc_recover (part of extended stored procedures) in the
> master database.
> Best,
> Manfred
|||| From: "Jay Shen" <jay_shen@.msn.com>
| References: <eGLZClkPFHA.248@.TK2MSFTNGP15.phx.gbl>
<d3dpcu$d6c$1@.nntp.fujitsu-siemens.com>
| Subject: Re: Microsoft JDBC Driver XA Problem
| Date: Mon, 11 Apr 2005 14:13:59 -0700
| Lines: 38
| 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; Response
| Message-ID: <eTZJittPFHA.4004@.TK2MSFTNGP15.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: adsl-67-113-30-33.snfc21.pacbell.net 67.113.30.33
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP15.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.jdbcdriver:1029
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| Thanks a lot, Manfred.
|
| I did apply the suggestion to grant the rights. But for some reason, I am
| still getting the same errors...weird...
|
| "Manfred Rosenboom" <marochess@.gmx.de> wrote in message
| news:d3dpcu$d6c$1@.nntp.fujitsu-siemens.com...
| > Jay Shen wrote:
| >> Hi,
| >>
| >> I have applied XA support via the dll and script...but now I got the
| >> following error. Anyone can point me a direction to fix this?
| >> Thanks,
| >>
| >> j-
| >>
| >> 20:44:06 [tyrex.resource.n3-db] [main] [transaction server is
recovering]
| >> [] [] ERROR - Failed to create connection for default user
| >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
| >> JDBC][SQLServer]xa_open (0) returns -3
| >> at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown
| > Hi Jay,
| >
| > Seems, that you haven't started the DTC (Distributed Transaction
| > Coordinator) service. This service is installed during the
| > MS SQL Server 2000 installation but with start type 'manual'.
| >
| > BTW: which user do you use to connetc to the database ? If you don't
| > use sa (which would be a good idea) have in mind, that XA recovery is
| > only allowed for a system administrator. To allow all users to perform
| > XA recovery, you have to add the EXEC permission to PUBLIC for the
stored
| > procedure xp_jdbc_recover (part of extended stored procedures) in the
| > master database.
| >
| > Best,
| > Manfred
|
|
|
Are you using the sqljdbc.dll and driver .jar files that come with JDBC
SP3? Did you test with the actual SA account and see the same problem?
You can capture a SQL Profiler trace (with all Errors and Warnings events
and all data columns) and see if you are truly getting a permissions issue
on the execution of the extended stored procedures.
Aside from that, ensure that MSDTC is started and that XA is enabled.
Check the registry key HKLM\Software\Microsoft\MSDTC\Security. The Value
name is XATransactions, and it is a REG_DWORD value. A value of 0 means XA
transactions are disabled. A non-zero value means they are enabled. If
you have to change this from 0 to 1, restart the SQL Server service and
MSDTC service.
If the above information does not resolve the issue, post the Java code and
table definition that you use to reproduce the problem.
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft help! Trying to send reports via email using RS2000

I keep getting these errorrs. I am using RS 2000. What does this mean and
how do I fix this issue?
2007-09-25 11:00:25 - + [000] Schedule 143 has already been cached by job
0xF155CEC465AE154F8A73A19FB303190D
2007-09-25 11:01:02 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 143
2007-09-25 11:01:02 - + [163] 1 operations applied (0 remaining)
2007-09-25 11:03:32 - + [000] Schedule 144 has already been cached by job
0xEA305CE0F980DA49B68D71B6CC693AA9
2007-09-25 11:04:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 144
2007-09-25 11:04:01 - + [163] 1 operations applied (0 remaining)On Sep 25, 10:24 am, OriginalStealth
<OriginalStea...@.discussions.microsoft.com> wrote:
> I keep getting these errorrs. I am using RS 2000. What does this mean and
> how do I fix this issue?
> 2007-09-25 11:00:25 - + [000] Schedule 143 has already been cached by job
> 0xF155CEC465AE154F8A73A19FB303190D
> 2007-09-25 11:01:02 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 143
> 2007-09-25 11:01:02 - + [163] 1 operations applied (0 remaining)
> 2007-09-25 11:03:32 - + [000] Schedule 144 has already been cached by job
> 0xEA305CE0F980DA49B68D71B6CC693AA9
> 2007-09-25 11:04:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 144
> 2007-09-25 11:04:01 - + [163] 1 operations applied (0 remaining)
This link might be helpful.
http://support.microsoft.com/kb/295378
Regards,
Enrique Martinez
Sr. Software Consultant

Microsft Fix for wrong SP

Hi!
Tried to cure a problem described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;328551&Product=sql
The article says that
quote:
----
Hotfix 8.00.0702
A supported fix is now available from Microsoft, but it is only
intended to correct the problem described in this article. Only apply
it to systems that are experiencing this specific problem. This fix
may receive additional testing to further ensure product quality.
Therefore, if you are not severely affected by this problem, Microsoft
recommends that you wait for the next Microsoft SQL Server 2000
service pack (sp4) that contains this fix.
----
So I should be able to apply this fix for MS SQL2000 SP3. I could not
do it: It says that I have wrong service pack or version... Why?
Thanks."Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0311120254.3a5323ad@.posting.google.com...
> Tried to cure a problem described here:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;328551&Product=sql
> The article says that
> quote:
> ----
--
> Hotfix 8.00.0702
> A supported fix is now available from Microsoft, but it is only
> intended to correct the problem described in this article. Only apply
> it to systems that are experiencing this specific problem. This fix
> may receive additional testing to further ensure product quality.
> Therefore, if you are not severely affected by this problem, Microsoft
> recommends that you wait for the next Microsoft SQL Server 2000
> service pack (sp4) that contains this fix.
> ----
--
> So I should be able to apply this fix for MS SQL2000 SP3. I could not
> do it: It says that I have wrong service pack or version... Why?
It's possible you need to apply the latest service pack which is SQL Server
2000 SP3a , then apply the hotfix.
Steve|||This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build of
760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
hotfix build 765 to get the fix for SP3.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||- So, what SP matches this service pack, 1st or 2nd?
(I could not install it on MS SQL2000 w/o SP too)
rboyd@.onlinemicrosoft.com (Rand Boyd [MS]) wrote in message news:<uOuMCDYqDHA.1548@.cpmsftngxa06.phx.gbl>...
> This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build of
> 760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
> hotfix build 765 to get the fix for SP3.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.|||"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0311140139.49eb3fc0@.posting.google.com...
> - So, what SP matches this service pack, 1st or 2nd?
> (I could not install it on MS SQL2000 w/o SP too)
If you mean which service patch would match that hotfix -- the hotfix should
work on a post SP2 SQL installation.
For version information
http://support.microsoft.com/default.aspx?scid=kb;en-us;321185&Product=sql
I'd recommend getting the post sp3 hotfix and installing SQL Server SP3a.
Steve
> rboyd@.onlinemicrosoft.com (Rand Boyd [MS]) wrote in message
news:<uOuMCDYqDHA.1548@.cpmsftngxa06.phx.gbl>...
> > This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build
of
> > 760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
> > hotfix build 765 to get the fix for SP3.
> >
> > Rand
> > This posting is provided "as is" with no warranties and confers no
rights.|||You need to contact Microsoft and get the post-SP3 hotfix.
Rand
This posting is provided "as is" with no warranties and confers no rights.