Wednesday, October 14, 2009

BizTalk Adapter v2.0 for mySAP Business Suite - Could not open a connection to SQL Server

During a non-production dry run implementation of BizTalk 2009 yesterday, we ran into the following error when an application that uses the SAP Adapter (.Net Connector Version) received an IDoc.

Note: this post is strictly related to the .Net Connector version of the SAP adapter and NOT the WCF based LOB Adapter. We have some applications that we have not migrated to the new adapter. It is on our "to do" list, but our upgrade scope is primarily a "like for like" upgrade.


Event Type: Error
Event Source: BizTalk Adapter v2.0 for mySAP Business Suite
Event Category: None
Event ID: 0
Date: 10/13/2009
Time: 4:23:28 PM
User: N/A
Computer: Server
Description:
Error in Check Transaction: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




The first clue that something was wrong was that SAP did not show up in the configured list of Adapters. We were able to add it by right clicking on "Adapters" - "New" - "Adapters" before we turned on the application but that should have been our first indication that something wasn't quite right. We then checked for the existance of the following Stored Procedures that are added to the MessageBox database when you install the SAP Adapter:
- Mp_Sap_check_tid
- Mp_Sap_delete_tid
- Mp_Sap_insert_tid

These stored procs were not installed which prompted us to re-install the adapter. We also ensured to use the /console command when launching the Remote Desktop Connection tool. Upon removing the old adapter via control panel(repair didn't work) and re-installing the adapter we now had "SAP" showing up in the adapter list and the stored procedures were successfully added to the MessageBox Db. At this point we were able to successfully receive an IDoc from SAP.

5 comments:

Tudo Truong said...

Hi Kent,

We are trying to use this BizTalk Adapter v2.0 for mySAP Business Suite with BizTalk 2013 (with SAP connector) as we are also doing a like for like upgrade. But we have had no luck in receiving an idoc. Furthermore no errors are thrown.

After reading your post, I was wondering if by any chance you had to use this adapter with BizTalk 2013?

Thnak you.

Tudo Truong said...

Hi Kent,

We are planning to migrate to BizTalk 2013. We will intially be performing a like for like upgrade.
However we have been having issues while testing BizTalk Adapter v2.0 for mySAP Business Suite (with SAP connector) in Biztalk 2013 as no IDocs are received. Furthermore no errors are thrown.

I was wondering if you had a chance to use BizTalk Adapter v2.0 for mySAP Business Suite with BizTalk 2013?

Looking forward to hearing from you.

PS: Congratulations on finishing the Berlin marathon, I am myself a marathon runner it is always a great achivement to complete one.

Kent Weare said...

Hi Tudo,

I use this adapter every (work) day with BizTalk 2013. One thing I have not done with it though (in 2013) is receive an IDOC. I have scenarios where I am calling RFCs/BAPIs. However, with BizTalk 2010 at another company we were receiving 1000s of IDOCs every day.

So a few things that I would check;
- Have the pre-requisite SAP Dlls been installed in the correct System32 and SYSWOW64 (64 bit) directories.

- Are you able to do a connected client test from SAP? When you turn on a Receive location that uses this adapter a connection is established to SAP and from SAP you can perform this test. It is much like a Ping but it will confirm whether or not you have a listener. You can perform this test from a transaction called SM59

Marathons are a tough feat. I would like to run the New York marathon but probably not for a couple years. As I am sure you have experienced, setting aside the time to train that much is difficult. I will continue to run half marathons in the mean time.

Tudo Truong said...

Hi Kent,

Thank you for your quick reply.

We are actually able to call BAPIs and have successfully connection tested the RFCs having the BizTalk 2013 machine as target with SM59. We just cannot receive any IDocs.
We will check again that all the pre-requisite SAP Dlls are installed.


New york marathon is the ultimate one for most marathon runners. I woud love to run it too.Yeah training marathon is very demanding and not simple to find time to train.

Kent Weare said...

If you can call BAPIs and perform the connected client test then I believe the SAP dlls have been correctly installed.

My gut tells me that the Trading Partner configuration in SAP is not setup correctly.