Friday, April 29, 2016

Invalid or expired security context token or there is mismatch between bindings

While testing  WCF-WSHTTP based service using SOAP UI got following error

"The message with To ' ' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndPointAddresses agree."

Why it happened and what to do:

Issue was the Request message is missing a To tag in the soap header.

On the Message Editor, just below the request message window click on button WS-A(WS-Addressing) and set WS-Addressing property to true. Then select the checkbox "Add default wsa:To"

At BizTalk end WSHttp adapter(the WCF service) utilises the WS-Addressing standard to identify the receive location to which the message needs to be submitted.

So that error was gone but a new error appeared as can be seen below:

To overcome this, go to receive location and click on configure WCF-WSHttp adapter and set the Security mode to None and you are done.

Tuesday, March 22, 2016

The Web server is configured not to list the contents of this directory

Today, I was demonstrating how to publish BizTalk schema as WCF service to my new team member. Created a simple schema and publish this schema as WCF service using the Publishing wizard, followed by enabling the receive location created by wizard. But while browsing this service was welcome by HTTP Error stating that "The Web server is configured not to list the contents of this directory"

Why it happened

It was because Directory Browsing was not enabled on the machine.

What to do

Go to IIS manager-->Directory Browsing. On right top there is Enable property - click it. After that service was accessible.

Wednesday, March 9, 2016

Begineer to BizTalk Expert : Interview with Glenn Colpaert

Welcome to Nineteenth interview of the series, today's expert is Glenn Colpaert.

Glenn Colpaert is an Integration Consultant and Microsoft Integration MVP at Codit.

He has been integrating businesses with BizTalk & Microsoft technologies for more than 5 years. During these years he was involved in many EAI and B2B projects - both on-premise and hybrid (cloud). 
He has gained a lot of hand-on experience during his projects and likes to share it with colleagues and the community.

Glenn is also part of the Microsoft Azure Insider program as well as the BizTalk Advisors group.
He became a board member of (, the Belgian BizTalk User Group and is an active blogger on the Codit Blog(

Glenn tweets via

Let's begin the Interview....

Mahesh: Who are you and what you do?
Glenn: My name is Glenn Colpaert and I’m based in Belgium where I live in a small town with my wife and son. I work as an Integration Consultant for Codit and next to my day to day job I’m also a Microsoft Azure MVP and organizing community events with the Belgian BizTalk User Group.

Mahesh: When did you start working on BizTalk?
Glenn: I started working with BizTalk in 2009 when I joined Codit. Basically I started working with BizTalk 2006 and beyond. 

Mahesh: How did you mastered BizTalk (Learning path, amount of time)?
Glenn: I received a two weeks training when I started my job and after that I really started learning BizTalk by using the product day to day at customers.
Mastering BizTalk is all about working with the product and discovering all the possibilities. Remember, there are tons of great resources out there to learn all about BizTalk and Integration in general.

Mahesh: Which are the major projects you handled so far?
Glenn: Over the last couple of yeast I have worked on quite a few BizTalk and Integration project. I also had the change to integrate with different types of applications and other technologies which allowed me to broaden up my knowledge about different systems.
If I have to choose one project out of the many I’d choose a project we did to connect 32 member states across Europe to exchange electronic information using the new AS4 messaging protocol.

Mahesh: How do you see BizTalk compare to other integration platform?
Glenn:Personally I do not have many experience with other integration platforms such as Oracle, Tibco or Websphere. But I believe that BizTalk is a very competitive and mature product and can perfectly compete with products from other vendors. 

Mahesh: What as per you is must to know to become an Integration (BizTalk) Expert?
Glenn: Hard question, what is an Expert? I believe becoming an expert is all about the hand-on experience, like I already stated: learn by doing!
There is however a shortcut, if you can master BAM you are automatically awarded expert level! :)

Mahesh: What are your thoughts on forums,blogs and articles etc.?
Glenn: Forums, blogs, articles, sessions, integration Monday,… These are all super important resources to be able to share knowledge across integration developers and people that are interested into integration. It is something that everyone can benefit from and it’s great to see that he BizTalk/Integration community has such a great set of contributors on all levels! And I want to thank each and every one for that!

Mahesh: Your suggestion to a newcomers? What should be approach to get sound knowledge in BizTalk?
Glenn: As I already mentioned couple of times during this interview there are a great set of resources out there to learn BizTalk. But in my opinion, and that’s also how I learned it, the best way to learn and to ‘master’ BizTalk is by doing it. Challenge yourself to build crazy integration scenarios and you’ll learn all the good stuff and pitfalls along the way.

Mahesh: What are your thoughts around BizTalk certification?
Glenn: Let me rephrase that question! ‘What are your thoughts around Certifications’?
Certifications are a necessary pain, it shows that you have knowledge of the product to a certain level, but it does not make you an expert on it. Therefor you need experience and work with the product or technology. 

Mahesh: What is the future of BizTalk?
Glenn: As Microsoft already stated ‘Integration is about to level-up’. Integration is really important in modern enterprises because they have lots of applications and endpoints that need to communicate with each other. I believe exciting times are coming for Integration people.

Mahesh: Any thoughts on cloud?
Glenn: Simple: Azure is awesome! :)

