Intermitent problem : New transaction cannot enlist in the specified transaction coordinat

I have a Windows 2003 Application Server. When I dont use the
Application for about 15 minutes, I get the error : "New transaction
cannot enlist in the specified transaction coordinator" when trying to
do a transaction with the Database server.
When I got the error, if I keep trying to do a transaction, eventually
the transaction process restart to work until I keep it inactive for
about 15 minutes.
I did some test with the application and with DTCTester. When it dont
work with the application it dont work with DTCTester
(http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
- The application server is Windows 2003 SP1
- This server connect to a Cluster SQL Server 2000 database intalled on
Windows 2003 servers .
- The two servers are in two differents Network zone.
- All ports are opened between Database servers and application
servers.
- MSDTC is started on the Application and Database server.
- In security configuration of MSDTC of the Application server the
option "No Authentication Required is selected". This option is not
selected on the Database server because the service pack 1 is not
installed.
- Database computers names are in the host file of the application
server and application server name is in the host file of the SQL
Server.
I did some test with another Database server (SQL Server 2000 on
windows 2000) and it always works, but these two server are in the same
zone.
I would like to know if someone have an idea why the transaction stop
to works after about 15 minutes and restart to work if I keep trying.
Thank you very much.
DavidHi Dave
I am not sure what you mean by different zones? Is this a different sub-net?
It is not clear if you are seeing exactly the same symptoms with DTC tester
or if it never works?
As the problem is intermittent it sounds like a network type issue rather
than the components. You may want to try changing network cards and
hubs/switches to see if it continues to fail. Also if there are any firewalls
make sure they are configured correctly, also make sure that no antivirus or
intrusion detection software is causing a conflict.
John
"Dave960" wrote:
> I have a Windows 2003 Application Server. When I dont use the
> Application for about 15 minutes, I get the error : "New transaction
> cannot enlist in the specified transaction coordinator" when trying to
> do a transaction with the Database server.
> When I got the error, if I keep trying to do a transaction, eventually
> the transaction process restart to work until I keep it inactive for
> about 15 minutes.
> I did some test with the application and with DTCTester. When it dont
> work with the application it dont work with DTCTester
> (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> - The application server is Windows 2003 SP1
> - This server connect to a Cluster SQL Server 2000 database intalled on
> Windows 2003 servers .
> - The two servers are in two differents Network zone.
> - All ports are opened between Database servers and application
> servers.
> - MSDTC is started on the Application and Database server.
> - In security configuration of MSDTC of the Application server the
> option "No Authentication Required is selected". This option is not
> selected on the Database server because the service pack 1 is not
> installed.
> - Database computers names are in the host file of the application
> server and application server name is in the host file of the SQL
> Server.
>
> I did some test with another Database server (SQL Server 2000 on
> windows 2000) and it always works, but these two server are in the same
> zone.
> I would like to know if someone have an idea why the transaction stop
> to works after about 15 minutes and restart to work if I keep trying.
> Thank you very much.
> David
>|||Hi John,
Thank's for your reply :)
- By different zone I mean different sub-net.
- I'm seeing exactly the same problem with dtctester. After a couple of
try it work's and if I do nothing for about 15 minutes it stop to work
until I try dtctester for a couple of try ( 2 to 20).
If I run a transaction between the application server and the SQL
server every 5-10 minutes, transaction always work.
The transaction process always work with another Database server
(Server2) in the same zone as my application server, so I think it's
not hardware related. But there is difference with this second server,
it run on windows 2000 and is not in a cluster.
If I do the dtctester test with the Database server (Server1 - the one
that I have problem with) with another application server in the Dabase
server sub-net it always works.
Another thing, I'm always able to retrieve data from the Database
server, I just have problem with transactions.
>From what I see it look like a network problem, but I dont see why
after about 15 minutes of inactivity it strop to work ?
If you have any ideas, let me know.
Thanks a lot.
David
It look similar to this problem :
http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
John Bell wrote:
> Hi Dave
> I am not sure what you mean by different zones? Is this a different sub-net?
> It is not clear if you are seeing exactly the same symptoms with DTC tester
> or if it never works?
> As the problem is intermittent it sounds like a network type issue rather
> than the components. You may want to try changing network cards and
> hubs/switches to see if it continues to fail. Also if there are any firewalls
> make sure they are configured correctly, also make sure that no antivirus or
> intrusion detection software is causing a conflict.
> John
>
> "Dave960" wrote:
> > I have a Windows 2003 Application Server. When I dont use the
> > Application for about 15 minutes, I get the error : "New transaction
> > cannot enlist in the specified transaction coordinator" when trying to
> > do a transaction with the Database server.
> >
> > When I got the error, if I keep trying to do a transaction, eventually
> > the transaction process restart to work until I keep it inactive for
> > about 15 minutes.
> >
> > I did some test with the application and with DTCTester. When it dont
> > work with the application it dont work with DTCTester
> > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> >
> > - The application server is Windows 2003 SP1
> >
> > - This server connect to a Cluster SQL Server 2000 database intalled on
> > Windows 2003 servers .
> >
> > - The two servers are in two differents Network zone.
> >
> > - All ports are opened between Database servers and application
> > servers.
> >
> > - MSDTC is started on the Application and Database server.
> >
> > - In security configuration of MSDTC of the Application server the
> > option "No Authentication Required is selected". This option is not
> > selected on the Database server because the service pack 1 is not
> > installed.
> >
> > - Database computers names are in the host file of the application
> > server and application server name is in the host file of the SQL
> > Server.
> >
> >
> >
> > I did some test with another Database server (SQL Server 2000 on
> > windows 2000) and it always works, but these two server are in the same
> > zone.
> >
> > I would like to know if someone have an idea why the transaction stop
> > to works after about 15 minutes and restart to work if I keep trying.
> >
> > Thank you very much.
> >
> > David
> >
> >|||Hi Dave
It is not clear why you need a distributed transaction, from what you say it
is only
the one server being used at any one time?
John
"Dave960" wrote:
> Hi John,
> Thank's for your reply :)
> - By different zone I mean different sub-net.
> - I'm seeing exactly the same problem with dtctester. After a couple of
> try it work's and if I do nothing for about 15 minutes it stop to work
> until I try dtctester for a couple of try ( 2 to 20).
> If I run a transaction between the application server and the SQL
> server every 5-10 minutes, transaction always work.
> The transaction process always work with another Database server
> (Server2) in the same zone as my application server, so I think it's
> not hardware related. But there is difference with this second server,
> it run on windows 2000 and is not in a cluster.
> If I do the dtctester test with the Database server (Server1 - the one
> that I have problem with) with another application server in the Dabase
> server sub-net it always works.
> Another thing, I'm always able to retrieve data from the Database
> server, I just have problem with transactions.
> >From what I see it look like a network problem, but I dont see why
> after about 15 minutes of inactivity it strop to work ?
> If you have any ideas, let me know.
> Thanks a lot.
> David
>
> It look similar to this problem :
> http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> John Bell wrote:
> > Hi Dave
> >
> > I am not sure what you mean by different zones? Is this a different sub-net?
> > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > or if it never works?
> >
> > As the problem is intermittent it sounds like a network type issue rather
> > than the components. You may want to try changing network cards and
> > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > make sure they are configured correctly, also make sure that no antivirus or
> > intrusion detection software is causing a conflict.
> >
> > John
> >
> >
> > "Dave960" wrote:
> >
> > > I have a Windows 2003 Application Server. When I dont use the
> > > Application for about 15 minutes, I get the error : "New transaction
> > > cannot enlist in the specified transaction coordinator" when trying to
> > > do a transaction with the Database server.
> > >
> > > When I got the error, if I keep trying to do a transaction, eventually
> > > the transaction process restart to work until I keep it inactive for
> > > about 15 minutes.
> > >
> > > I did some test with the application and with DTCTester. When it dont
> > > work with the application it dont work with DTCTester
> > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > >
> > > - The application server is Windows 2003 SP1
> > >
> > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > Windows 2003 servers .
> > >
> > > - The two servers are in two differents Network zone.
> > >
> > > - All ports are opened between Database servers and application
> > > servers.
> > >
> > > - MSDTC is started on the Application and Database server.
> > >
> > > - In security configuration of MSDTC of the Application server the
> > > option "No Authentication Required is selected". This option is not
> > > selected on the Database server because the service pack 1 is not
> > > installed.
> > >
> > > - Database computers names are in the host file of the application
> > > server and application server name is in the host file of the SQL
> > > Server.
> > >
> > >
> > >
> > > I did some test with another Database server (SQL Server 2000 on
> > > windows 2000) and it always works, but these two server are in the same
> > > zone.
> > >
> > > I would like to know if someone have an idea why the transaction stop
> > > to works after about 15 minutes and restart to work if I keep trying.
> > >
> > > Thank you very much.
> > >
> > > David
> > >
> > >
>|||Hi John,
The application server run COM+ components that use distributed
transaction for certain type of query to the database.
This application is already running on another server, we just want to
switch this application to a new server that is in a different sub-net.
If there's missing informations, dont hesitate to ask me.
Thanks !!!
David
John Bell wrote:
> Hi Dave
> It is not clear why you need a distributed transaction, from what you say it
> is only
> the one server being used at any one time?
> John
>
> "Dave960" wrote:
> > Hi John,
> >
> > Thank's for your reply :)
> >
> > - By different zone I mean different sub-net.
> > - I'm seeing exactly the same problem with dtctester. After a couple of
> > try it work's and if I do nothing for about 15 minutes it stop to work
> > until I try dtctester for a couple of try ( 2 to 20).
> >
> > If I run a transaction between the application server and the SQL
> > server every 5-10 minutes, transaction always work.
> >
> > The transaction process always work with another Database server
> > (Server2) in the same zone as my application server, so I think it's
> > not hardware related. But there is difference with this second server,
> > it run on windows 2000 and is not in a cluster.
> >
> > If I do the dtctester test with the Database server (Server1 - the one
> > that I have problem with) with another application server in the Dabase
> > server sub-net it always works.
> >
> > Another thing, I'm always able to retrieve data from the Database
> > server, I just have problem with transactions.
> >
> > >From what I see it look like a network problem, but I dont see why
> > after about 15 minutes of inactivity it strop to work ?
> >
> > If you have any ideas, let me know.
> >
> > Thanks a lot.
> >
> > David
> >
> >
> > It look similar to this problem :
> > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> >
> > John Bell wrote:
> > > Hi Dave
> > >
> > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > or if it never works?
> > >
> > > As the problem is intermittent it sounds like a network type issue rather
> > > than the components. You may want to try changing network cards and
> > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > make sure they are configured correctly, also make sure that no antivirus or
> > > intrusion detection software is causing a conflict.
> > >
> > > John
> > >
> > >
> > > "Dave960" wrote:
> > >
> > > > I have a Windows 2003 Application Server. When I dont use the
> > > > Application for about 15 minutes, I get the error : "New transaction
> > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > do a transaction with the Database server.
> > > >
> > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > the transaction process restart to work until I keep it inactive for
> > > > about 15 minutes.
> > > >
> > > > I did some test with the application and with DTCTester. When it dont
> > > > work with the application it dont work with DTCTester
> > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > >
> > > > - The application server is Windows 2003 SP1
> > > >
> > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > Windows 2003 servers .
> > > >
> > > > - The two servers are in two differents Network zone.
> > > >
> > > > - All ports are opened between Database servers and application
> > > > servers.
> > > >
> > > > - MSDTC is started on the Application and Database server.
> > > >
> > > > - In security configuration of MSDTC of the Application server the
> > > > option "No Authentication Required is selected". This option is not
> > > > selected on the Database server because the service pack 1 is not
> > > > installed.
> > > >
> > > > - Database computers names are in the host file of the application
> > > > server and application server name is in the host file of the SQL
> > > > Server.
> > > >
> > > >
> > > >
> > > > I did some test with another Database server (SQL Server 2000 on
> > > > windows 2000) and it always works, but these two server are in the same
> > > > zone.
> > > >
> > > > I would like to know if someone have an idea why the transaction stop
> > > > to works after about 15 minutes and restart to work if I keep trying.
> > > >
> > > > Thank you very much.
> > > >
> > > > David
> > > >
> > > >
> >
> >|||Hi Dave
As this is intermitten, it implies that it is set up correctly and something
other than SQL Server is causing this to fail. Have you checked for intrusion
detection or virus checkers being active at this time?
John
"Dave960" wrote:
> Hi John,
> The application server run COM+ components that use distributed
> transaction for certain type of query to the database.
> This application is already running on another server, we just want to
> switch this application to a new server that is in a different sub-net.
> If there's missing informations, dont hesitate to ask me.
> Thanks !!!
> David
>
> John Bell wrote:
> > Hi Dave
> >
> > It is not clear why you need a distributed transaction, from what you say it
> > is only
> > the one server being used at any one time?
> >
> > John
> >
> >
> >
> > "Dave960" wrote:
> >
> > > Hi John,
> > >
> > > Thank's for your reply :)
> > >
> > > - By different zone I mean different sub-net.
> > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > until I try dtctester for a couple of try ( 2 to 20).
> > >
> > > If I run a transaction between the application server and the SQL
> > > server every 5-10 minutes, transaction always work.
> > >
> > > The transaction process always work with another Database server
> > > (Server2) in the same zone as my application server, so I think it's
> > > not hardware related. But there is difference with this second server,
> > > it run on windows 2000 and is not in a cluster.
> > >
> > > If I do the dtctester test with the Database server (Server1 - the one
> > > that I have problem with) with another application server in the Dabase
> > > server sub-net it always works.
> > >
> > > Another thing, I'm always able to retrieve data from the Database
> > > server, I just have problem with transactions.
> > >
> > > >From what I see it look like a network problem, but I dont see why
> > > after about 15 minutes of inactivity it strop to work ?
> > >
> > > If you have any ideas, let me know.
> > >
> > > Thanks a lot.
> > >
> > > David
> > >
> > >
> > > It look similar to this problem :
> > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > >
> > > John Bell wrote:
> > > > Hi Dave
> > > >
> > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > or if it never works?
> > > >
> > > > As the problem is intermittent it sounds like a network type issue rather
> > > > than the components. You may want to try changing network cards and
> > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > intrusion detection software is causing a conflict.
> > > >
> > > > John
> > > >
> > > >
> > > > "Dave960" wrote:
> > > >
> > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > do a transaction with the Database server.
> > > > >
> > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > the transaction process restart to work until I keep it inactive for
> > > > > about 15 minutes.
> > > > >
> > > > > I did some test with the application and with DTCTester. When it dont
> > > > > work with the application it dont work with DTCTester
> > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > >
> > > > > - The application server is Windows 2003 SP1
> > > > >
> > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > Windows 2003 servers .
> > > > >
> > > > > - The two servers are in two differents Network zone.
> > > > >
> > > > > - All ports are opened between Database servers and application
> > > > > servers.
> > > > >
> > > > > - MSDTC is started on the Application and Database server.
> > > > >
> > > > > - In security configuration of MSDTC of the Application server the
> > > > > option "No Authentication Required is selected". This option is not
> > > > > selected on the Database server because the service pack 1 is not
> > > > > installed.
> > > > >
> > > > > - Database computers names are in the host file of the application
> > > > > server and application server name is in the host file of the SQL
> > > > > Server.
> > > > >
> > > > >
> > > > >
> > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > windows 2000) and it always works, but these two server are in the same
> > > > > zone.
> > > > >
> > > > > I would like to know if someone have an idea why the transaction stop
> > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > >
> > > > > Thank you very much.
> > > > >
> > > > > David
> > > > >
> > > > >
> > >
> > >
>|||Hi Dave
You may also want to check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306843
John
"Dave960" wrote:
> Hi John,
> The application server run COM+ components that use distributed
> transaction for certain type of query to the database.
> This application is already running on another server, we just want to
> switch this application to a new server that is in a different sub-net.
> If there's missing informations, dont hesitate to ask me.
> Thanks !!!
> David
>
> John Bell wrote:
> > Hi Dave
> >
> > It is not clear why you need a distributed transaction, from what you say it
> > is only
> > the one server being used at any one time?
> >
> > John
> >
> >
> >
> > "Dave960" wrote:
> >
> > > Hi John,
> > >
> > > Thank's for your reply :)
> > >
> > > - By different zone I mean different sub-net.
> > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > until I try dtctester for a couple of try ( 2 to 20).
> > >
> > > If I run a transaction between the application server and the SQL
> > > server every 5-10 minutes, transaction always work.
> > >
> > > The transaction process always work with another Database server
> > > (Server2) in the same zone as my application server, so I think it's
> > > not hardware related. But there is difference with this second server,
> > > it run on windows 2000 and is not in a cluster.
> > >
> > > If I do the dtctester test with the Database server (Server1 - the one
> > > that I have problem with) with another application server in the Dabase
> > > server sub-net it always works.
> > >
> > > Another thing, I'm always able to retrieve data from the Database
> > > server, I just have problem with transactions.
> > >
> > > >From what I see it look like a network problem, but I dont see why
> > > after about 15 minutes of inactivity it strop to work ?
> > >
> > > If you have any ideas, let me know.
> > >
> > > Thanks a lot.
> > >
> > > David
> > >
> > >
> > > It look similar to this problem :
> > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > >
> > > John Bell wrote:
> > > > Hi Dave
> > > >
> > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > or if it never works?
> > > >
> > > > As the problem is intermittent it sounds like a network type issue rather
> > > > than the components. You may want to try changing network cards and
> > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > intrusion detection software is causing a conflict.
> > > >
> > > > John
> > > >
> > > >
> > > > "Dave960" wrote:
> > > >
> > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > do a transaction with the Database server.
> > > > >
> > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > the transaction process restart to work until I keep it inactive for
> > > > > about 15 minutes.
> > > > >
> > > > > I did some test with the application and with DTCTester. When it dont
> > > > > work with the application it dont work with DTCTester
> > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > >
> > > > > - The application server is Windows 2003 SP1
> > > > >
> > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > Windows 2003 servers .
> > > > >
> > > > > - The two servers are in two differents Network zone.
> > > > >
> > > > > - All ports are opened between Database servers and application
> > > > > servers.
> > > > >
> > > > > - MSDTC is started on the Application and Database server.
> > > > >
> > > > > - In security configuration of MSDTC of the Application server the
> > > > > option "No Authentication Required is selected". This option is not
> > > > > selected on the Database server because the service pack 1 is not
> > > > > installed.
> > > > >
> > > > > - Database computers names are in the host file of the application
> > > > > server and application server name is in the host file of the SQL
> > > > > Server.
> > > > >
> > > > >
> > > > >
> > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > windows 2000) and it always works, but these two server are in the same
> > > > > zone.
> > > > >
> > > > > I would like to know if someone have an idea why the transaction stop
> > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > >
> > > > > Thank you very much.
> > > > >
> > > > > David
> > > > >
> > > > >
> > >
> > >
>|||Hi John,
- I have the same problem if I desactivate the Antivirus sofware.
- I already follow the steps list in this link and DTCPing always
works.
If you have any other ideas, let me know.
Thanks
David
John Bell wrote:
> Hi Dave
> You may also want to check out
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306843
> John
> "Dave960" wrote:
> > Hi John,
> >
> > The application server run COM+ components that use distributed
> > transaction for certain type of query to the database.
> >
> > This application is already running on another server, we just want to
> > switch this application to a new server that is in a different sub-net.
> >
> > If there's missing informations, dont hesitate to ask me.
> >
> > Thanks !!!
> >
> > David
> >
> >
> > John Bell wrote:
> > > Hi Dave
> > >
> > > It is not clear why you need a distributed transaction, from what you say it
> > > is only
> > > the one server being used at any one time?
> > >
> > > John
> > >
> > >
> > >
> > > "Dave960" wrote:
> > >
> > > > Hi John,
> > > >
> > > > Thank's for your reply :)
> > > >
> > > > - By different zone I mean different sub-net.
> > > > - I'm seeing exactly the same problem with dtctester. After a couple of
> > > > try it work's and if I do nothing for about 15 minutes it stop to work
> > > > until I try dtctester for a couple of try ( 2 to 20).
> > > >
> > > > If I run a transaction between the application server and the SQL
> > > > server every 5-10 minutes, transaction always work.
> > > >
> > > > The transaction process always work with another Database server
> > > > (Server2) in the same zone as my application server, so I think it's
> > > > not hardware related. But there is difference with this second server,
> > > > it run on windows 2000 and is not in a cluster.
> > > >
> > > > If I do the dtctester test with the Database server (Server1 - the one
> > > > that I have problem with) with another application server in the Dabase
> > > > server sub-net it always works.
> > > >
> > > > Another thing, I'm always able to retrieve data from the Database
> > > > server, I just have problem with transactions.
> > > >
> > > > >From what I see it look like a network problem, but I dont see why
> > > > after about 15 minutes of inactivity it strop to work ?
> > > >
> > > > If you have any ideas, let me know.
> > > >
> > > > Thanks a lot.
> > > >
> > > > David
> > > >
> > > >
> > > > It look similar to this problem :
> > > > http://groups.google.ca/group/microsoft.public.platformsdk.complus_mts/browse_thread/thread/da9b915896c6d8a1/66b4518597052cfb?lnk=st&q=&rnum=1&hl=en#66b4518597052cfb
> > > >
> > > > John Bell wrote:
> > > > > Hi Dave
> > > > >
> > > > > I am not sure what you mean by different zones? Is this a different sub-net?
> > > > > It is not clear if you are seeing exactly the same symptoms with DTC tester
> > > > > or if it never works?
> > > > >
> > > > > As the problem is intermittent it sounds like a network type issue rather
> > > > > than the components. You may want to try changing network cards and
> > > > > hubs/switches to see if it continues to fail. Also if there are any firewalls
> > > > > make sure they are configured correctly, also make sure that no antivirus or
> > > > > intrusion detection software is causing a conflict.
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > > "Dave960" wrote:
> > > > >
> > > > > > I have a Windows 2003 Application Server. When I dont use the
> > > > > > Application for about 15 minutes, I get the error : "New transaction
> > > > > > cannot enlist in the specified transaction coordinator" when trying to
> > > > > > do a transaction with the Database server.
> > > > > >
> > > > > > When I got the error, if I keep trying to do a transaction, eventually
> > > > > > the transaction process restart to work until I keep it inactive for
> > > > > > about 15 minutes.
> > > > > >
> > > > > > I did some test with the application and with DTCTester. When it dont
> > > > > > work with the application it dont work with DTCTester
> > > > > > (http://support.microsoft.com/default.aspx?scid=kb;en-us;293799).
> > > > > >
> > > > > > - The application server is Windows 2003 SP1
> > > > > >
> > > > > > - This server connect to a Cluster SQL Server 2000 database intalled on
> > > > > > Windows 2003 servers .
> > > > > >
> > > > > > - The two servers are in two differents Network zone.
> > > > > >
> > > > > > - All ports are opened between Database servers and application
> > > > > > servers.
> > > > > >
> > > > > > - MSDTC is started on the Application and Database server.
> > > > > >
> > > > > > - In security configuration of MSDTC of the Application server the
> > > > > > option "No Authentication Required is selected". This option is not
> > > > > > selected on the Database server because the service pack 1 is not
> > > > > > installed.
> > > > > >
> > > > > > - Database computers names are in the host file of the application
> > > > > > server and application server name is in the host file of the SQL
> > > > > > Server.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I did some test with another Database server (SQL Server 2000 on
> > > > > > windows 2000) and it always works, but these two server are in the same
> > > > > > zone.
> > > > > >
> > > > > > I would like to know if someone have an idea why the transaction stop
> > > > > > to works after about 15 minutes and restart to work if I keep trying.
> > > > > >
> > > > > > Thank you very much.
> > > > > >
> > > > > > David
> > > > > >
> > > > > >
> > > >
> > > >
> >
> >

intermitent connection problem asp to sql2000

I have an asp page (w2003 IIS) which grabs a very small amount of data from
a table on our
sql server (sql2000).
Most of the time the page works fine, with no problems. However
intermitently it falls over with:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
/MIS/Searches/main_search.asp, line 8
this is the connection and query which brings back about 300 records:
Dim MM_uLiveDatabase_STRING
MM_uLiveDatabase_STRING = "dsn=database;uid=username;pwd=password
Dim getID
Dim getID_numRows
Set getID = Server.CreateObject("ADODB.Recordset")
getID.ActiveConnection = MM_uLiveDatabase_STRING
getID.Source = "select fltf_value from caps_users left join
caps_user_filters on uflt_for_user = user_id inner join caps_filter_fields
on fltf_filter_flt = uflt_filter_flt where user_ref like '" +
Replace(getID__theUser, "'", "''") + "'"
getID.CursorType = 0
getID.CursorLocation = 2
getID.LockType = 1
getID.Open()
THis is rapidly becoming a major problem! Anyone got any ideas?
john
You'd want to start by monitoring for locking, blocking
issues in SQL Server when you experience the timeouts. You
can monitor for these issues using sp_who2, sp_lock and
querying master..sysprocesses.
-Sue
On Tue, 1 Feb 2005 17:43:41 -0000, "John" <john@.home.com.uk>
wrote:

>I have an asp page (w2003 IIS) which grabs a very small amount of data from
>a table on our
>sql server (sql2000).
>Most of the time the page works fine, with no problems. However
>intermitently it falls over with:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC SQL Server Driver]Timeout expired
>/MIS/Searches/main_search.asp, line 8
>
>this is the connection and query which brings back about 300 records:
>Dim MM_uLiveDatabase_STRING
>MM_uLiveDatabase_STRING = "dsn=database;uid=username;pwd=password
>Dim getID
>Dim getID_numRows
>Set getID = Server.CreateObject("ADODB.Recordset")
>getID.ActiveConnection = MM_uLiveDatabase_STRING
>getID.Source = "select fltf_value from caps_users left join
>caps_user_filters on uflt_for_user = user_id inner join caps_filter_fields
>on fltf_filter_flt = uflt_filter_flt where user_ref like '" +
>Replace(getID__theUser, "'", "''") + "'"
>getID.CursorType = 0
>getID.CursorLocation = 2
>getID.LockType = 1
>getID.Open()
>
>THis is rapidly becoming a major problem! Anyone got any ideas?
>john
>

