Configuring SAP and BizTalk

SAP BIZTALK & ASSOCIATED ISSUES

I get countless problems with SAP, it’s a pain to get going, but once its working, it’s golden.

Have you ever experienced any of these errors, well here are the errors and the solutions.

ERROR 1: The Messaging Engine failed while executing the inbound map for the message coming from source Details:"Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly. "

ERROR 2: The Messaging Engine failed to add a receive location …. to the adapter "WCF-SAP". Reason: "Microsoft.ServiceModel.Channels.Common.ConnectionException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_BUSY. SapErrorMessage=CMALLC : rc=2 > Connect from SAP gateway to RFC server failed

Connect_PM  DEST=BIZTALK_2, TPNAME=BIZTALK_2

ERROR 3: The receive location "SAPxyz" with URL "sap://CLIENT=100;LANG=ENxyz&ListenerProgramId=BIZTALK_2&RfcSdkTrace=False&AbapDebug=False" is shutting down. Details:"The Messaging Engine failed while notifying an adapter of its configuration. ".

ERROR 4: The Messaging Engine failed to add a receive location "SAPxyz" with URL "sap://CLIENT=100;LANG=EN;@a/xyz…&ListenerProgramId=BIZTALK_2&RfcSdkTrace=False&AbapDebug=False" to the adapter "WCF-SAP". Reason: "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_SYSTEM_FAILURE. SapErrorMessage=Open file 'saprfc.ini' failed: 'No such file or directory'.

Answer 1: When the sap adapter is deployed, it is supposed to deploy this assembly, however it does not, so you need to add it as a resource to BizTalk. 

 

 Answer 2 & 3

These are related, check you have a receive location setup, with your program ID, go into the SAP GUI and check via the /nsmgw command, look for your host, it will be the one running the BTSNTSvc command. You need to have it appear here first, get a receive location hooked up to this… if not there is your problem.

 

Check /nsm59 look for your entry point under TCP/IP, and sure it exists.

Double click on it, and make sure the activation type is registered service program, it is not the default. Your SAP admin will need to fix this.

Perform the connection test, it must pass…your receive location will need to be configured and running....

Answer 4: 

Read what it says in the description panel, for destination name, there are two of these… make both blank, it will stop asking you for the saprfc.ini

 

BAM Portal Not Installing

You installed BizTalk Server

You want to config BAM Portal see this error:

Failed to validate BAM Portal Web site (BAMPortal)

   Additional information:

      The BAM Portal website Default Web Site is not valid.

      (Microsoft.Biztalk.Bam.CfgExtHelper.PortalHelper)

      Exception from HRESULT : 0x80005008(System.DirectoryServives)

Basically its not allowing you to select the default website, its giving a red cross. 

Simple Solution:

1. Open the Server Manager MMC snap-in (right-click on Computer and select the Manage option).
2. Expand the features node.
3. Select the Web Server node.
4. Look through the role services.  Check for IIS 6 Management Compatibility and see if it says it is installed.
5. If not installed, click Add Role Services on right of screen.  Select the IIS 6 Management Compatibility and install.
6. Go back to BizTalk configuration, the BAM Portal feature should now install without any issues.

Please verify that the pipeline strong name is correct and that the pipeline assembly is in the GAC.

We have received the error:

There was a failure executing the response(send) pipeline: "xxx" Source: "Unknown " Receive Port: "yyy.TwoWay" URI: "/path/BTSHTTPReceive.dll?Receive" Reason: Failed to get pipeline: Namesapce.Pipelines.CPipeline,Namespace.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=edf16f912420a3a8. Please verify that the pipeline strong name is correct and that the pipeline assembly is in the GAC.

With many errors in BizTalk with this error, on the two way receive port, all suspended not resumable. 

We recently did a deployment, and ever since then this has been occurring. We deployed, we did the normal remove all, re-deploy and restart all hosts. 

Still this error occurred. 

It turned out that one of the Dev’s had renamed one of the pipelines, slightly, and when we deployed we forgot the one very important host. 

All of the errors were occurring under the Isolated Adapter, as this was a http receive port. This runs under the isolated host. 

What is the Isolated host? And how can I restart this? It says not applicable in BizTalk Admin. 

Well it’s any out of process host, for the HTTP receive, and most of these, its isolated host, is…. IIS.

Doing an IISReset, is just like restarting that isolated host.  It flushed the old assemblies from memory, and  caused it to reload all assemblies fresh from the GAC.