Chris Vidotto's Blog

Hi Chris,

The connector we are using is of 1.2.0.0, during installation it is not prompting for "Runtime only" option.
Does v1.0.3 allows to install "Runtime only" ?
(At present, I don't have v1.0.3. to try it out)

Pl advise.

Thanks
Kishore

Chris,

I forgot to mention, we are gettng followin error when we tried to install connector 1.2 on BTS 2006/VS.NET 2005
"unable to get installer type in the C:\program files\microsoft visual studio.net 2003\
common7\ide\sap.connector.design.dll assembly. --> One or more of the types in the
assembly unbale to load."
I guess, as you explained, it is looking for vs.net 2003

Kishore

Chris,

with .net connector 1.0 from sap marketplace, worked out.

Thanks
Kishore

As you may be aware, SAP .NET Connector version 2.0 doesn't work from within VS.NET 2005. It's impossible to use the proxy generator wizard in the new VS IDE.

For those of you interested, we've developed a NEW SAP .NET Connector to be used with VS.NET 2005. It's fully build with C# & .NET Framework 2.0 and doesn't require Java runtime at all (as SAP's Connector does.) providing seamless SAP interface programming .

Features:

- Execute BAPIs and RCs with few lines of code.
- Send and receive IDocs.
- Call .NET functions from ABAP programs using the RFC Server classes.
- Supports RFC & SOAP for full integration in SAP NetWeaver scenarios.
- Read SAP tables directly
- Generate and execute ABAP code on the fly.
- Use Batch Input to execute tracsactions in SAP.

It provides a far more natural way of interface programming trought exposing each function with objects such as Imports/Exports/Tables/Structures, common elements to ABAP programmers.

Wizard generated code is more legible and maintanable than classic SAP .NET Connector Wizard's one.

We have a license that provides full source code, many examples & documentation at a very competitive price.

Please feel free to send questions and comments to danteotero@hotmail.com.

Regards,

Ing. Dante R. Otero

Hi,

I've been testing the integration with SAP with BTS2006 but I have some problems. This is the error in EventLog when I run an orchestration:

The Messaging Engine failed to create the transport adapter "SAP".
OutboundAssemblyPath: "NULL"
OutboundTypeName: "Microsoft.Biztalk.Adapter.SAPAdapter.SAPTransmitter,SAPTransmitter, Version=2.0.1.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35"
Exception Details: "Retrieving the COM class factory for component with CLSID {1EB415A4-242C-4E28-9E9C-33367784F01E} failed due to the following error: 8007007e."


This is the software installed on machine:
SQLServer2005 – 9.0.1399
VS2005 – 8.0.50727.42 (RTM.050727-4200)
BTS2006 – 3.5.1602.0 Enterprise Edition
SAP.NET Connector Runtime – 1.0.3
BTS Adapter v2.0 for mySAP Business Suite SP1

In advance, I get an error when I installed the Adapter SP1:

Error 6000.An error occured when adding the adapter to BizTalk configuration. Either the BizTalk configuration database was not found, or an Adapter for SAP was already added to the configuration. Click Cancel if you wish to roll back this installation or click OK to successfully complete this installation, and then manually add this adapter.

I really don't know how to resolve this problem.

Thanks in advance,

Carlos

Any updates on this? I get the same error with the same configuration in BizTalk Server 2006 Developer.

Bo Pedersen

I am also getting the same error with the same configuration as Carlos. Did anyone ever hear back what the problem was and how to fix it?

I have the same problem. does somebody know the solution? thanks so much for reply....

martin.hunady@microsoft.com

Hi,

I was also experiencing the COM issue, and have found the problem (and a solution).

I had a search around and discovered that error 8007007e is a standard COM error meaning it cannot find a specific component/file.

I ran filemon to see what it was trying to load, and (for my machine atleast), it was trying to load ATL71.dll but could not find it.

I then did a search and this dll wasn't on my machine at all. I downloaded it from http://www.dll-files.com/dllindex/dll-files.shtml?atl71 and placed it in the "C:\Program Files\Microsoft BizTalk Adapter v2.0 for mySAP Business Suite" directory. Now making it to the next wizard prompt. Yay!

I had the same issue and copying ATL71.dll solved the problem. Does anyone know why this dll is missing in the first place?

Thanks Nic.

I have exactly the same problem, after copying ATL71.dll into the "C:\Program Files\Microsoft BizTalk Adapter v2.0 for mySAP Business Suite" directory, it works!

Cheers.

Hello people

I know why you need ATL71.dll because normally

you need visual studio 2003 to have Sap

adapter but you can compensate by having only

ATL71.dll the best is to get it from source

cause it is dangerous to have dlls from the

net.

Cheers

Hi,

  I am struglilng to install SAP adapter in BTS2006, visual studio 2005. What r the requirments for install SAP adapter. I tried to install SAP.Net connector 2.0 in my system it's asking visual studio 2003 version. It's must to install SAP adapter.

Plz help me, I am struglling a lot for this one.

Hi

Please let me know how to get the CTP update for the BTS 2004 sap adapter

Regards,

Srini

(vaasulk@yahoo.com)

Dear Chris,

We are planning for SAP ERP Integration using BizTalk Server 2006

I have some queries related to BizTalk Adapter v2.0 for mySAP  Business Suite.

1- Do BizTalk Adapter v2.0 for mySAP  Business Suite supports integration with SAP ERP ECC 6.0

2- Is SAP.Net connector required on Both sides BizTalk Server and SAP ERP?

3- Can we use the combination BizTalk Server 2006 +  SAP.Net connector v2.0 + BizTalk Adapter v2.0 for mySAP  Business Suite +Visual Studio .Net 2005

PingBack from http://www.keyongtech.com/332491-a-problem-about-sap-adapter