Monish Nagisetty's Space

Building connectivity on-premise, in the cloud and beyond

Multi-server BizTalk Configuration under a NT4 Domain

I ran into the error below when configuring BizTalk in a multi-server environment (1 SQL Server + 1 BizTalk Server).  It turns out that both servers were members of a NT4 domain.  I discovered that BizTalk does not support NT4 domains.  As stated in the installation document, only Active Directory (AD) domains are supported.

TITLE: Microsoft BizTalk Server 2006 Configuration Wizard


CORP\QABTSServerAdmins is not an valid domain group. (ConfigHelper)




The specified domain either does not exist or could not be contacted. (ConfigHelper)


February 18, 2008 Posted by | Uncategorized | | Leave a comment

The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

Have you ever seen the error below? The error tells you that it cannot find a file but it does not mention the name of the file! In my case, I had a map with a script functoid that referenced an external assembly. It turns out that I copied this map from another project and the assembly reference was no longer valid. I should have encountered build errors but instead I had to deal with this issue at runtime.

Event Type: Error

Event Source: BizTalk Server 2006

Event Category: BizTalk Server 2006

Event ID: 5753

Date: 2/8/2008

Time: 2:24:53 PM

User: N/A

Computer: QSI-BTS06R201


A message received by adapter “FILE” on receive location “RCV.CUST.DATA.FROM.SYSTEM.A” with URI “C:\BTSMessageLogger\File Drops\In\copy*.txt” is suspended.

Error details: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

MessageId: {A916E973-85FB-42B0-83CB-84670D0DDAFF}

InstanceID: {62D1A2A0-9D45-447C-ACD0-17F273E21762}

February 9, 2008 Posted by | BizTalk | | Leave a comment

Visual Studio 2005 Freezes when building BizTalk projects

Have you ever seen VS2005 freeze when building BizTalk projects? I have and it was not a pleasant experience.  In search for a solution back in October last year, I meticulously collected info about my environment and posted it on MSDN Forums.   I just ran into this problem again today and I saw that someone responded to my post with a solution that actually works! Even though the solution is ridiculous it worked for me.  Thank you Hema!

February 8, 2008 Posted by | Uncategorized | , | 1 Comment

BizTalk Assembly Checker Tool

Check out the BizTalk Assembly Checker tool out on codeplex.  I wish I had known about this tool before because it would have saved me some time when doing production deployments with multiple servers.  This tool allows you to verify that your BizTalk assemblies are present on all of your BizTalk servers.  Once you run the verification, you can also copy the assemblies from one BizTalk server to the GAC of all the other BizTalk servers.  This means you only need to login to one of the BizTalk servers when deploying.


February 7, 2008 Posted by | Uncategorized | | 1 Comment

Announcing MOCSDUG (Mid-Ohio Connected Systems Developers User Group)

Drum roll…

I’ve been given the exciting opportunity to start a subgroup under CONDG (Central Ohio .NET Developers Group).  You can read more about the recent updates at CONDG on Steve Harmans’ blog post.  The sub group is named MOCSDUG (pronounced mocks-dug) which stands for Mid-Ohio Connected Systems Developers User Group.  You may wonder why the sub group does not use “Central” for the first word within the acronym.  I will leave that your imagination.

The motivation behind starting MOCSDUG is to raise awareness about specific type of challenges we face today in the Enterprise (note the big E).  Most of members of CONDG are already familiar with the challenges they face when building client/server, smart client, and web applications.  The challenges are not new and we can build manageable solutions using different frameworks and patterns (EntLib, NHibernate, Active Record, Monorail, etc) in our enterprise.

So where does this brings us? We now have 5 or more custom applications each possibly using a different database, framework and language in our Enterprise.  Pretty soon someone will ask you how we can make App A to talk to App B, App C to App A, App D to App A and so on.  One of the first approaches to this problem is to write custom code to integrate each application with another application.  This is called point-to-point integration.  Although this is a reasonable approach within an enterprise that has a handful of apps, it quickly becomes complex and unmanageable.  If you have 5 applications and they all need to talk to each other, the number of points of integration (custom code in each app) will equal to 10.   The formula for this is n*(n-1)/2 where n is the number of apps.  There are multiple solutions available to address the point-to-point problem and you can read all about them at your leisure.

The Integration Problem is central to the challenge I was referring to earlier and our approach to connecting systems will address this problem.  Enter ESB, SOA, BPA, BPI, and Click here to generate another acronym.  Also enter BizTalk, WCF, and WF.  The goal of MOCSDUG is to focus on these technologies and approaches to understand how we can better solve the integration problem.

I am currently still working to get a site setup for MOCSDUG so please be patient.  In the meantime, do not hesitate to contact me (mnagisetty at if you would like to be added to the mailing list.

It looks like some of you are already excited and blogging about MOCSDUG.  That’s great! Spread the word! 

February 7, 2008 Posted by | Uncategorized | , | 1 Comment