|
Home > Archive > BizTalk Server Applications Integration > July 2005 > BizTalk SAP Adaptor limitation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk SAP Adaptor limitation
|
|
| herbat73@yahoo.com 2005-07-19, 7:48 am |
| Dear Readers,
Recently I have a problem with processing large IDocs (over 12MB).
I am running on W2K +SP4, BTS 2002, SAP Adaptor 1.0
It seems that large idocs cannot be handled by Windows 2K MSMQ
(inframouse 4MB Unicode limit).
Unfortunatelly SAP Adaptor can work only with MSMQ and there is no way
to save idoc to file without MSMQ.
any input will be appreciated
There are event descriptions.
--------------------------------------------------------------
(104) The IDoc Handler COM server DLL was not able to
deliver an IDoc to MSMQ. HRESULT = c00e0027
Error description = There are insufficient resources to perform the
operation.
EXPLANATION
This error may be caused by a failure in Message Queueing.
ACTION
The SAP system and the IDoc Handler DLL should cooperate to
try to deliver this IDoc to BizTalk again. If event 102
follows this event, stating that the same IDoc transaction
was retried, and there are no further Error category events
after that, then no action is necessary.
If the error recurs, contact Microsoft support
--------------------------------------------------------------
(112) The IDoc Handler COM server DLL failed while processing the.
IDoc that SAP com4abap delivered with the Idoc_Inbound_Asynchronous
method.
HRESULT=c00e0027
Description=Failed placing the IDoc in the message queue
EXPLANATION
A system failure occurred while processing an IDoc, before
the DLL was able to send it to BizTalk.
ACTION
Make sure that the SAP DCOM Connector com4abap service is
configured correctly. Default Server Component COM Class
(IDocHandler.IDocHandler.1) and Type Library in XML
(IDocHandlerLib).
Use the BizTalk Adapter for SAP to make sure the correct
SAP Systems, Routing Keys and MSMQs are also defined.
--------------------------------------------------------------
The description for Event ID ( 103 ) in Source ( SAP COM for ABAP )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. The following information is part of the event: Error while
invoking IDOC_INBOUND_ASYNCHRONOUS: ..
| |
| Jeff Lynch 2005-07-19, 8:47 pm |
| Take a look at this post in EldarM's blog. In BTS2004 the 4 MB limit is gone
with MSMQ Adapter but you will need a lot of RAM.
http://blogs.msdn.com/eldarm/archiv.../03/424894.aspx
--
Jeff Lynch
"A BizTalk Enthusiast"
http://codebetter.com/blogs/jeff.lynch
<herbat73@yahoo.com> wrote in message
news:1121774855.103011.70480@g14g2000cwa.googlegroups.com...
> Dear Readers,
>
> Recently I have a problem with processing large IDocs (over 12MB).
> I am running on W2K +SP4, BTS 2002, SAP Adaptor 1.0
>
> It seems that large idocs cannot be handled by Windows 2K MSMQ
> (inframouse 4MB Unicode limit).
> Unfortunatelly SAP Adaptor can work only with MSMQ and there is no way
> to save idoc to file without MSMQ.
>
> any input will be appreciated
>
> There are event descriptions.
>
> --------------------------------------------------------------
>
> (104) The IDoc Handler COM server DLL was not able to
> deliver an IDoc to MSMQ. HRESULT = c00e0027
> Error description = There are insufficient resources to perform the
> operation.
>
> EXPLANATION
> This error may be caused by a failure in Message Queueing.
>
> ACTION
> The SAP system and the IDoc Handler DLL should cooperate to
> try to deliver this IDoc to BizTalk again. If event 102
> follows this event, stating that the same IDoc transaction
> was retried, and there are no further Error category events
> after that, then no action is necessary.
> If the error recurs, contact Microsoft support
>
> --------------------------------------------------------------
>
> (112) The IDoc Handler COM server DLL failed while processing the.
> IDoc that SAP com4abap delivered with the Idoc_Inbound_Asynchronous
> method.
>
> HRESULT=c00e0027
>
> Description=Failed placing the IDoc in the message queue
>
> EXPLANATION
> A system failure occurred while processing an IDoc, before
> the DLL was able to send it to BizTalk.
> ACTION
> Make sure that the SAP DCOM Connector com4abap service is
> configured correctly. Default Server Component COM Class
> (IDocHandler.IDocHandler.1) and Type Library in XML
> (IDocHandlerLib).
> Use the BizTalk Adapter for SAP to make sure the correct
> SAP Systems, Routing Keys and MSMQs are also defined.
>
> --------------------------------------------------------------
>
> The description for Event ID ( 103 ) in Source ( SAP COM for ABAP )
> cannot be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote
> computer. The following information is part of the event: Error while
> invoking IDOC_INBOUND_ASYNCHRONOUS: ..
>
|
|
|
|
|