Commerce Server General - Could not connect to datasource error in payment.asp

Author

Could not connect to datasource error in payment.asp

Kiran Kakanur

2005-05-06, 5:57 pm

Hi,

We are running MSCS 2000 + SP1 on Windows 2000 Advanced Server. And we are
running SQL Server 2000 Std Ed + SP3. We recently moved the SQL db to another
server. And we did have our share of connection string related issues after
the DB move. I believe that we have updated all areas in Commerce Server
Manager to reflect the new database server. And the fact that the site has
been running smoothly after the DB move proves that.

But lately we are seeing this rather sporadic error during customer
checkout. The error message that we get is:

Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
Could not connect to datasource
/<sitename>/include/payment.asp, line 248

And line 248 is in a function called, SaveBasketAsOrder(...), in payment.asp
as shown below:

Sub SaveBasketAsOrder(mscsOrderGrp)
Dim mscsOrderGrpMgr

' Remove any addresses from the orderform which are not referenced
Call mscsOrderGrp.PurgeUnreferencedAddresses()

Call mscsOrderGrp.SaveAsOrder() ' This is line 248

' Submit appropriate OrderForms using BizTalk
Call InvokeBizTalk(mscsOrderGrp)

Set mscsOrderGrpMgr = GetOrderGroupManager()
Call mscsOrderGrpMgr.DeleteOrderGroupFromDisk(m_UserID)

'// Call update of gift registy items
Call UpdateGiftRegistryCounts(mscsOrderGrp)

Call Analysis_LogSubmitOrder(mscsOrderGrp.Value(ORDERGROUP_ID)) 'Do this
last, as it can't be rolled back

End Sub

The payment.asp has not been modified at all.

Any thoughts what might be causing this and what can be done to eliminate it?

Thanks a lot.

Best regards,
Kiran Kakanur
The Revere Group
http://www.reveregroup.com

Vinod Kumar[MSFT]

2005-05-09, 5:50 pm

This seems like a connection string issue. You should go and check the Transaction resource connection string. and Transaction Resource connection string. If this connection strings are fine then other place to
look for would be DTC. Try using the DTC ping tool to see if the DTC is working properly.

Thanks
-Vinod

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
--------------------
Thread-Topic: Could not connect to datasource error in payment.asp
thread-index: AcVSilNopJKMcdqER9G+xOEMI4u8gQ==
X-WBNR-Posting-Host: 68.22.186.186
From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <Kiran Kakanur@discussions.microsoft.com>
Subject: Could not connect to datasource error in payment.asp
Date: Fri, 6 May 2005 15:24:10 -0700
Lines: 58
Message-ID: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2714
X-Tomcat-NG: microsoft.public.commerceserver.general

Hi,

We are running MSCS 2000 + SP1 on Windows 2000 Advanced Server. And we are
running SQL Server 2000 Std Ed + SP3. We recently moved the SQL db to another
server. And we did have our share of connection string related issues after
the DB move. I believe that we have updated all areas in Commerce Server
Manager to reflect the new database server. And the fact that the site has
been running smoothly after the DB move proves that.

But lately we are seeing this rather sporadic error during customer
checkout. The error message that we get is:

Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
Could not connect to datasource
/<sitename>/include/payment.asp, line 248

And line 248 is in a function called, SaveBasketAsOrder(...), in payment.asp
as shown below:

Sub SaveBasketAsOrder(mscsOrderGrp)
Dim mscsOrderGrpMgr

' Remove any addresses from the orderform which are not referenced
Call mscsOrderGrp.PurgeUnreferencedAddresses()

Call mscsOrderGrp.SaveAsOrder() ' This is line 248

' Submit appropriate OrderForms using BizTalk
Call InvokeBizTalk(mscsOrderGrp)

Set mscsOrderGrpMgr = GetOrderGroupManager()
Call mscsOrderGrpMgr.DeleteOrderGroupFromDisk(m_UserID)