intermitent connection problem asp to sql2000

I have an asp page (w2003 IIS) which grabs a very small amount of data from
a table on our
sql server (sql2000).
Most of the time the page works fine, with no problems. However
intermitently it falls over with:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
/MIS/Searches/main_search.asp, line 8
this is the connection and query which brings back about 300 records:
Dim MM_uLiveDatabase_STRING
MM_uLiveDatabase_STRING = "dsn=database;uid=username;pwd=password
Dim getID
Dim getID_numRows
Set getID = Server.CreateObject("ADODB.Recordset")
getID.ActiveConnection = MM_uLiveDatabase_STRING
getID.Source = "select fltf_value from caps_users left join
caps_user_filters on uflt_for_user = user_id inner join caps_filter_fields
on fltf_filter_flt = uflt_filter_flt where user_ref like '" +
Replace(getID__theUser, "'", "''") + "'"
getID.CursorType = 0
getID.CursorLocation = 2
getID.LockType = 1
getID.Open()
THis is rapidly becoming a major problem! Anyone got any ideas'
johnYou'd want to start by monitoring for locking, blocking
issues in SQL Server when you experience the timeouts. You
can monitor for these issues using sp_who2, sp_lock and
querying master..sysprocesses.
-Sue
On Tue, 1 Feb 2005 17:43:41 -0000, "John" <john@.home.com.uk>
wrote:

>I have an asp page (w2003 IIS) which grabs a very small amount of data from
>a table on our
>sql server (sql2000).
>Most of the time the page works fine, with no problems. However
>intermitently it falls over with:
>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC SQL Server Driver]Timeout expired
>/MIS/Searches/main_search.asp, line 8
>
>this is the connection and query which brings back about 300 records:
>Dim MM_uLiveDatabase_STRING
>MM_uLiveDatabase_STRING = "dsn=database;uid=username;pwd=password
>Dim getID
>Dim getID_numRows
>Set getID = Server.CreateObject("ADODB.Recordset")
>getID.ActiveConnection = MM_uLiveDatabase_STRING
>getID.Source = "select fltf_value from caps_users left join
>caps_user_filters on uflt_for_user = user_id inner join caps_filter_fields
>on fltf_filter_flt = uflt_filter_flt where user_ref like '" +
>Replace(getID__theUser, "'", "''") + "'"
>getID.CursorType = 0
>getID.CursorLocation = 2
>getID.LockType = 1
>getID.Open()
>
>THis is rapidly becoming a major problem! Anyone got any ideas'
>john
>

intermitent connection failure

We have written a thread to monitor whether the database connection is still
alive or not.
This monitoring thread executes a stored procedure, sp_TestDB, with ADO
_CommandPtr every 3 seconds.
Most of the time we have no problems executing it. However, we receive the
following error randomly:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(WrapperWrite()). Msg:Unspecified error
We are convinced that the machine where the database server is installed is
definitely alive as we ping it all the time and there is no request time out
.
We want to know what other problems could cause this error to happen randoml
y?
The development language we use is Visual C++.
The database server we use is :
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
ScottHi Scott,
Since this is an unspecified error on the client side, In this case, please
try to use SQL profiler to start a trace to see what is actually happening
on the server. The trace log might show more information on this error.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."|||Excuse me, but I have the same problem, could you tell me how can I fix ?
I will appreciate it.
Thanks
Bruno Martinez
MCDBA
BMartinez@.cosapisoft.com.pe
"scottrm" <scottrm@.newsgroup.nospam> escribi en el mensaje
news:AD41E055-5B53-4015-B73E-88086A949CE4@.microsoft.com...
> We have written a thread to monitor whether the database connection is
> still
> alive or not.
> This monitoring thread executes a stored procedure, sp_TestDB, with ADO
> _CommandPtr every 3 seconds.
> Most of the time we have no problems executing it. However, we receive the
> following error randomly:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
> (WrapperWrite()). Msg:Unspecified error
> We are convinced that the machine where the database server is installed
> is
> definitely alive as we ping it all the time and there is no request time
> out.
> We want to know what other problems could cause this error to happen
> randomly?
> The development language we use is Visual C++.
> The database server we use is :
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>
>
> --
> Scott

