Saturday, July 19, 2014

Could Not load file or assembly "Microsoft.BizTalk.Scheduler" or one of its dependencies

While working on the Scheduler POC for the article BizTalk Server : Scheduling Orchestration using Trigger Message, received below error while deploying the application using the visual studio.

Why it happened:  It happened because Microsoft.BizTalk.Scheduler  assembly which is used by Scheduled Task Adapter was missing in the GAC .

What to do :
·         Open BizTalk administration console
·         Right click on application "BizTalk Application 1"  (The shared application in which assemblies related to scheduled Task Adapter is installed)
·         Select Add | BizTalk Assemblies
·         Click the Add button
·         Browse and select C:\Program Files (x86)\Microsoft BizTalk Server 2013\Microsoft.BizTalk.Scheduler.DLL
·         Click Open
·         Check on Overwrite all
·         Check on:
·         “Add to the global assembly cache on add resource (gacutil)”
·         “Add to the global assembly cache on MSI import (gacutil)”
·         “Add to the global assembly cache on MSI file install (gacutil)”

             Click OK

Friday, July 4, 2014

Interview questions on HL7

This post intends to cover the BizTalk HL7 related questions, which a BizTalk developer can face during an interview.

1.What happens when HL7 accelerator is installed?

2. What does BTAHL72VXCommon project contains?

3. What does BTAHL7231common project contains?

4. Is it mandatory to configure party for HL7?

5.Is it required to specify schema per pepiline?

6.What consideration is to be taken while dealing with MSH entries?

7.When does DASM generates acknowledgemets?

8.Why is it required to have party configured?

9.HL7 accelerator runs in which mode?

10.Can we override values in the MSH segment of the outgoing message?

11.Can we alter the namespace in the MSH schema?

12. What is difference between BTAHL72XReceive and BTAHL7XMLReceive?

13. What are the acknowledgement types in HL7?

For answers please have look at following article:
BizTalk Developer Interview Questions and Answers - HL7

Wednesday, July 2, 2014

Begineer to BizTalk Expert : Interview with Steef-Jan Wiggers

Starting a blog series where I would be interviewing the BizTalk experts all around the world, the focus will be on getting the insights on how to become expert and what experts did to become expert. Today's BizTalk guru is Steef-Jan Wiggers. Before starting the interview I would like to congratulate Steef on being rewarded MVP award for 5th time in a row(

I met (virtually) Steef through TechNet Wiki last year and it was him, the first person who guided me proactively and helped me improvising the BizTalk articles. And I know, like me, he has guided many new contributors, playing the role of guardian very well. Before that, I was already found of his articles, which demonstrated the amount of knowledge, expertise he has in BizTalk. He is one who has been consistent for many years with the eagerness and desire to serve the community by sharing his knowledge and experience via TechNet Wiki , blogs and forums. Great to have such person in the community.

Lets start the interview....

Mahesh: Who are you and what you do?
Steef: My name is Steef-Jan, married, three children and living in Ede a village near the National Park “The Hoge Veluwe”. As an all-round integration specialist I work on different projects with various customers building integration solutions with Microsoft Technology like .NET (WCF), WF, SQL, and BizTalk Server. My role involves architecting and designing solutions, perform audits, guide installation and configurations of BizTalk environments, development and do consultancy.

Mahesh: When did you start working on BizTalk?
Steef: I started working with BizTalk Server in 2005 as junior BizTalk professional. By then I had six years of .NET development, SQL Server and OS experience. I was a certified MSCD.NET, MCDBA and MCSA 2003. It was not too difficult for me to enroll into BizTalk Server product and technology behind it. I started with installations and configurations of BizTalk 2004. Not an easy task back then. Subsequently I developed my first BizTalk solutions.

Mahesh: How did you master BizTalk (Learning path)?
Steef: The learning path can be different from person to person. I myself already had a vast experience with Visual Studio, SQL Server, XML, and XSD’s and so on. Therefore, I could focus on learning the product itself and gain experience by doing projects. I believe the best way to master BizTalk is by experience. The way you can approach this is by reading one of my TechNet Wiki articles named: BizTalk Server 2013: Beginners Guide. I did the write up so others can use that approach it that suits them.

Mahesh: Which are the major projects you handled so far?
Steef: During the last couple of years I have done various large BizTalk projects for global and local operating customers in verticals like retail, telecom, energy, and insurance. In those projects the challenging aspects are deployment and operations not the development.

Mahesh: How do you see BizTalk compare to other integration platform?                              
Steef: BizTalk is the best choice as an integration platform in a heterogeneous environment. The choice for BizTalk is platform depended. Therefore, in a predominantly Microsoft environment BizTalk is the logical choice and challenging to compare with other products. I feel Gartner does a better job of comparing integration platforms than we as BizTalk professionals.

