Consider the following scenario:
- You have a computer that is running Microsoft
BizTalk Server 2006 with the Microsoft BizTalk Adapter 2.0 for mySAP Business Suite installed.
- You configure a send port to send messages to an SAP server
by using the BizTalk Adapter 2.0 for mySAP Business Suite.
- You use the adapter to make SAP Business API (BAPI) calls
by using an
OPENREUSE connection.
Note For more information about the OPENREUSE connection,
refer to the "More information" section. - After you open a connection by using an OPENREUSE connection and
before you use a REUSECLOSECONNECTION value to send the next
message
to the SAP server by,
you restart the BizTalk Server host instance.
In this scenario, messages
that you intend to send over a reused connection are not sent.
The corresponding orchestration instance is dehydrated and cannot be resumed.
The
messages
remain active in
the send
port and cannot be sent to the SAP server.
Note When this problem occurs,
no error message is raised, and no
event
is logged.
When
the
OPENREUSE option is used, BizTalk Server 2006 maintains
an in-memory hash table that contains the
cached (reusable) SAP connection objects.
After you restart the BizTalk Server host
instance, the hash table is lost and therefore a nullReferenceException exception
occurs
when the SAP send ports try to reuse the cached SAP connections.
However, the exception is not
handled
by
Microsoft BizTalk Adapter 2.0 for mySAP Business Suite.
Hotfix information
A supported
hotfix is available from Microsoft. However, this hotfix is intended to correct
only the problem that is described in this article. Apply this hotfix only to
systems that are experiencing the problem described in this article. This
hotfix might receive additional testing. Therefore, if you are not severely
affected by this problem, we recommend that you wait for the next software
update that contains this hotfix.
If the hotfix is available for
download, there is a "Hotfix download available" section at the top of this
Knowledge Base article. If this section does not appear, contact Microsoft
Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
Prerequisites
You must have BizTalk Server 2006 and BizTalk Adapter 2.0
for mySAP Business Suite Service Pack 1 installed to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this
hotfix. However, you must restart the BizTalk host instance service after you
apply this hotfix.
Hotfix replacement information
This hotfix does not replace other hotfixes.
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the
Time
Zone tab in the
Date and Time item in Control
Panel.
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Invoke.dll | 2.0.1027.0 | 11,584 | 27-Oct-2009 | 18:41 | x86 |
| Rfcschemaproxygenerator.dll | 2.0.1027.0 | 104,288 | 27-Oct-2009 | 18:41 | x86 |
| Saptransmitter.dll | 2.0.1027.0 | 83,792 | 27-Oct-2009 | 18:41 | x86 |
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
To reuse connections when you connect to an
SAP server by using the BizTalk Adapter 2.0 for mySAP
Business Suite,
you can specify a value in the
ConnectionType property
that is
exposed in Microsoft.BizTalk.SAPAdapterProperties.dll.
For example, you
can open a connection by specifying the
ConnectionType property
as
OPENREUSE.
You
can reuse
an open connection by specifying the property
value as
REUSEOPENCONNECTION. Also, you can reuse an open
connection and close
it by specifying the property as
REUSECLOSECONNECTION. The
REUSECLOSECONNECTION connection is typically used to commit or rollback a transaction.
MsgTmpRequest(SAPSend.ConnectionType) = 'OPENREUSE'
MsgTmpRequest(SAPSend.ConnectionType) = 'REUSEOPENCONNECTION'
MsgCommit(SAPSend.ConnectionType) = 'REUSECLOSECONNECTION'
MsgRollback(SAPSend.ConnectionType) = 'REUSECLOSECONNECTION'
For more information about the OpenReuse connection, click the following article number to view the article in the Microsoft Knowledge Base:
934328Â
(http://kbalertz.com/Feedback.aspx?kbNumber=934328/
)
Implementation of the OpenReuse value and the ReuseOpenConnection value
in the BizTalk SAP adapter
For more information about BizTalk Server hot
fixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2003907/
)
Information on BizTalk Server hot
fixes