Mahesh: What motivates you to do the community work?
Glenn: I like learning about new technologies and play with them to build small demos or POC’s.  Because it’s a shame to let them sit there with no purpose I often share this with the community by writing a blogpost or giving a talk on that subject. I think it’s a combination of staying on the edge of technology and share those experiences with other people and try to create some sort of interaction.

Mahesh: Being MVP, do you feel that responsibilities get added? What is your thought on MVP?
Glenn: I see it more as opportunities rather than responsibilities. I’m really excited about the MVP Program because it allows me to interact on a regular basic with different Product Groups. It also provides me with the chances to test a product or service before it reaches the general audience.
Next to that, due to the MVP program I got to know lots of new people and experienced some unforgettable moments with them.

Mahesh: As per the Roadmap provided by Microsoft,LogicApps can be run on-premise in addition to Azure.Do you think Azure Stack Logic Apps on prem will supersede BizTalk Server?
Glenn: In its current state Logic Apps will not replace BizTalk, it is a product that is currently being worked on and is growing fast. I feel there is a big drive behind Logic Apps both from the community as the Product Group! They really take into account feedback and go back to the drawing board with it.
I’m not a visionary, but we all know BizTalk is a robust product and will be hard to replace.  But I believe with the proper investments and the combination of different services in Azure (Logic Apps, Service Bus, API Aps,…) Logic Apps will be something to watch.

Thanks a lot Glenn for sharing your insights and experiences, this will surely benefit many !!!

Feel Free to ask questions to Glenn in the comments!!!!!!!!

Related Post:

Friday, February 19, 2016

Begineer to BizTalk Expert : Interview with Greg Forsythe

Welcome to Eighteenth interview of the series, today's expert is Greg Forsythe.

Let's begin the Interview.....

Mahesh: Who are you and what you do?
Greg: My name is Greg Forsythe, I was born in New Zealand and returned here 20 years ago after a decade of travelling the world. I am married and the father of two adult children. I have worked in IT for 30+ years and seen a lot of change. I love the challenge of learning new things and tend to learn by doing, and am always downloading the latest beta products, SDKs and trying out the Azure previews.

Mahesh: When did you start working on BizTalk?
Greg: My introduction to BizTalk was in 1999, with the beta of BizTalk 2000. Not a lot of good things were ever written about BizTalk 2000 or its successor BizTalk 2002 and with good reason. I was again involved in the beta of BizTalk 2004 which embraced the new .NET technologies and was a vast improvement on its predecessor. I have used every version since and am continuing to learn. 

Mahesh: How did you master BizTalk (Learning path, amount of time)?
Greg: Most of the knowledge I have gained with BizTalk is from experience - working out how to solve problems. There are a lot of smart people out there who have come up with interesting solutions to problems they have encountered. These people have probably been my best teachers. Remember Google can be your best friend. 

Mahesh: Which are the major projects you handled so far?
Greg: I have worked on quite a few BizTalk projects in the last 15 years. From retail chains, telecoms, banking and finance, insurance and more recently education and health care. One of my favourites was in health insurance building a web site interface for contracted providers. We used a combination BizTalk and pure WCF services all secured using SAML. This was done just before WIF was released so we had to build our own SAML token server and we learnt a lot of lessons on the way. 

Mahesh: How do you see BizTalk compare to other integration platform?
Greg: I don’t have a lot of experience with other integration platforms. Have been involved in projects where we had to integrate with WebSphere from IBM, and SeeBeyond/JCAPS/Oracle SOA Suite. More recently MuleSoft is making big gains in the integration space and this looks like a good product. All of these products were capable of producing the results and the choice of platform came down to non-technical decisions such as existing commercial relationships, costs of licensing and training. 
BizTalk found a niche because of competitive licensing and a lot of companies running Microsoft infrastructure and a large pool of .Net developers.