'// Call update of gift registy items
Call UpdateGiftRegistryCounts(mscsOrderGrp)

Call Analysis_LogSubmitOrder(mscsOrderGrp.Value(ORDERGROUP_ID)) 'Do this
last, as it can't be rolled back

End Sub

The payment.asp has not been modified at all.

Any thoughts what might be causing this and what can be done to eliminate it?

Thanks a lot.

Best regards,
Kiran Kakanur
The Revere Group
http://www.reveregroup.com

Kiran Kakanur

2005-05-10, 5:55 pm

Hi Vinod,

Thanks so much for your prompt and useful response.

One thing I wanted to make sure that I understood correctly...You meant the
connection strings in "Transactions" and "Transactions Config" under
"Commerce Sites >> <sitename> >> Site Resources" in Commerce Server Manager,
right?

These connection strings are pointing to the correct database server, and to
the correct database. I also tested the connection to the db and it was
successful.

I also downloaded DTCPing.exe from a link that I found at the following KB
article:

http://support.microsoft.com/defaul...kb;en-us;306843

I installed DTCping.exe on all 3 web servers and the 1 database server. And
performed the tests on the servers. Specifically, I tested to see if each web
server can successfully communicate with the database server.

I got one failure in the DTCPing logs when one of the 3 web servers was
attempting to "Reverse Bind" to the database server. And this failure
happened just once. It was successful the other times. I am guessing this is
probably what is causing the "could not connect to datasource" error during
checkout. The odd thing is the we don't get the datasource error
consistently. It occurs probably 2 out 10 times. And the 2 times that it does
not work is inviting the unbridled wrath of our customers :-(

Here is an extract of the "failure" entry in the DTCPing log file. I
replaced the actual web server and database server names with <webserver> and
<dbserver> below:

++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from <dbserver>
Network Name: <webserver>
Source Port: 4354
Hosting Machine:<webserver>
05-09, 16:12:30.765-->Trying to Reverse Bind to <dbserver>...
Test Guid:AB38D5BC-310F-4C99-AD36-94A101AC7C76
Name Resolution:
<dbserver>-->192.168.50.9--><dbserver>
Error(0x6D9) at ServerManager.cpp @450
-->RPC reverse BIND failed
-->1753(There are no more endpoints available from the endpoint mapper.)
Reverse Binding to <dbserver> Failed
In GUID
Out GUID
Reverse BIND FAILED
Session Down

What would cause the "Reverse Bind" to fail intermittently? And how can we
prevent it from failing?

FYI - The "Distributed Transaction Coordinator" service is running on all 3
web servers and 1 database server. It is set to run Automatically. It is
using the Local System Account to run, and has the "Allow service to interact
with desktop" setting checked.

Also, the DTC dependent services: Remote Procedure Call, and Security
Accounts Manager are running on all 3 web servers and 1 database server. They
are also set to run automatically, and they are running with the Local system
account as well.

The Remote Procedure Call Locator service is NOT running on the 3 web
servers and 1 database server.

Any help you can provide to resolve this error will be greatly appreciated.

Thanks a lot.

Best regards,
Kiran Kakanur
http://www.reveregroup.com

"Vinod Kumar[MSFT]" wrote:

> This seems like a connection string issue. You should go and check the Transaction resource connection string. and Transaction Resource connection string. If this connection strings are fine then other place to
> look for would be DTC. Try using the DTC ping tool to see if the DTC is working properly.
>
> Thanks
> -Vinod
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcVSilNopJKMcdqER9G+xOEMI4u8gQ==
> X-WBNR-Posting-Host: 68.22.186.186
> From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <Kiran Kakanur@discussions.microsoft.com>
> Subject: Could not connect to datasource error in payment.asp
> Date: Fri, 6 May 2005 15:24:10 -0700
> Lines: 58
> Message-ID: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2714
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi,
>
> We are running MSCS 2000 + SP1 on Windows 2000 Advanced Server. And we are
> running SQL Server 2000 Std Ed + SP3. We recently moved the SQL db to another
> server. And we did have our share of connection string related issues after
> the DB move. I believe that we have updated all areas in Commerce Server
> Manager to reflect the new database server. And the fact that the site has
> been running smoothly after the DB move proves that.
>
> But lately we are seeing this rather sporadic error during customer
> checkout. The error message that we get is:
>
> Error Type:
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> Could not connect to datasource
> /<sitename>/include/payment.asp, line 248
>
> And line 248 is in a function called, SaveBasketAsOrder(...), in payment.asp
> as shown below:
>
> Sub SaveBasketAsOrder(mscsOrderGrp)
> Dim mscsOrderGrpMgr
>
> ' Remove any addresses from the orderform which are not referenced
> Call mscsOrderGrp.PurgeUnreferencedAddresses()
>
> Call mscsOrderGrp.SaveAsOrder() ' This is line 248
>
> ' Submit appropriate OrderForms using BizTalk
> Call InvokeBizTalk(mscsOrderGrp)
>
> Set mscsOrderGrpMgr = GetOrderGroupManager()
> Call mscsOrderGrpMgr.DeleteOrderGroupFromDisk(m_UserID)
>
> '// Call update of gift registy items
> Call UpdateGiftRegistryCounts(mscsOrderGrp)
>
> Call Analysis_LogSubmitOrder(mscsOrderGrp.Value(ORDERGROUP_ID)) 'Do this
> last, as it can't be rolled back
>
> End Sub
>
> The payment.asp has not been modified at all.
>
> Any thoughts what might be causing this and what can be done to eliminate it?
>
> Thanks a lot.
>
> Best regards,
> Kiran Kakanur
> The Revere Group
> http://www.reveregroup.com
>
>
>
>
>
>
>
>

Kiran Kakanur

2005-05-10, 5:55 pm

Hi Vinod,

I did some additional testing on our web site, and saw the following
"Information" entries in the "Application Log" in the Event Viewer on the web
server. These entries were created when I got the "could not connect to
datasource" error. And the time stamp for these entries exactly matches the
time that I was performing the test.

Event Type: Information
Event Source: MSDTC Client
Event Category: CM
Event ID: 4156
Date: 5/10/2005
Time: 3:01:49 PM
User: N/A
Computer: LONWEBSRVR-2
Description:
String message: Session idle timeout over, tearing down the session.

++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++

Event Type: Information
Event Source: MSDTC
Event Category: CM
Event ID: 4156
Date: 5/10/2005
Time: 3:01:49 PM
User: N/A
Computer: LONWEBSRVR-2
Description:
String message: Session idle timeout over, tearing down the session.

Based on the above entries the sources are MSDTCClient and MSDTC. These
entries are Informational only, and are not Errors.

Is it normal for the session to be torn if it is idle, or is it a problem
with our MSDTC configuration? If it is problem, what do we need to do to fix
it?

The odd thing is that if I click on the "Back" button in the browser and
resubmit the checkout page, it works fine. Could this mean that we have a
potential problem (hardware? performance?) with our web server which
intermittently loses contact with the database server?

Kiran

"Vinod Kumar[MSFT]" wrote:

> This seems like a connection string issue. You should go and check the Transaction resource connection string. and Transaction Resource connection string. If this connection strings are fine then other place to
> look for would be DTC. Try using the DTC ping tool to see if the DTC is working properly.
>
> Thanks
> -Vinod
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcVSilNopJKMcdqER9G+xOEMI4u8gQ==
> X-WBNR-Posting-Host: 68.22.186.186
> From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <Kiran Kakanur@discussions.microsoft.com>
> Subject: Could not connect to datasource error in payment.asp
> Date: Fri, 6 May 2005 15:24:10 -0700
> Lines: 58
> Message-ID: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2714
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi,
>
> We are running MSCS 2000 + SP1 on Windows 2000 Advanced Server. And we are
> running SQL Server 2000 Std Ed + SP3. We recently moved the SQL db to another
> server. And we did have our share of connection string related issues after
> the DB move. I believe that we have updated all areas in Commerce Server
> Manager to reflect the new database server. And the fact that the site has
> been running smoothly after the DB move proves that.
>
> But lately we are seeing this rather sporadic error during customer
> checkout. The error message that we get is:
>
> Error Type:
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> Could not connect to datasource
> /<sitename>/include/payment.asp, line 248
>
> And line 248 is in a function called, SaveBasketAsOrder(...), in payment.asp
> as shown below:
>
> Sub SaveBasketAsOrder(mscsOrderGrp)
> Dim mscsOrderGrpMgr
>
> ' Remove any addresses from the orderform which are not referenced
> Call mscsOrderGrp.PurgeUnreferencedAddresses()
>
> Call mscsOrderGrp.SaveAsOrder() ' This is line 248
>
> ' Submit appropriate OrderForms using BizTalk
> Call InvokeBizTalk(mscsOrderGrp)
>
> Set mscsOrderGrpMgr = GetOrderGroupManager()
> Call mscsOrderGrpMgr.DeleteOrderGroupFromDisk(m_UserID)
>
> '// Call update of gift registy items
> Call UpdateGiftRegistryCounts(mscsOrderGrp)
>
> Call Analysis_LogSubmitOrder(mscsOrderGrp.Value(ORDERGROUP_ID)) 'Do this
> last, as it can't be rolled back
>
> End Sub
>
> The payment.asp has not been modified at all.
>
> Any thoughts what might be causing this and what can be done to eliminate it?
>
> Thanks a lot.
>
> Best regards,
> Kiran Kakanur
> The Revere Group
> http://www.reveregroup.com
>
>
>
>
>
>
>
>

Vinod Kumar[MSFT]

2005-06-06, 5:56 pm

Sorry for the delay in response. I was out of office for few days.

If this error message occurs more frequently than every 10 minutes, it may indicate a problem. The HKLM\SOFTWARE\Microsoft\MSDTC\CmMaxIdleP
ings registry key controls the length of the session idle
timeout period. If this key does not exist, MS DTC uses a default value of 10 minutes. If the sessions are timing out before the idle timeout has expired, it may indicate that the DTCcm.dll file is somehow corrupted.

Thanks
-Vinod

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
--------------------
Thread-Topic: Could not connect to datasource error in payment.asp
thread-index: AcVVnoBX+Ow4cD/+RCq1dngyTp29rw==
X-WBNR-Posting-Host: 68.22.186.186
From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <KiranKakanur@discussions.microsoft.com>
References: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com> <42snTOLVFHA.388@TK2MSFTNGXA01.phx.gbl>
Subject: RE: Could not connect to datasource error in payment.asp
Date: Tue, 10 May 2005 13:26:09 -0700
Lines: 157
Message-ID: <F34E33A1-41D9-41E6-8436-A1480846A09A@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2727
X-Tomcat-NG: microsoft.public.commerceserver.general

Hi Vinod,

I did some additional testing on our web site, and saw the following
"Information" entries in the "Application Log" in the Event Viewer on the web
server. These entries were created when I got the "could not connect to
datasource" error. And the time stamp for these entries exactly matches the
time that I was performing the test.

Event Type: Information
Event Source: MSDTC Client
Event Category: CM
Event ID: 4156
Date: 5/10/2005
Time: 3:01:49 PM
User: N/A
Computer: LONWEBSRVR-2
Description:
String message: Session idle timeout over, tearing down the session.

++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++

Event Type: Information
Event Source: MSDTC
Event Category: CM
Event ID: 4156
Date: 5/10/2005
Time: 3:01:49 PM
User: N/A
Computer: LONWEBSRVR-2
Description:
String message: Session idle timeout over, tearing down the session.

Based on the above entries the sources are MSDTCClient and MSDTC. These
entries are Informational only, and are not Errors.

Is it normal for the session to be torn if it is idle, or is it a problem
with our MSDTC configuration? If it is problem, what do we need to do to fix
it?

The odd thing is that if I click on the "Back" button in the browser and
resubmit the checkout page, it works fine. Could this mean that we have a
potential problem (hardware? performance?) with our web server which
intermittently loses contact with the database server?

Kiran

"Vinod Kumar[MSFT]" wrote:

> This seems like a connection string issue. You should go and check the Transaction resource connection string. and Transaction Resource connection string. If this connection strings are fine then other
place to
> look for would be DTC. Try using the DTC ping tool to see if the DTC is working properly.
>
> Thanks
> -Vinod
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcVSilNopJKMcdqER9G+xOEMI4u8gQ==
> X-WBNR-Posting-Host: 68.22.186.186
> From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <Kiran Kakanur@discussions.microsoft.com>
> Subject: Could not connect to datasource error in payment.asp
> Date: Fri, 6 May 2005 15:24:10 -0700
> Lines: 58
> Message-ID: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2714
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi,
>
> We are running MSCS 2000 + SP1 on Windows 2000 Advanced Server. And we are
> running SQL Server 2000 Std Ed + SP3. We recently moved the SQL db to another
> server. And we did have our share of connection string related issues after
> the DB move. I believe that we have updated all areas in Commerce Server
> Manager to reflect the new database server. And the fact that the site has
> been running smoothly after the DB move proves that.
>
> But lately we are seeing this rather sporadic error during customer
> checkout. The error message that we get is:
>
> Error Type:
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> Could not connect to datasource
> /<sitename>/include/payment.asp, line 248
>
> And line 248 is in a function called, SaveBasketAsOrder(...), in payment.asp
> as shown below:
>
> Sub SaveBasketAsOrder(mscsOrderGrp)
> Dim mscsOrderGrpMgr
>
> ' Remove any addresses from the orderform which are not referenced
> Call mscsOrderGrp.PurgeUnreferencedAddresses()
>
> Call mscsOrderGrp.SaveAsOrder() ' This is line 248
>
> ' Submit appropriate OrderForms using BizTalk
> Call InvokeBizTalk(mscsOrderGrp)
>
> Set mscsOrderGrpMgr = GetOrderGroupManager()
> Call mscsOrderGrpMgr.DeleteOrderGroupFromDisk(m_UserID)
>
> '// Call update of gift registy items
> Call UpdateGiftRegistryCounts(mscsOrderGrp)
>
> Call Analysis_LogSubmitOrder(mscsOrderGrp.Value(ORDERGROUP_ID)) 'Do this
> last, as it can't be rolled back
>
> End Sub
>
> The payment.asp has not been modified at all.
>
> Any thoughts what might be causing this and what can be done to eliminate it?
>
> Thanks a lot.
>
> Best regards,
> Kiran Kakanur
> The Revere Group
> http://www.reveregroup.com
>
>
>
>
>
>
>
>

Oliver Besch

2005-06-28, 5:52 pm

Hi,

we are facing here the same problem. The registry key mentioned here is
valid for NT4.0 and MSDTC 2.0 only.
So did this help nevertheless running MS Server 2000 and Commerce Server 2002?

"Vinod Kumar[MSFT]" schrieb:

> Sorry for the delay in response. I was out of office for few days.
>
>
> If this error message occurs more frequently than every 10 minutes, it may indicate a problem. The HKLM\SOFTWARE\Microsoft\MSDTC\CmMaxIdleP
ings registry key controls the length of the session idle
> timeout period. If this key does not exist, MS DTC uses a default value of 10 minutes. If the sessions are timing out before the idle timeout has expired, it may indicate that the DTCcm.dll file is somehow corrupted.
>
>
> Thanks
> -Vinod
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcVVnoBX+Ow4cD/+RCq1dngyTp29rw==
> X-WBNR-Posting-Host: 68.22.186.186
> From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <KiranKakanur@discussions.microsoft.com>
> References: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com> <42snTOLVFHA.388@TK2MSFTNGXA01.phx.gbl>
> Subject: RE: Could not connect to datasource error in payment.asp
> Date: Tue, 10 May 2005 13:26:09 -0700
> Lines: 157
> Message-ID: <F34E33A1-41D9-41E6-8436-A1480846A09A@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 8bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2727
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi Vinod,
>
> I did some additional testing on our web site, and saw the following
> "Information" entries in the "Application Log" in the Event Viewer on the web
> server. These entries were created when I got the "could not connect to
> datasource" error. And the time stamp for these entries exactly matches the
> time that I was performing the test.
>
>
> Event Type: Information
> Event Source: MSDTC Client
> Event Category: CM
> Event ID: 4156
> Date: 5/10/2005
> Time: 3:01:49 PM
> User: N/A
> Computer: LONWEBSRVR-2
> Description:
> String message: Session idle timeout over, tearing down the session.
>
> ++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: CM
> Event ID: 4156
> Date: 5/10/2005
> Time: 3:01:49 PM
> User: N/A
> Computer: LONWEBSRVR-2
> Description:
> String message: Session idle timeout over, tearing down the session.
>
>
> Based on the above entries the sources are MSDTCClient and MSDTC. These
> entries are Informational only, and are not Errors.
>
> Is it normal for the session to be torn if it is idle, or is it a problem
> with our MSDTC configuration? If it is problem, what do we need to do to fix
> it?
>
> The odd thing is that if I click on the "Back" button in the browser and
> resubmit the checkout page, it works fine. Could this mean that we have a
> potential problem (hardware? performance?) with our web server which
> intermittently loses contact with the database server?
>
> Kiran
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "Vinod Kumar[MSFT]" wrote:
>
> place to
>
>

Vinod Kumar[MSFT]

2005-07-15, 5:56 pm

Did you try putting this fix?

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
--------------------
Thread-Topic: Could not connect to datasource error in payment.asp
thread-index: AcV76zmNMmtSadCaQKyEI2sgoui8PQ==
X-WBNR-Posting-Host: 138.190.15.46
From: =?Utf-8?B?T2xpdmVyIEJlc2No?= <OliverBesch@discussions.microsoft.com>
References: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com> <42snTOLVFHA.388@TK2MSFTNGXA01.phx.gbl> <F34E33A1-41D9-41E6-8436-A1480846A09A@microsoft.com>
<TYL6zLraFHA.3928@TK2MSFTNGXA01.phx.gbl>
Subject: RE: Could not connect to datasource error in payment.asp
Date: Tue, 28 Jun 2005 07:11:06 -0700
Lines: 206
Message-ID: <42B2CE04-4F71-4482-ADAB-7891A9087AFE@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2942
X-Tomcat-NG: microsoft.public.commerceserver.general

Hi,

we are facing here the same problem. The registry key mentioned here is
valid for NT4.0 and MSDTC 2.0 only.
So did this help nevertheless running MS Server 2000 and Commerce Server 2002?

"Vinod Kumar[MSFT]" schrieb:

> Sorry for the delay in response. I was out of office for few days.
>
>
> If this error message occurs more frequently than every 10 minutes, it may indicate a problem. The HKLM\SOFTWARE\Microsoft\MSDTC\CmMaxIdleP
ings registry key controls the length of the session
idle
> timeout period. If this key does not exist, MS DTC uses a default value of 10 minutes. If the sessions are timing out before the idle timeout has expired, it may indicate that the DTCcm.dll file is somehow
corrupted.
>
>
> Thanks
> -Vinod
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcVVnoBX+Ow4cD/+RCq1dngyTp29rw==
> X-WBNR-Posting-Host: 68.22.186.186
> From: "=?Utf-8?B?S2lyYW4gS2FrYW51cg==?=" <KiranKakanur@discussions.microsoft.com>
> References: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com> <42snTOLVFHA.388@TK2MSFTNGXA01.phx.gbl>
> Subject: RE: Could not connect to datasource error in payment.asp
> Date: Tue, 10 May 2005 13:26:09 -0700
> Lines: 157
> Message-ID: <F34E33A1-41D9-41E6-8436-A1480846A09A@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 8bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2727
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi Vinod,
>
> I did some additional testing on our web site, and saw the following
> "Information" entries in the "Application Log" in the Event Viewer on the web
> server. These entries were created when I got the "could not connect to
> datasource" error. And the time stamp for these entries exactly matches the
> time that I was performing the test.
>
>
> Event Type: Information
> Event Source: MSDTC Client
> Event Category: CM
> Event ID: 4156
> Date: 5/10/2005
> Time: 3:01:49 PM
> User: N/A
> Computer: LONWEBSRVR-2
> Description:
> String message: Session idle timeout over, tearing down the session.
>
> ++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++
>
> Event Type: Information
> Event Source: MSDTC
> Event Category: CM
> Event ID: 4156
> Date: 5/10/2005
> Time: 3:01:49 PM
> User: N/A
> Computer: LONWEBSRVR-2
> Description:
> String message: Session idle timeout over, tearing down the session.
>
>
> Based on the above entries the sources are MSDTCClient and MSDTC. These
> entries are Informational only, and are not Errors.
>
> Is it normal for the session to be torn if it is idle, or is it a problem
> with our MSDTC configuration? If it is problem, what do we need to do to fix
> it?
>
> The odd thing is that if I click on the "Back" button in the browser and
> resubmit the checkout page, it works fine. Could this mean that we have a
> potential problem (hardware? performance?) with our web server which
> intermittently loses contact with the database server?
>
> Kiran
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "Vinod Kumar[MSFT]" wrote:
>
other[vbcol=seagreen]
> place to
>
>

Oliver Besch

2005-07-18, 7:48 am

No, we haven't tried putting this fix so far because it is related to MTS
2.0. With our Commmerce 2002 on Windows 2000 Server we have MTS 3.0 deployed.
Thus, we do not have a MSDTC.dll but a MSDTC.exe. Our administrator says he
does not like to set these registry keys.
We simply do not know, if these registry keys apply from version 2.0 on or
until this version. This is perhaps due to fair english comprehension.
--
Oliver Besch

"Vinod Kumar[MSFT]" wrote:

> Did you try putting this fix?
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use. Â© 2002 Microsoft Corporation. All rights
> reserved.
> --------------------
> Thread-Topic: Could not connect to datasource error in payment.asp
> thread-index: AcV76zmNMmtSadCaQKyEI2sgoui8PQ==
> X-WBNR-Posting-Host: 138.190.15.46
> From: =?Utf-8?B?T2xpdmVyIEJlc2No?= <OliverBesch@discussions.microsoft.com>
> References: <AA1887A3-2C3D-4810-BA29-22620C4AE36F@microsoft.com> <42snTOLVFHA.388@TK2MSFTNGXA01.phx.gbl> <F34E33A1-41D9-41E6-8436-A1480846A09A@microsoft.com>
> <TYL6zLraFHA.3928@TK2MSFTNGXA01.phx.gbl>
> Subject: RE: Could not connect to datasource error in payment.asp
> Date: Tue, 28 Jun 2005 07:11:06 -0700
> Lines: 206
> Message-ID: <42B2CE04-4F71-4482-ADAB-7891A9087AFE@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 8bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.commerceserver.general
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2942
> X-Tomcat-NG: microsoft.public.commerceserver.general
>
> Hi,
>
> we are facing here the same problem. The registry key mentioned here is
> valid for NT4.0 and MSDTC 2.0 only.
> So did this help nevertheless running MS Server 2000 and Commerce Server 2002?
>
> "Vinod Kumar[MSFT]" schrieb:
>
> idle
> corrupted.
> other
>
>