by community-syndication | Jun 10, 2006 | BizTalk Community Blogs via Syndication
I got the following warning messages when building a BizTalk project.
—— Build started: Project: BizTalkApp, Configuration: Development .NET ——
Updating references…
The dependency ‘Microsoft.BizTalk.Tracing’ could not be found.
The dependency ‘Microsoft.BizTalk.Bam.EventObservation’ could not be found.
The dependency ‘Microsoft.BizTalk.Streaming’ could not be found.
The dependency ‘Microsoft.BizTalk.XPathReader’ could not be found.
Performing main compilation…
I think these warning messages are no harm at runtime. But, they may annoy. The BizTalk project had a reference to a pipeline component project using some BizTalk related components such as Microsoft.BizTalk.Pipeline.dll.
To suppress these warning messages, you can select “False” for the “Copy Local” property of the referenced pipeline project in the BizTalk project. After then, they will be gone.
by community-syndication | Jun 10, 2006 | BizTalk Community Blogs via Syndication
I got the following warning messages when building a BizTalk project.
—— Build started: Project: BizTalkApp, Configuration: Development .NET ——
Updating references…
The dependency ‘Microsoft.BizTalk.Tracing’ could not be found.
The dependency ‘Microsoft.BizTalk.Bam.EventObservation’ could not be found.
The dependency ‘Microsoft.BizTalk.Streaming’ could not be found.
The dependency ‘Microsoft.BizTalk.XPathReader’ could not be found.
Performing main compilation…
I think these warning messages are no harm at runtime. But, they may annoy. The BizTalk project had a reference to a pipeline component project using some BizTalk related components such as Microsoft.BizTalk.Pipeline.dll.
To suppress these warning messages, you can select “False” for the “Copy Local” property of the referenced pipeline project in the BizTalk project. After then, they will be gone.
by community-syndication | Jun 10, 2006 | BizTalk Community Blogs via Syndication
Here’s a post from Somasegar about WinFX being renamed to .NET Framework 3.0. Seems to make sense to keep the same naming going forward, since WCF and WWF are getting confusing enough, I liked Avalon, Longhorn, and Indigo myself.
-B
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
Well we had the most awful time with this the other day. I posted this on the biztalk.general newsgroup but eventually solved the problem myself. Heres what happened.
We had two orchestrations published as webservices. (Using Biztalk 2004 on XP SP2) One was typed and the other untyped (ie) consuming an XmlDocument at the recievePort and assigning it to a specific message variable internally. The untyped one worked fine when called from another orchestration and from an NUnit test. The typed one however always threw a weird error message saying ” Server was unable to process request. –> File or assembly name FileName .dll, or one of its dependencies, was not found.” . We attempted the following
(a) I looked at the support article for the same at http://support.microsoft.com/?kbid=910295 but to no avail. I gave all possible users permissions on all temp folders, but the same message appeared.
(b) Both webservices had anonymous access enabled and i set the ASPNET and Isolated Host users to have permissions to the temp folders and the databases. (I even temporarily let the ASPNET user run as SYSTEM :-)).
(c) I tried adding some code to the asmx.cs to write custom statements to the event log but that didnt work either. It seemed that the web service was just not being called.
(d) found an article which said that Proxy projects that have names more than 61 characters long cannot be compiled (weird huh). But even shortening the names to well below 61 didnt help.
(e) enabled detailed error tracing but this was of no use since the webservice was not being JIT compiled correctly (thats the reason for the weird error message)
Finally we had a breakthrough. We first changed the input operation to accept an untyped message. The system appeared to run for a longer time but returned the same error. While looking at the custom logging files we had setup (using EntLib) it appeared that the orchestration was indeed being invoked by the webservice but the system still threw the exception. Looking at the stack trace we found something about a method which has the word ‘response’ in the name. At that time this didnt ring any bells, but in desperation we changed the return type to XmlDocument and the wretched thing started working!!
It could have just been the response message wasnt being constructed correctly, but all we do now is construct a typed response message and then assign it to an XmlDocument and send it to the response port.
I cant understand it. Typed messages are the bread and butter of Biztalk and untyped messages are not frequently used. So for the system to complain about a typed message is very strange indeed. Anyway, this is a tidbit i thought i’d share in case someone else comes across this problem anytime. Im hoping to find some time later to try and reproduce the problem and do some more detailed debugging. Its a pity that orchestrations are so difficult to debug (even with the orchestration debugger).
Speaking at a user group: I’ve been invited to do an Introduction to Biztalk at the .NET Exchange User Group in London next week. The speaker who was supposed to do this dropped out and as i had volunteered earlier to share my experience with BTS, I’ve been asked to do the honors. Gotta get the old slides polished up and get a demo working.
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
To me this makes alot of sense – good-bye
WinFX
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
A co-worker of mine, Vishal, has posted on GotDotNet a new utility which enables customers to take the archives of their tracking database and stitch them together into a single, large database.
http://www.gotdotnet.com/codegallery/codegallery.aspx?id=67bbd6ea-850e-4d93-be87-df6788976cab
This can be a very usefull tool when used in association with the Archiving and Purging features of BizTalk 2006 which will also be available in BizTalk 2004 SP2. Now you can schedule regular archiving of your tracking database and then reconstruct one single database against which you can mine your data. Thanks to Vishal for putting together this tool for everyone.
For those of you heading to Boston for Tech-ed, drop by the Connected Systems area and say hi. I will be there all week and am doing a co-presentation on Wednesday (my bit is on performance) and have a chalk-talk on Tuesday on Ordered Delivery. Hope to see a lot of you there.
Lee
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
There are a couple upcoming MSDN webcasts coming up that should be interesting to BizTalk architects …
-
Building Modern Software: Services, Workflow, and Identity – Presented by Dave Chappell from TechEd 2006
-
BizTalk Server: Strategy, Deliverables, and Timelines – Just reviewed the deck for this session. Should be interesting.
-
Enabling “People-Ready” Processes Using Microsoft Business Process Management Solutions and Technologies
- [on demand]
Integrating BizTalk Server 2006 and Windows Workflow Foundation
Enjoy.
Technorati Tags: BizTalk
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
This is an addin for Reflector that allows you to list all BizTalk artifacts contained in an assembly and extract them.
Installation
Donwload the attached file and extract Reflector.BizTalkDecompiler.dll into the same directory as Reflector (otherwise it won’t work). Go to View|Add-Ins in Reflector, and Add Reflector.BizTalkDecompiler.dll.
Usage
Using File|Open…, add the BizTalk assembly you’ll like to decompile to Reflector’s assemblies list. Right click on the BizTalk assembly and select…(read more)
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
The other day, I found this entry in the event log:
Event Type: Error
Event Source: BAM EventBus Service
Event Category: None
Event ID: 25
Date: 4/2/2006
Time: 4:16:28 PM
User: N/A
Computer: SERVERNAME
Description:
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQLServer: SERVERNAME\BIZTALK, Database: BAMPrimaryImport.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
TDDS (Tracking Data Decode Service, also known as the BAM Event Bus Service) is responsible for moving data from the MessageBox to the tracking database as well as migrating collected data to the BAMPrimaryImport databases.
It turned out that I had added two additional Hosts with tracking turned on which was not an issue by itself. I then proceeded to create HostInstances and assigned different service accounts for logins. Effectivily, this caused the HostInstances to access SQL under different thread and increased the chances of locking.
Solution:
unchecking the “Allow Host Tracking” option on hosts that use a different service account.
if you need to track all hosts, run all the HostInstances under the same service account.
by community-syndication | Jun 9, 2006 | BizTalk Community Blogs via Syndication
I want to use this space to share my experiences with (in my humble opinion) one of the most under-rated technology Microsoft has ever produced – BizTalk. I hope you’ll find my musing interesting and my tips helpful.