Mahesh: What as per you is must to know to become an Integration (BizTalk) Expert?
Steef: I have a passion for technology and BizTalk in particular. I started working with the products in 2005, and after a year I decided to share my experience and knowledge through a blog. I started blogging on, where I created a blog called “SOA Thoughts, EAI Challenges”. SOA was a hot topic at that moment and Microsoft organized conferences like SOA & BPM, where BizTalk was featured as Microsoft's offering for SOA and BPM. BizTalk in my view can be a right fit as an enabler for SOA with Microsoft Technology. I visited the last three conferences held at Microsoft Campus in 2006, 2007, and 2009. With every visit I shared my experience through blog posts and with my colleagues. Soon after the first conference in 2006 I started writing articles for Dutch magazines and did presentations, sharing my gained insights to fellow BizTalk professionals.
After writing articles and blogging, I started helping people out in BizTalk forums. In June 2010 I was nominated for MVP and July 1st I was awarded. Filled with joy, excitement, and appreciation, I became even more active on forums, writing more articles, and presenting nationally and internationally for BizTalk User Groups. Being an MVP gave me a boost and more opportunities to share my knowledge and experience with the community. For instance, beginning of this year, PackT publishing gave me the opportunity to review a BizTalk book, and even the opportunity to write one. So I started writing a BizTalk Cookbook and it is due to be released the beginning next year.
The great thing about Microsoft MSDN Forums, Blogs, Code Gallery, and the TechNet Wiki is that you can share your knowledge and experience. Recently, I even started being active on Code Gallery and TechNet Wiki sharing code samples and writing Wiki articles. The general message that's coming from myself is to share your knowledge with passion, dedication, and persistence. At the end of the day you will be appreciated for your efforts, and it can lead to becoming a well-respected community member like an MVP.

Mahesh: What are your thoughts on forums, blogs and articles etc.?
Steef: Forums, blogs, articles, books, sites, and so on are all resources you can access to learn more on BizTalk Server, or help you with building a solution, or can aid in helping to solve an issue you are facing. The number of resources grew substantially on BizTalk the last couple of years. When I started with BizTalk Server there not as much of the resources as there are today. These resources play in my view a vital role in the success of BizTalk Server today.

Mahesh: Your suggestion to a newcomers? What should be the approach to have a sound knowledge in BizTalk?
Steef: I would suggest to read my TechNet Wiki articles named: BizTalk Server 2013: Beginners Guide.

Mahesh: What are your thoughts around BizTalk certification?
Steef: Certification is a means of showing your knowledge of the product towards customers. However, certification alone will not tell how skillful you are. A better indicator for that is experience, the number of projects and endorsements from peers.

Mahesh: What is the future of BizTalk?
Steef: The product, BizTalk Server is still standing strong and Microsoft will be investing in now with the upcoming release and beyond that. Besides BizTalk Microsoft is putting tremendous effort in its cloud counterpart Microsoft Azure BizTalk Service. My prediction is that in some point of time there will be a convergence between the on premise BizTalk Server and Microsoft Azure BizTalk Server. This means there will be a kind of symmetry between both of them, where you build your solution and deploy it either on premise or in Azure.

Thanks a lot Steef, am sure many of us will be benefited from your insights and your journey is inspiring !!!!!!

Wednesday, June 11, 2014

This schema has the same type name as its namespace

After installing BizTalk 2013, just to check I started to create a project with name as Test. Then added a schema named Test with Root tag named as Test and two elements. Signed the project and tried to build it and following error appeared.

To find out the problem,  I went through the properties of the schema and found that Namespace and Type name is same. Well I don’t  the exact reason but it seems having same namespace and type name causes ambiguity in resolution. 

Why it happened:  Namespace (Project Name) and Type Name (Schema name) were same
What to do : Rename the schema and Type Name Or delete the schema and create new schema with name different than that of Project Name.

Tuesday, June 10, 2014

Error 1309 : Error reading from file

While installing BizTalk 2013, received below error.  As per error there was some error while reading the file.

So first thing was to check whether the file mentioned in error existed or not and secondly whether it was accessible. To check this I traversed the whole path, and file was there. Next I right clicked on the file and tried opening it  and below error popped out.

While extracting , I kept the name same as that of the image(ISO) file i.e. en_biztalk_server_2013_developer_edition_x86_x64_dvd_319207  and that was the problem.  So I renamed the folder name as “Biz” and then tried installing again and it was done.

Why it happened: The path length exceeded the threshold.

What to do : Reduce the length of the path by renaming the initial folder name. 

Friday, May 9, 2014

Exception From HResult:0x80070005(E_ACCESSDENIED)

Received below errors today when I tried deploying the BizTalk HL7 solution:

Why it happened: When we deploy BizTalk solution it makes entries in management database and GAC. Both Management database and GAC requires Admin rights to make any change in it (adding and removing assemblies).

What to do: Open the visual studio with Admin rights. Right click on the Visual Studio and Select "Run as Administrator" and then open the project you want to deploy.

