MQSC Adapter Connection Failure with reason Code = 2538

I recently tried to test the MQSC adapter in BizTalk 2013 R2 servers was getting connection issues.. below are the server\ version details. MQ listener is running as BizTalk 2010 with the same MQ Client version is able to connect and read the messages. 

BizTalk Version : 2013 R2

HIS : 2013

MQ Client : 7.5.0.5

Error : 

The adapter "MQSC" raised an error message. Details "Failure encountered while attempting to open queue. queue = ****, queueManager = ****, reasonCode = 2538".

Remote host '***' not available, retry later.   The attempt to allocate a conversation using TCP/IP to host '***' for channel **** was not successful. However the error may be a transitory one and it may be possible to successfully allocate a TCP/IP conversation later. &P In some cases the remote host  cannot be determined and so is shown as '????'.  

Possible Resoluition

1) Telnet to the Queue. Verify if security is not blocking the ports. 

open command prompt enter the below command.
                   telnet "your Connection Name" "Port-number" eg: telnet TestMQ 3038

2) If you are able to telnet and still getting the connection error .. please check and use a Fully Qualified Name in the Connection Name of the Adapter Configuration.

Hope this help... If you have any question please feel to ping me .. 

Happy Integrating .. 

BizTalk 2013....

Got Biztalk 2013 from MSDN and Installed in my VM. I am much exited to check the new WebHttp Adapter. I feel this is a much awaited adapter to integrate with Restful service….

Will keep posted on the new cool features….

BizTalk 2013

Visual Studio 2012

Sql Server 2012

Windows Server 2008 R2

~Dheer

Use of multipleSiteBindingsEnabled property in IIS

Coming soon...



~Dheer

Adding Custom Headers in BizTalk WCF Service..

How do we add custom headers in BizTalk WCF Service? We are aware that we can add the custom Headers at the Port configuration level in SOAP adapter but this feature is removed from WCF adapter.  Below post will outline the process of adding the custom header.

We can have the header added in a Dynamic Manner by using custom Behavior, but the flip side of this is only custom Header Metadata is exposed and Document schema metadata will not be exposed to the End person.

What if we need both the Header and Document schema? We need to sue the below static method of adding the Custom Headers.

More to come.........



~Dheer

Handling Soap Exception with Multiple Operations in Orchestration…

How to handle Soap Exceptions with Multiple Operations in Orchestration.

Coming Soon.........

How to publish and EDI orchestration as Web service to return native message without external web service

1. Create an orchestration that takes in a string and return a string. Add a Call Orchestration shape to call into the original orchestration that accepts the EDI in the XML format.
2. Build and deploy the orchestration.
3. Run the WCF Service Publishing Wizard to publish the orchestration as a WCF service.

4. Open the web.config file where the Orchestration is published and add the following under

a.

5. If Sharepoint is installed on tha machine, open the Sharepoint Central Admin console and go to: "Configure Virtual Server Settings -> "Default Web Site" -> "Define Managed Paths" and under "Add a New Path" exclude the virtual directory where the WCF Service is hosted.
6. Go to the BizTalk Server Admin Console, and configure the new WCF Receive Location as follows:

a. Change Receive Pipeline to EdiReceive. And Send Pipeline to EdiSend.

b. Under "Transport" -> "Type" click "Configure"

c. Go to the "Messages" tab and under the "Inbound BizTalk message body" select the "Path" option.

d. For the "Body path expression enter: /*[local-name()='string']

e. For the "Node encoding" select: String

f. Click OK and then on the Receive Location Properties click OK again.

g. Enable the WCF Receive Location. This is needed to be able to build the proxy using svcutil.

7. Run the svcutil.exe to generate the proxy and config file for the WCF Service and build the client. Client should pass the EDI message as a string (in the native EDI format) to the Orchestration.
8. Go back to the Orchestration and modify the incoming request and the outgoing response from a String to the required EDI formats.
9. Build and deploy the orchestration. Start everything. Send the EDI message in native format from the client. You should receive the response back in native EDI format.

Performance and Operations Guides in TechNet

Microsoft BizTalk Server Performance Optimization Guide
http://technet.microsoft.com/en-us/library/cc558617.aspx

Microsoft BizTalk Server Operations Guide
http://technet.microsoft.com/en-us/library/cc296643.aspx

BizTalk Server Database Optimization
http://technet.microsoft.com/en-us/library/bb743398.aspx