Mahesh: What as per you is must to know to become an Integration(BizTalk) Expert?
Greg: The key with integration is learning the patterns. Technology is ever changing but the patterns are more constant. We have moved from XML/SOAP web services to REST and JSON. From less than 100 integration points to millions with mobile and billions with IoT. But the basic patterns are still the same.
Another key skill is knowing when not to use BizTalk, i.e. when you have a hammer everything looks like a nail. I have worked on BizTalk solutions much better suited to SSIS and others where every single web service goes thru BizTalk, even a simple query for values to put in a dropdown list. Implementing solutions on integration servers can be expensive both in development and resource costs. Use BizTalk for solutions where it will add value.

Mahesh: What are your thoughts on forums, blogs and articles etc.?
Greg: These are an invaluable resource. Chances are someone else has tried to do something similar to what you need and struggled for a solution and posted a question. Post questions yourself if you cannot find an answer, there are a lot of people that may be able to give you an answer.
I used forums as a learning device, trying to discover the answer to questions. I have a lot of BizTalk projects created to test possible solutions to people’s problems. Someone else may come up with a better solution, but this is just another opportunity to learn.

Mahesh: Your suggestion to a newcomer? What should be approach to get sound knowledge in BizTalk?
Greg: I guess the first step is becoming familiar with the product and the tools. Get a VM and install BizTalk, SQL and Visual Studio. This can sometimes be a bit of a mission, but I can almost guarantee someone has hit whatever problems you will have and has solved it and written it down in a blog post or forum answer. I tend to learn far more from failure than success.
Go to MSDN and look for BizTalk tutorials. Have a play at creating and deploying a solution. Go to the forums and see if you can solve someone’s problem.

Mahesh: There are many tools from community which support BizTalk in some or the other way (like BTDF, Bizunit, etc.), what do you say about it? Which ones you would recommend? Why?
Greg: There are a lot of open source resources for BizTalk, some good and some not so good. One issue with open source solutions is the time and energy required to maintain and improve them. Some tools offer great promise but fail to deliver their full potential due to lack of resources. 
I would urge people to get involved. As well as contributing to the community you will also learn a lot about BizTalk. The more you know about how BizTalk works, the better your solutions will be.

Mahesh: What are your thoughts around BizTalk certification?
Greg: I am in two minds about certification, not just with BizTalk.  Having a certification shows a degree of commitment, however being able to study and pass an exam is not nearly as good as experience. And this is the catch-22 for beginners, maybe getting involved in the community is the answer. I would be more impressed by someone putting open source contributor on their CV than a certificate, but both would be better.

Mahesh: What is the future of BizTalk?
Greg: BizTalk as a product, definitely has a limited life span.  But in saying that BizTalk will be around for a long time to come. Most IT departments are unable discard one technology for another very quickly. Just consider flat files and FTP. These technologies have been around forever but are still the staple of many integrations.
The basic concepts of integrating systems and processes will remain the same. Anyone working in BizTalk will find most of their skills will apply to the next set of tools. What does an adapter do? How does a pub/sub engine work? How do you correlate asynchronous processes? What is the best model for scaling your application?

Mahesh; Any thoughts on cloud?
Greg: The cloud is the future. It is not just a matter of renting a virtual machine in someone else’s data centre. It is the tools and services that back up the cloud that make the difference. A common tool set that comes with the platform that you do not have to invent yourself. How to deploy and scale applications. How to monitor and diagnose problems. 
The imminent release of Azure Stack will make these technologies ubiquitous. Soon people will wonder how they managed to build applications without these tools.

Mahesh: What motivates you to do the community work?
Greg: I guess it is a combination of factors. The desire to help others, the chance to learn new things and I guess there is also some ego involved as well.

Mahesh: You have been MVP, do you feel that responsibilities get added? What is your thought on MVP?
Greg: Being and MVP was a privilege. I did not feel any extra responsibilities were added and there were some definite advantages to being an MVP. 

Mahesh: As per the Roadmap provided by Microsoft, LogicApps can be run on-premise in addition to Azure. Do you think Azure Stack Logic Apps on premise will supersede BizTalk Server?
Greg: Logic apps are not a complete replacement for BizTalk. However, in combination with the Service Bus and Web apps will one day provide a better tool set than BizTalk. I would expect the Azure integration tools both locally with Azure Stack and in the cloud will replace the need to use BizTalk. 
However, don’t be too hasty. Logic apps are still a work in progress. And while their list of API’s is growing fast there are still a few areas where BizTalk is currently superior. I suspect this will not remain this way for long as Microsoft continues to invest heavily in Azure.

