SAP adapter problem - RfcAbort: Cannot lock transaction

[Kim Bergstr?m]

Hi,

I'm having problems with receiving IDocs from an SAP system using the
BizTalk Adapter v2.0 for mySAP Business Suite. I've set up a receive
port and location and when we test the RFC destination in SAP the
connection to BizTalk works. However, when an IDoc is sent it fails
with the error "RfcAbort: Cannot lock transaction".

I'm using Microsoft BizTalk Server 2004 (v. 3.0.4902.0), the SAP .NET
Connector Runtime (v. 1.2.1) and Microsoft BizTalk Adapter v2.0 for
MySAP Business Suite (v. 2.0.0313.0) in this test environment. I've
also installed hotfix 884553 (see below).

I initially had problems in my development environment where I got an
error message in SAP saying "TARGET_METHOD_EXCEPTION raised by
external server". I found a hotfix (884553), which solved this so
everything works fine there. But in the development environment I'm
using the SAP .NET Connector v2.0. That is the only difference as far
as I can see.

Don't really know where to start error tracking so any help would be
appreciated!

Thanks,
Kim

[Jason S]

Hi all,

I am having the exact same issue as Kim, except I'm running SP1 (v.
3.0.6070.0) and v. 2.0 of the .NET Connector. We are able to test the
connection between SAP and BTS successfully, but when we attempt to
send an IDOC via the tRFC port we've configured, we get this error. No
errors in the event log, nothing in HAT. We enabled tracing on the SAP
side and it looks like the IDOC is being transferred successfully but
something is failing in the adapter shortly thereafter. I can provide
the SAP trace if that would be helpful.

The adapter documentation (which sets a new record for sparseness) has
not been helpful. Any and all assistance in troubleshooting this issue
will be greatly appreciated.

Jason S.

[Jason S]

Hi all,

I've found a solution. First, some background. The SAP adapter relies
on a couple of stored procedures it installs in the message box
database. No specific permissions are applied to these procedures by
the installer (or so it seems). Consequently, non-admins cannot call
them successfully. My BizTalk host account normally runs at low
privilege, as per best practices. As low privilege == non-admin, the
host was failing trying to call these stored procedures.

To resolve the problem, I've temporarily elevated the host account to
Admin. However, it should be possible to determine and implement more
granular permissions so the account can remain low privilege and still
work.

Ping me if you have any questions.

Jason S.

[Mark]

Hi,

running with SAP .NET Connector V2 - are you able to generate Idoc schema?

thks
mark

Post by Jason S
Hi all,
I've found a solution. First, some background. The SAP adapter relies
on a couple of stored procedures it installs in the message box
database. No specific permissions are applied to these procedures by
the installer (or so it seems). Consequently, non-admins cannot call
them successfully. My BizTalk host account normally runs at low
privilege, as per best practices. As low privilege == non-admin, the
host was failing trying to call these stored procedures.
To resolve the problem, I've temporarily elevated the host account to
Admin. However, it should be possible to determine and implement more
granular permissions so the account can remain low privilege and still
work.
Ping me if you have any questions.
Jason S.

[Jason S]

Mark,

I've also learned that only the 1.0.x versions of the .NET Connector
are supported. Uninstall the adapter, uninstall 2.0, install 1.0.x
(greater than 1.0.2; I'm using 1.0.3), install the adapter. Should
start working better.

Jason S.

[Kim Bergstr?m]

Thanks Jason!

I added my BizTalk host account to the Admin group and that solved my problems.

Kim

Post by Jason S
Mark,
I've also learned that only the 1.0.x versions of the .NET Connector
are supported. Uninstall the adapter, uninstall 2.0, install 1.0.x
(greater than 1.0.2; I'm using 1.0.3), install the adapter. Should
start working better.
Jason S.