Haja’s Blog

I got the following error after successful deployment of assemblies in BizTalk. I have BizTalk installed in federated (distributed) way. 4 BizTalk servers associated with same deployment and I have to install orchestration assembly in one server and gac it all other servers. After installing and gacing when it starts processing I encountered unique and weird problem. Some time my orchestration picks up message and some other time throws following error.
Failed while creating a XyZ.Orchestration service.       
Exception type: ServiceCreationException
Source:
Target Site:
Help Link:
Additional error information:
 
File or assembly name XyZ.Orchestration, or one of its dependencies, was not found.
       
Exception type: FileNotFoundException
Source: mscorlib
Target Site: System.Type GetType(System.String, Boolean)
Help Link:
Additional error information:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
When I checked the installation logs there was no error and also checked whether the orchestration was present in the gac on all the servers and it was there.
So there is something must happened the way it was installed which made BizTalk engine to run the orchestration on and off mode. 
And finally it got resolved; below you can find what I did to resolve it.
1. If you encounter the problem like above check all the servers have the assembly gaced.
2. If not gac the dlls in all the server and install the assembly in one server (either by deployment wizard or scripts).
3. Most important thing you should do always is restart the host service for the orchestration in all the servers

List of things I like to see in joost

1. Better visual clue to resize and position the window.
2. More channels and programmes.
3. User interface elements in a fixed postion, than appearing and disappearing.

Things which i liked

1. Nice search feature, to search for your favorite programmes.
2. Stunning video quality, even after making the window size bigger.
3. Flicker free resizing.
4. My Joost customization with many widgets (like weather, news ticker, clock, instant messaging - you can share what you are watching with your IM buddies.) etc.

joost_UI, originally uploaded by haja_maideen_m.

I tried joost from my office, it didnt work, got network error, may not work under firewalls? Not sure. Screen shot of main UI below.

Another way to reach this blog. Search for the term “Haja” or “Hajamaideen” in Google or yahoo, I managed to get this blog listed in first page of search engine results. Little bit of SEO (Search engine optimization) which I did long back is paying of now. 

After a month long wait I got invitation to participate in ‘Joost’ (Formerly ‘the Venice Project’) beta testing. Brief background info: Joost is yet to be released video tool which promises to revolutionize online video viewing and probably may replace TV!!!    I just downloaded the beta version and planning to post my opinion / review about the product in coming days/weeks/months!!!!. Stay tuned.   

I ran into weird issue in BizTalk 2004 mapper when I am trying to implement nested looping using loop functoids, but at the end I got single ‘for-each’ xslt output instead of nested ‘for-each’ for 3 functoids which used. This is what I did.
1. I got to loop 3 elements which nested inside.
2. I drag and dropped 3 functoid to designer surface.
3. Connected top most parent element to first functoid and then connected corresponding destination element.
4. Repeated step 3 for next child element and then inner most child element.
5. When I validated the Map i got only one for each xslt output for the top most parent element. This depicted in the following map picture.
 

What is going wrong in this? I believe there is bug (or may be it suppose to work this way, which don’t know) the order in which you connect elements source node -> looping functoid -> destination nodes.
If you follow the steps as shown above you may not get nested loop (which is expected result). So follow the following steps.
1. Drag and drop all functoids to the designer surface.
2. Start connecting innermost element from source schema to functoid and then to destination node.
3. Repeat the step 2 for element or node which need to be loop(ed) above the innermost element as shown below

So, moral of the story is, start your looping functoid connection from innermost node and repeat the step for upper nodes.