Thanks a lot Greg for sharing your insights and experiences, this will surely benefit many !!!

Feel Free to ask questions to Greg in the comments!!!!!!!!

Related Post:

Monday, February 1, 2016

Specify a valid .NET type name for this root node.The current .NET type of this root node is invalid

In current project I have to work on papiNet schema, an opensource schema used for paper industry, this schemas for it can be downloaded here . 

To start with, I created a project in visual studio and added PurchaseOrderV2R40 schema to it (which I downloaded from link mentioned above). To make sure all is ok with schema, I build the project and was encountered with errors for few nodes

"Specify a valid .NET type name for this root node.The current .NET type of this root node is invalid(it is reserved BizTalk Keyword or is an invalid C# identifier)"

as can be seen in below image.

Why it happened:

The errors say that few mentioned nodes does not have valid .NET type name - it refers to RootNode TypeName property. As can be seen in image(marked in yellow), there is hyphen(-) used in RootNode TypeName and that is not allowed.

What to do:

As hypen is not allowed, I removed it  from all nodes having it and build the project -- all the errors were gone.

Note: I am not sure what implication will it have as the project progresses, I think there won't be any problem but if any then will update

Friday, January 29, 2016

ESB Portal Error Information

Upon completion with ESB installation and configuration, did build the ESB.Portal project and running the Management_Install command, thought of having look at ESB portal but following is what I got :(

Nothing substantial, so checked event log as notified

Why it happened:

Aah ! I missed to install Reportviewer which is required.

What to do:

Download and install Microsoft Report Viewer Redistributable 2008  

After installing Report viewer, ESB portal was all good .

Note: Other considerations while configuring ESB Portal

1. Download and install Enterprise Library 5.0
2. Open ESB.Portal.sln found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
3.In the Solution Explorer add Microsoft.Practices.ServiceLocation.dll as a reference to the ESB.BAM.Service.Implementation project. This assembly is found in C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
4. Save all files in the solution and Rebuild ESB.Portal project.
5. Close Visual Studio and Run Management_Install.cmd file found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts

Wednesday, January 13, 2016

Begineer to BizTalk Expert : Interview with Bill Chesnut

Welcome to Seventeenth interview of the series, today's expert is Bill Chesnut.

He is Principal Consultant for Mexia Consulting based in Melbourne Australia. He started his career in IT in 1983 and have worked on numerous enterprise projects using Microsoft C/C++, Visual Basic and SQL Server. Most recently, he have been working on various application integration projects using C#, VB.NET, ASP.NET, XML, XSLT, SQL Server and BizTalk Server to connect a variety of Microsoft Business Solutions applications with other systems. He have been awarded a Microsoft MVP for BizTalk Server since 2004 for my community involvement in the Australian BizTalk User Community.He is very involved in the Microsoft User Group Community and have been a past leader of the Melbourne .Net User Group and worked closely with Microsoft to start a BizTalk User group in Melbourne and am now an active participant in both the Melbourne Azure group and the Brisbane Azure group. He is also a member for the Microsoft VTSP program for BizTalk.

Let's Begin the Interview

Mahesh: Who are you and what you do?
Bill: Bill Chesnut, Principal Consultant for Mexia, based in Melbourne, Australia
Was born in Cincinnati, Ohio, grew up in Berea, Kentucky, immigrated to Melbourne, Australia in 2000

Mahesh: When did you start working on BizTalk?
Bill: I started working with BizTalk 2000 in early 2001, while I was working for a Great Plains Dynamic reseller in Melbourne, Australia, we were working with Dan Murphy’s liqueur retails based in Melbourne, they were switching POS systems and needed a way to get transaction from the POS system into Great Plains, I had been reading some Microsoft information about BizTalk 2000 and thought it would be a good fit, we did a small POC and decided it would work.  We hit lots of challenges with BizTalk 2000 and ending up writing heaps of code and using MSMQ to single thread some of the message flow, but the project was a success and was used by Dan Murphy’s until they replaced Great Plains with SAP a few years ago.

Mahesh: How did you mastered BizTalk (Learning path, amount of time)?
Bill: The Great Plains Dynamics Reseller I was working for was purchased by a bigger company and I decided to join Readify (at that time called Monash.Net), a Microsoft .Net consultancy and training provider.  The 1st week I was there Microsoft call the owner and ask us to send someone to Redmond for the BizTalk 2004 ascend training and then return to Australia and go around the country and train all the partners in BizTalk 2004, the boss asked everyone if they knew anything about BizTalk and I was the only one that even knew what it was so off to Redmond I went.  I brought the ascend training material back to Australia and went around the country to train as many Microsoft Partner on BizTalk 2004, I also started up a BizTalk User Group and began doing presentation about the different features of BizTalk.  My mastery of BizTalk came by answering people’s question during the training with many late nights trying out my ideas.

Mahesh: Which are the major projects you handled so far?
Bill: Most of the BizTalk project in Australia are on a much smaller scale than those in the US or Europe, most of the project are at most 2 Enterprise BizTalk server for failover and the rest are single Standard Edition BizTalk.  Also working for Readify for just over 4 years, we did mostly mentoring and training, so I was not really part of any large project teams.  I then became Practice lead at Stargate Group and again, the majority of our BizTalk projects were on the small size but integrated with some of our other products and a bit of BizTalk training.  I then joined Mexia in 2011 and most of my work has been overseeing the technical side of our larger BizTalk project but again not directly working on the actual coding parts of the project and also doing some BizTalk training for our clients. 

Mahesh: How do you see BizTalk compare to other integration platform?
Bill: I have really only worked with the Microsoft stack since 1994, and to compare SQL DTS/SSIS to BizTalk would be a bit of a stretch.  I have been involved in some competitive tender processes around integration platforms and in the Australian marked, the big plus for BizTalk is it cost and the fact that is .Net and Visual Studio based.  I still believe that is its strongest features in the market and its best feature is that it works and typically just runs without much care and feeding.

Mahesh: What as per you is must to know to become an Integration(BizTalk) Expert?
Bill: I guess the thing I look for in an Integration Expert is someone that understand integration, from my training it has always been easier to teach someone that understands integration BizTalk than to teach a web or windows developer to thing in a message oriented way.

Mahesh: What are your thoughts on forums,blogs and articles etc.?
Bill: There is a lot of information about BizTalk out there now, but when I started the blog posts and forums were pretty scarce, but I guess the biggest issue I see today with the forums and blogs it that lots of the information is wrong or people recommend dropping into .Net instead of doing things the BizTalk way, which can cloud the picture for new people starting in BizTalk.

Mahesh: Your suggestion to a newcomers?
Bill: Make sure you are strong in the .Net technologies; BizTalk talk it not the answer to all the integration problems, spend time understanding integrations and messaging, BizTalk is a tool, if your though process is not integration focused no tool will solve your problems.

Mahesh: What should be approach to get sound knowledge in BizTalk?
Bill: You have to work with the product, there is no quick way to become an expert except working with the product, spend time on the forums, when you don’t know the answer spend time trying to solve the problem.  Send as much time as you can reading blog posts and articles, but realise that everything you read is not the best way, spend time trying other ways to solve the problem, because there is always multiple way to solve any problem.

Mahesh: There are many tools from community which support BizTalk in some or the other way(like BTDF, Bizunit etc), what do you say about it?
Bill: I have not typically used many of the community tools, recently I have been using BTDF heavily as part of an automated build and deployment for BizTalk solutions, there are thing I like about it and thing I wish they would fix.  I have also used BizUnit a bit, but recently using SpecFlow more for BizTalk integration testing.  I tend to use more code snippets and samples I find on the internet than a complete tool.

Mahesh: Which ones you would recommend?Why?
Bill: BTDF – it simplifies the build and deployment of BizTalk solutions in most cases and it works well with tools like TFS, VSTS, TeamCity and Octopus Deploy.

Mahesh: What are your thoughts around BizTalk certification?
Bill: There is a big hole in both BizTalk training and certification at the moment, the core BizTalk product has not changed that much in the recent years and Microsoft has not spent any money on either one recently, the only current certification for BizTalk is part of the Microsoft partner program and it fairly simplistic at best.  With BizTalk training, Quicklearn has excellent training material and trainers, but their business model just does not fit in the Australian market, people still want someone standing in front of them delivering the training.

Mahesh: What is the future of BizTalk?
Bill: Well, this is a good question, BizTalk’s death has been written about several times in the past, but it is still alive and kicking and I expect it to be for many years to come, but the move to the cloud is accelerating and even some of Mexia’s recently BizTalk Server projects are running the BizTalk infrastructure in Azure Virtual machines, because it is cheaper and easier to setup and manage.  I am very interested in what new features with be in BizTalk 2016 in relation to how it will interact better with the new Azure Logic Apps and the rest of the Azure stack.

Mahesh: Any thoughts on cloud?
Bill: It is here to stay and if you are not looking at using it for part of your integration strategy then you are doing your company and or clients a big disservice.  I believe that 2016 will be a big year for Integration with BizTalk 2016 and Logic Apps.

Mahesh: What motivates you to do the community work?
Bill:I guess my background as a trainer, makes me eager to help people learn about technology, I was involved in the Melbourne .Net User group when .Net 1.0 was still in beta and have been eager to help people continue in the .Net, Azure and BizTalk learning with all the new releases.  I have also always had employers that were very supportive of my community work.

Mahesh: Being MVP, do you feel that responsibilities get added?
Bill: Yes, I do, I think the nature of an MVP is someone that is eager to help other with their chosen technology.  And that MVP need to be leaders in both their local communities and in the wider country and world communities, so for most MVP spare time is something that we all can remember having before we became MVPs.

Mahesh: What is your thought on MVP?
Bill: The MVP program is a great program, it has given me that extra connection to the Microsoft Product team that has both helped shape the BizTalk product and helped me do a better job delivering high quality BizTalk and Azure solution to our company and clients.  I have just been renewed from the 13th year and have been a BizTalk MVP, Microsoft Integration MVP and now an Azure MVP, but nothing has really changed about my Integration focus.  I do believe that the condensing of lots of the MVP specialties into a few is a good thing, I was already doing heaps of stuff in the community around Azure and I am now an Azure MVP.

Mahesh: As per the Roadmap provided by Microsoft,LogicApps can be run on-premise in addition to Azure.Do you think Azure Stack Logic Apps on prem will supersede BizTalk Server?
Bill: I think eventually it might, but not in the near term, there are still heaps of things that BizTalk is the only way to do, but I think it is only a matter of time until they add those capabilities to Azure and Azure Stack. I think the Azure Stack will make BizTalk Dev and Test much easier for those company that are not able to move to the cloud currently because of security and privacy reasons.

Thanks a lot Bill for sharing your insights and experiences, this will surely benefit many !!!

Feel Free to ask questions to Bill in the comments!!!!!!!!

Related Post:

Monday, January 4, 2016

This client is not supported for a partitioned entity

Scenario is simple, to send file which is on Prem using SB Messaging adapter to Azure service bus queue and for that I created a queue using Azure portal under my ServiceBus namespace using the Quick Create option.

Created a simple messaging application in Admin console with a receive location and a send port configured with SB adapter and properties pertaining to the queue which I created using the Azure portal.

Got above error while sending message to Azure Service Bus queue. 

Why it happened

As mentioned in error "This client is not supported for a partitioned entity" , the destination is a partitioned entity -- the Queue and communication to this queue is not supported for client (BizTalk SB adapter).

Whenever you create a queue using Quick Create option, the created queue will have partitioning enabled by default, so you can't send messages to those queue from BizTalk as of now.

What to do

You need to create a queue which does not have partitioning enabled on it, but we don't have provision to do this with Quick create option so we need to use Custom create option.

Above three properties are also available when we use Quick Create option, but you don't see second page i.e., Configure Queue. It is only visible when we choose Custom create option

And as can be seen in above snap, Enable Partitioning property is checked by default, so I unchecked it and continued.

After the new queue was created , I configured the send port as per new queue and tried sending message again, and yes it was successful.

Friday, January 1, 2016

A connection attempt failed because the connected party did not properly respond after a period of time

Faced Could Not connect error...... while sending message to Service Bus Queue from BizTalk 2013 R2

So in order to debug it, tried sending test message to the queue using Server Explorer, but it wasn't successful -- network delay.

As per the error text Could not connect to net.tcp:// , it appears that BizTalk SB adapter uses an outbound connection and works only over TCP port 9351-9354. I checked the outbound rules and there was no such port, so to fix this i tried with creating new outbound rule and enabled the port 

But still error persist, upon looking on some blogs it is said installing Azure SDK 2.8.1 will solve the problem --- did installed and restarted the host instances  but still error persists.

 But error still  persisted.

Upon suggestion from fellow MVP Michael Stephenson, I tried from home and bingo --- it worked. Message was successfully delivered to Service Bus Queue.

Why it happened

BizTalk SB adapter uses an outbound connection and works only over TCP port 9351-9354 so this ports should be enabled. But, I had enabled it still there was error, why? It is because I had enabled the port on Local Server but it was blocked  on Network Level.

What to do

If you are in private network then enable the ports on Local machine but if you are at workplace then check with your network team to enable those port .