Microsoft Knowledge Base Email Alertz

KBAlertz.com: The BizTalk Server SAP adapter stops receiving IDOC messages in BizTalk Server

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 949855 - Last Review: March 24, 2009 - Revision: 1.0

The BizTalk Server SAP adapter stops receiving IDOC messages in BizTalk Server

SYMPTOMS

Consider the following scenario. You are using Microsoft BizTalk Server. You send an IDOC message. An IDOC message is an intermediate SAP document from the SAP system to the server that is running BizTalk Server. The BizTalk Server SAP adapter stops receiving IDOC messages, and the following error may be logged in the event log:

Error in Check Transaction: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Additionally, BizTalk Server receives the IDOC messages if the BizTalk Server host is restarted or if the blocking process on the server that is running Microsoft SQL Server is killed.

CAUSE

This problem occurs because the index on the SAPTid table that is used by the BizTalk Server SAP adapter is not available.

WORKAROUND

To work around this problem, the index for the SAPTid table must be created. Ask the database administrator to run the following SQL script in the MessageBox database.
 
create unique clustered index SAPTid_clusteredIndex_RfcTID ON SAPTid (RfcTID)

APPLIES TO
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Ed.
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
Keywords: 
kbexpertiseadvanced kbtshoot kbsurveynew kbprb KB949855
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please