Monday, May 5, 2014

(MCTS): Microsoft BizTalk Server 2010 (70-595) Certification Guide (second edition) book review

I got an opportunity to review the book - Microsoft BizTalk erver 2010 Certification Guide, and below is what I feel about the book.

As per the guidelines/information published on the Microsoft site (, the authors have done good job of dividing them in 8 chapters and sequencing them like the path we take while learning the technology and using it (the first six chapters), i.e. fundamentals first, understanding the building blocks/components , developing using the components, testing and handling
exceptions, deploying and managing. Seventh and Eight chapter is focused on the WCF and Extended components which are used to extend the capabilities of BizTalk solution (RFID is missing - but I guess that's ok).

Chapter 9 is not required for BizTalk 2010 certification, but yes it's an add on and should be useful for those going for BizTalk 2013 Technical assessment.

The authors have done great job by including the images wherever there was need and tips (with a bulb - the key points). No guide will be useful if it only says how to do without any evidence, there are sample codes as well which shows how the concepts are implemented/applied.

Although people going for certification (should) have 1-2 years minimum experience, it's rarely possible that he had worked on all areas. Considering that,this book tries to cover each and every part and have provided a dedicated chapter for guidance on how to cover all areas, how to prepare and how to appear in exam - chapter 10.

Just going through book and code is not enough, net practice is important before actual match. A dedicated section after every chapter "Testing your knowledge" is there for practice .

All in all a good Guide, have it with you and practice as much as possible !!!

Sunday, April 6, 2014

Error happened in body during parsing

For testing the HL7 tutorial sample , I picked sample message from following link:

PID|||191919^^^MYHOS^MR~123-45-6789^^^USSSA^SS|253763|SMITH^JOHN^Q||19560129|M|||    123MAIN^^BUFFALO^NY^98052^""||(123)555-0100||S|M|10199925^^^MYHOS^AN|123-45-6789
PD1|S|F|NormalString^A^+1^-1^ISO^simpletext&Test&HCD^GI^simpletext&NormalString&ISO^I|   NormalString^Test&Test^Test^Test^Test^Test^AE^simpletext^simpletext&Test&ISO^P   ^NormalString^M10^MC^simpletext&NormalString&HCD^A|N|simpletext|I|I|N|NormalString   ^+1^M11^simpletext&NormalString&L,M,N^RRI^simpletext&NormalString&HCD|NOVALUE^NormalString   ^Test^Test^NormalString^Test|N

Error 3: Error happened in body during parsing
Error # 1
Segment Id: PD1
Sequence Number: 1
Field Number: 4
Error Number: 103
Error Description: Table value not found
Encoding System: HL70200

Error3.1: Message had parse errors, can not be serialized

Why It happened : It happened because there were space between the fields in the PD1 segment.

What to do : Remove the spaces in between the data

Tuesday, April 1, 2014

Awarded as Microsoft Integration MVP 2014 by Microsoft

Yesterday  it was Gudi Padwa (New Year) and today received a mail "Congratulations April 2014 MVP Award Winners" from Microsoft. What a start of the year. It feels great to get recognized for the job which you like to do most (helping others and sharing knowledge).

I would like to thank all the community members who share their knowledge and for the guidance  and congrats to the other community members who are also awarded as MVP along with me.

Apart from community there are many other people who I would like to thanks, like family members, my colleagues and friends who were the motivators and supportive in this journey which I started Last year .

Thanks to all .... Looking forward to learn from community and give it back what I know !!!!!!!!!

Reference :


Thursday, March 27, 2014

Error: Error in the application

Error: Error in the application

It was when I used BTAHL7SendPipeline on the send port to transmit HL7 file.

1. A message sent to adapter "FILE" on send port "Tutorial_BTAHL7Drop" with URI "C:\Users\tiwarmah\AppData\Local\Temp\%MessageID%.txt" is suspended.
 Error details: There was a failure executing the send pipeline: "BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "BTAHL7 2.X Assembler" Send Port: "Tutorial_BTAHL7Drop" URI: "C:\Users\tiwarmah\AppData\Local\Temp\%MessageID%.txt" Reason: Error in the application. 
 MessageId:  {51D8E0DB-A23A-47CD-A6FD-319AFCC1B25C}
 InstanceID: {53E75E07-D0E1-4F88-B7A9-6B8701F4A397}

2.There was a failure executing the send pipeline: "BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "BTAHL7 2.X Assembler" Send Port: "Tutorial_BTAHL7Drop" URI: "C:\Users\tiwarmah\AppData\Local\Temp\%MessageID%.txt" Reason: Error in the application

Why it happened: It is a bug in BTAHL7 Assembler, Microsoft has resolved this bug and have provided hotfixes for it.

What to do : To fix  Install the cummulative packages

KB Article Number(s): 2838133
Language: English
Platform: i386
Location: (

KB Article Number(s): 2892599
Language: English
Platform: i386
Location: (