BizTalk
General BizTalk posts.
A few months ago a few of us had an idea - what would be the ideal hosting and support site for .Net Developers? Dot Net Haven? Perhaps. www.dotnethaven.net is currently active and growing quickly. Initial features are hosting plans, FAQ's with the responses that only premier blogs like this one provide; a Help Desk Ticket system that provides some limited support for users. Finally? If you are an authorized MSDN Licensee and get clearance, you have access to the SharePoint Portal sandbox that we're...
Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group on this server The devil is always in the details J The following I wanted to share because this individual sorted through this error and his resolution may help someone else. I am posting a summary of our correspondence. PROBLEM: BizTalk Deployment Failing – Error: Unable to connect to registry on the server (machineName), or you are not a member of the OLAP Administrators group...
Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup (NOTE: If you find any errors here - please feel free to point them out - I worked hard to document each step and leave nothing out. Some of the steps that are not detailed are so because the process is pretty straight-foward.) This document takes the following considerations into account. Please note: You need to be familiar with basic network naming conventions for this setup. Before beginning the processes to setup BizTalk...
I noticed, only after some feedback, that my original post did not inlcude the actual Xml structure of the file you needed to complete. I apologize for this. I am not very used to how these blogs strip out (or does not strip out) Xml references. Hopefully the new entry / update will not only make sense, but help the hundreds that have reviewed this article and were not able to use it with out this fix. Again, my apologies. I'be beein on the road for several weeks - and getting time to update aspects...
I had a challenge recently that was quite a blast sorting through. The architecture included HIS 04 on the BTS NLB clustered nodes - where the HIS database objects were to be on a A/P Failover SQL Server 2000 Cluster. By design, you cannot deploy the database objects to a clustered instance of SQL Server. I sent the following to PSS after implementing a successful 'work-around'. Deploy Host Integration Server 2004 on a Clustered SQL Server 2000 Instance PROBLEM When you have SQL Server 2000 Enterprise...
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. SQL Server: \. Database: BizTalkDTADb The above error seems to indicate that more than one TDDS is processing at the same time / on the same data, locking it and preventing access to it. If you experience this error in a clustered / multi-node BizTalk Server environment, follow...
I have deployed dozens of BTS 04 servers and in each engagement I go on I find much the same scenario: There are great BTS developers that know how to use specific components in the Orchestration Designer, or who can code snippets that BTS can transact wtih. However, when it comes to deploying a clean BTS architecture, very few seem to understand all of the nuances - myself included :) As I run into various challenges, I'll take the time to post the challenge and my approach / solution here - in...
BizTalk Server 2004 Setup/Architecture – Stand-Alone Instance(s) To simplify this documentation, the BTS server is BTSSERVER and we will use SQL Server on a remote SQL Server called SQLSERVER. Service Account Setup Perform the following service account setup on both of these servers, and be sure the noted pre-requisite components are all in place: Login as Administrator, or an account that is a member of the Administrator’s Group on the machine. Create a user account that will be used...
Clustered Enterprise Single Sign-On (ENTSSO) Setup When you want to configure BizTalk Server on multiple NLB (network load balancing) nodes, you will have to install / configure the SSODB (Enterprise Single Sign-On – ENTSSO) service on a clustered SQL Server instance. For this document, SQL Server runs clustered on a 2 node cluster – SERVERNODE1 and SERVERNODE2. This document provides a real deployment – where the domain names are generic in this case. For example, I use / and then...