intermitent connection failure

We have written a thread to monitor whether the database connection is still
alive or not.
This monitoring thread executes a stored procedure, sp_TestDB, with ADO
_CommandPtr every 3 seconds.
Most of the time we have no problems executing it. However, we receive the
following error randomly:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
(WrapperWrite()). Msg:Unspecified error
We are convinced that the machine where the database server is installed is
definitely alive as we ping it all the time and there is no request time out.
We want to know what other problems could cause this error to happen randomly?
The development language we use is Visual C++.
The database server we use is :
Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Scott
Hi Scott,
Since this is an unspecified error on the client side, In this case, please
try to use SQL profiler to start a trace to see what is actually happening
on the server. The trace log might show more information on this error.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
|||Excuse me, but I have the same problem, could you tell me how can I fix ?
I will appreciate it.
Thanks
Bruno Martinez
MCDBA
BMartinez@.cosapisoft.com.pe
"scottrm" <scottrm@.newsgroup.nospam> escribi en el mensaje
news:AD41E055-5B53-4015-B73E-88086A949CE4@.microsoft.com...
> We have written a thread to monitor whether the database connection is
> still
> alive or not.
> This monitoring thread executes a stored procedure, sp_TestDB, with ADO
> _CommandPtr every 3 seconds.
> Most of the time we have no problems executing it. However, we receive the
> following error randomly:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite
> (WrapperWrite()). Msg:Unspecified error
> We are convinced that the machine where the database server is installed
> is
> definitely alive as we ping it all the time and there is no request time
> out.
> We want to know what other problems could cause this error to happen
> randomly?
> The development language we use is Visual C++.
> The database server we use is :
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
>
>
> --
> Scott
sql