Geeks With Blogs

Mike H. - Another Geek In Need... WebLog

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 Server on any servers, ensure that you have read and completed the steps covered in Enterprise Single Sign-On (ENTSSO) Setup.


NOTE: This deployment of BizTalk is a complete install: BAS/BAM is setup, and this requires Analysis Services and SharePoint Services 2.x to be installed. A word of caution: If you are running applications under the DefaultAppPool, the installation of SharePoint Services could cause problems with the execution of those applications. You need to be familiar with the different installation options for SharePoint. Here we perform some pretty basic stuff – but I wanted to mention this.


At the time of this setup, Host Integration Server 2004 had a newer SSO engine, so we actually used that SSOENT setup instead of the BTS one. You can use either, but we ultimately wound up clustering this setup – which requires setting up the Enterprise Single Sign-On (ENTSSO) on a clustered SQL Server.


This setup takes into account that we are 1) running SQL Server clustered – with a virtual machinename of HAMILTON\SQLSERVERINSTANCE. This cluster runs on the servers HAM1 and HAM2 respectively.


There are 2 computers used to setup BTS. Each is in the HAMILTON domain, and each is named BTS1 and BTS2 respectively. Network Load Balancing is being used on these servers – not full clustering. For basic HTTP orchestrations, this will work great – but you will see some notes below that address the obvious: BTS is an active/active server component itself, and is not designed to be clustered. We had a requirement to make it work nonetheless, and we did. So read onJ.


Within an enterprise, it is ideal to use domain-level security groups, so you have a little leg-work to do here. For this walk-through, we used a domain called HAMILTON, and the short name in our group naming convention of HAM .


 The following BizTalk and HIS domain-level groups were created before proceeding:

 (This is a Systems Administration task – often handled by your AD or Server Group personnel.)


  • HAM BizTalk Application Users
  • HAM  BizTalk BAS Managers
  • HAM  BizTalk BAS Users
  • HAM  BizTalk BAS Web Services Group
  • HAM  BizTalk Isolated Host Users
  • HAM  BizTalk Server Administrators
  • HAM  EDI Subsystem Users
  • HAM  HIS Administrators
  • HAM  HIS Runtime Users
  • HAM  SSO Administrators
  • HAM  SSO Affiliate Administrators


Notice that the naming convention is the default for BTS and HIS – preceded by HAM and a space.


Next, add the HAMILTON/BtsService user (service) account to the following groups:

(This is a Systems Administration task as well.)


  • HAM  BizTalk BAS Managers
  • HAM  BizTalk BAS Web Services Group
  • HAM  BizTalk Isolated Host Users
  • HAM  BizTalk Server Administrators
  • HAM  HIS Administrators
  • HAM  SSO Administrators


We are now ready to install the prerequisite software.


NOTE: We copied all necessary CD’s for all components that we were going to install to a \Microsoft folder on each server. These include:


  • BTSENT04      -           BizTalk Server 2004 Enterprise License
  • HIS04              -           Host Integration Server 2004 License
  • SQLOLAP      -           SQL Server 2000 Analysis Services License
  • SP3A               -           Service Pack 3a for SQL Analysis Services License
  • WSS2              -           Windows SharePoint Services 2.x License


Prerequisite Software (some optional):


  • SQL Server 2000 Enterprise Edition
  • SQL Server 2000 Service Pack 3a
  • SQL Server 2000 Analysis Services
  • SQL Server 2000 Analysis Services Service Pack 3a
  • Internet Information Services 6.0 (NOTE: By default IIS 6.0 configuration does not allow ISAPI extensions. You must explicitly configure this before using BizTalk Server HTTP receive handlers.)
  • ASP.Net
  • MSXML 4.0 (Must be done for each BTS Server)
  • SQLXML 3.0 SP2 or later. (Must be done for each BTS Server)
  • SOAP SDK 2.0 (optional, but recommended)
  • MS OWC (Office Windows Components) Version 10 (Must be done for each BTS Server)
  • NOTE: KB Article 831950 deals with a transaction log / backup issue and should be applied to the server after SQL Server is configured.
  • SharePoint Services 2.0



Installing Analysis Services

Install the SQL Server 2000 Analysis Services.

You do not need to install Sample Applications or Books Online

Immediately afterwards, install the SP3a (Service Pack 3a) for OLAP (SQLOLAP).


Installing Windows SharePoint Services

Install the SharePoint Services, and test the installation once completed:

  • Permissions need to be set up on the target SQL Server, granting Database Creator permissions to the account desired. (We used our BtsService account in this walk-through.)
  • Open Web Service Extensions management (Computer Mgmt à Services à IIS à Web Service Extensions)
    • Prohibit FrontPage Server Extensions
    • Enable everything else except CGI Extensions
  • Go to Add/Remove programs à Widows Components à Application Server
    • Check “Enable Network DTC Access”
    • Open IIS, uncheck FrontPage Server Extensions
  • Install SharePoint Services making sure to install on a Server Farm and not a typical installation.
  • Create a new Application Pool.
  • Because we are configuring for BTS BAS, call it SharePointBASPool, for lack of a better imagination.
  • Select Configurable option under Select a Security Account for This Application Pool.
  • Provide the username / password to use for this configuration (in this case, the user id is HAMILTON\BtsService; password = ).
  • Restart IIS, and then click OK. (NOTE: Do NOT click the OK for SharePoint before restarting IIS (drop to a command prompt and type iisreset. – Otherwise you’ll be uninstalling and doing this part over – for WSS.)
  • Next, Set Configuration Database Server. Provide the HAMILTON\SQLSERVERINSTANCE as the SQL Server instance.
  • Provide a name (such as SharePointBASDb) for the configuration database in SQL Server 2000.
  • Select Users Already Have Domain Accounts for this configuration.
  • Click OK.
  • Uninstall FrontPage extensions (if applicable)
  • From the Central Administration window, we need to create and configure the Content Database.
    • Select Extend or Upgrade Virtual Server from the Virtual Server Configuration options.
    • Select Default Web Site.
    • Select Extend and Create Content Database.
    • Provide our SharePointBASPool application pool.
    • Provide the same username / password we used for our application pool setup (under site owner settings).  In this case, it is HAMILTON\BtsService
    • We need to now test SharePoint by creating a test site.


To verify that SharePoint is configured correctly

  • You may select the hyperlink displayed as the top-level website to test this configuration.  If the template shows up, then the configuration worked fine.  If you want to be absolutely sure, perform the more thorough check below:
  • On the Start menu, point to Control Panel, click Administrative Tools, and then click SharePoint Central Administration.
  • Click “Create a top-level Web site”. Click your default Web site, typically named “Default Web Site".
  • On the next page, in the Web Site Address section, supply a name for the new Web site. In the URL Name box, type test. This will create the site http:///sites/test.
  • In the “Site Collection Owner” section, enter a valid username using the format domain\user, and an email address, for example
  • Click OK.
  • On the next page, click the hyperlink for your new site. Then select a template for your site.

You should see your new Web site. This indicates that SharePoint is working correctly.

To delete this site, return to SharePoint Central Administration (to the home page) and select Delete Site Collection. Type the complete URL for the site to delete and then confirm the deletion.

·        Important If the SharePoint Configuration database, Content database, and BizTalk Server 2004 exist on different computers, and if you use Windows authentication to access those databases, then you must have db_owner permissions on these databases when running BizTalk Server 2004 configuration. After BizTalk Server configuration is complete, these permissions should be removed from the SharePoint Configuration and Content databases.



Installing BizTalk Server 2004


We need to make sure the following local groups are created on the target SQL Server boxes (HAM1 and HAM2 – our clustered servers for SQL Server.):


·        BizTalk Application Users

·        BizTalk Isolated Host Users

·        BizTalk Server Administrators

  • SSO Administrators



Once these Groups are created, we need to add our domain Groups to these local Groups. We do this using the Manage Users and Groups. Right-click My Computer, select Manage. When the computer management MMC opens, expand Manager Users and Groups and then select Groups on the left hand side.


Create the groups we need, and during the creation, you will see a button at the bottom that will allow us to add Users or Groups to this Group. We want to add to each group the respective domain group.


For the BizTalk Application Users we’ll add the HAMILTON\HAM BizTalk Application Users group.


We do this for each of the groups. Notice the only difference in the default BizTalk group naming is that our domain group is preceded by HAMILTON\HAM and a space.



Make sure that our HAMLTON\BtsService account has permissions on the production servers (BTS1 and BTS2) to access the folders (read/write or full) so our orchestrations execute without error.  The directories in which the custom DLL files reside will require at least read access for the service account.


Now run the BizTalk installation – and perform a complete installation.


Once this is complete, run the BizTalk Server Service Pack 1 upgrade.


Configuration Framework (First node in the cluster on machine BTS1-You will repeat this on BTS2 once this first setup is complete.)


Once BizTalk is installed, execute the ConfigFramework.exe from the \Program Files\Microsoft BizTalk Server 2004\ folder.


We are creating a new BTS Group.


This will not be the Master Secret Server. (That was setup under the Enterprise Single Sign-On Setup.)


Select Untrusted for both Host and Isolated Host Application(s). (We will review creating Trusted hosts later.)


When prompted, select yes to both Create an Analysis database for tracking and Use an Analysis Server for BAM Aggregations.


Next, specify the correct Windows accounts for the default groups created by BizTalk Server.  Change the windows account for access control to the domain groups.  Add the prefix “HAMILTON\HAM “to all of the default groups to utilize the HAMILTON domain accounts (with the exception of the BAS Site Owner).  Change the BAS Site Owner to the service account (HAMILTON\BtsService).


When prompted, change the default Site for the BAS site to SharePointBASSite.


Next, we leave the default BizTalk Host Name and Isolated Host Name as they are.


Next we leave the default Human Workflow Service Web Site the Default Web Site.


Next we specify the database for all of the database objects, except the BAS databases. Our production database is HAMILTON\SQLSERVERINSTANCE for all of the databases, including the SSODB. The installation should default to the proper BAS database as the machine name that OLAP was installed on.


Next we specify the Windows service account that is used to execute the list of services. We provide our HAMILTON\BtsService account for all of these services. (Yes, if you want to setup different _service accounts for running different services, you can – we are simply providing the basics here.)


Next, leave the default BAS site, but change the default email to a valid address.


Next, we will bind all message queuing to the virtual IP of our clustered BTS production servers (Again, this is a clustered-ready setup – so our servers have load balancing running – and each server group (2 or more) share a virtual IP address. For this example, you can also simply provide the server IP that you are working on).  This will ensure we have NLB routing to each server for load balancing.


Next, save the Configuration Setup and click Next to proceed.  If prompted for a login, use the BTS service account.


Setting up the Registry for Clustered BizTalk Orchestrations

Once this instance of BizTalk is configured, we need to modify the registry using the regedit snap-in.


Select StartàRun and type regedit and press .

Load Balancing File Receive When BTS is Load Balanced in Windows

It seems compelling to specify a file receive folder on a remote server that can be used by more than one BizTalk Server as a file receive folder, in order to provide a simple load-balancing scenario on a file receive.  However, a race condition may arise in cases of heavy load that causes some messages to be locked and orphaned.  A symptom of this is “File Not Found” errors appearing in the Application Event Log as one server tries to receive files that are already being received by another server.  Therefore, it is not recommended to try to load balance file receive locations unless you have a compelling reason to make it work.


There is a workaround for the race-condition issue, and you may wish to investigate its suitability for your application.  BizTalk Server 2004 is able to rename files before locking them for processing.  Since the rename can be done in a single file system operation, it prevents other servers from attempting to receive them.  To enable this feature, create a new registry key for all receiving servers:

HKLM\System\CurrentControlSet\Services\BTSSvc{GUID} RenameReceivedFiles DWORD 1.  This has a few side effects:

  • The files are renamed by being given a new extension (.BTS-WIP).  This means that if there is any service interruption before reception is completed (such as dropping the SQL Server connection), these files could be orphaned because they will not be picked up under the file mask that filters that receive location.  You don’t want to change the file mask to *.*, because this negates the effect of renaming the files.  An idea for solving this is to create another receive port/receive location that is only serviced by a single BizTalk Server, and set its file mask to *.BTS-WIP.  This will pick up any files in the receive folder that are orphaned by this issue.
  • During failover, you may or may not experience issues with the file renaming process. If both servers in the cluster are configured like this, we did not experience 1 problem – however, the individual that provided this work-around stated that problems have been experienced during failover.


Installing Host Integration Server 2004


Now we are ready to install HIS 2004.  Here we perform a complete installation.   Ensure that all Security options are selected (expand that node and select all options).  Do not include the SDK or Toolkit.


Once the HIS 2004 is installed, run the ConfigFramework.exe for HIS and complete the setup.  Select Join for the SSO configuration and Yes to configure the HIS databases.  Leave the Windows accounts as default.  Select a non-clustered server the SQL Server for both the SSO database and the TI database.  HIS cannot resolve a clustered server for this function, but we will work around that later.  Set the Windows service configurations to utilize the domain service account (HAMILTON\BtsService).  Enter the HIS subdomain as HIS_PRODUCTION.  Accept the default for network protocol.  Save the configuration and finish the wizard.


Deploy Host Integration Server 2004 on a Clustered SQL Server 2000 Instance

(Taken from a related article already posted.)



When you have SQL Server 2000 Enterprise installed on a A/A or A/P (active/active or active/passive) cluster, and you are running Virtual Instances of SQL Server, you will experience a problem when you try to install HIS on a different server, pointing the database connection to one of the virtual instances on the cluster. The ConfigFramework fails with the following found in the error log:

·          [12:50:59 PM Info DatabaseHelper] Configuring HISAdmin database role.

·          [12:50:59 PM Info DatabaseHelper] Executing database stored procedure:

·          [12:50:59 PM Info DatabaseHelper] sp_grantlogin '\HIS Administrators'

·          [12:50:59 PM Error ConfigHelper] Windows NT user or group '\HIS Administrators' not found. Check the name again.

In our case, we provided the \ for the database to connect to. For example, SERVER_A\SQLSERVER_A.


HIS passes the virtual machine name to SQL Server, and SQL Server cannot resolve the name because it is a virtual instance, and the groups are on the physical machine, and the command sp_grantlogin on that \GroupName will fail.



Microsoft is aware of this problem, and provided us part of the following solution. We note additional items not provided in the solution, but necessary for the HIS, TI (Transaction Integrator MC), and ENTSSO to work properly.


For this to work, you must already have the ENTSSO installed on a SQL Server cluster where the SSODB resides. Also, you will need a stand-alone SQL Server that is not a virtual / clustered instance to install HIS onto. (We used HAMILTON\TEST for this – another SQL Server installation – not clustered.)


  1. Install HIS, pointing it to the stand-alone SQL Server (if SSODB does not already exist on a stand-along SQL Server, create it at this time, otherwise JOIN it).
  2. Create the MSHIS_xxx database objects manually on the clustered, virtual instance of SQL Server. (MS)
  3. On each node of the cluster, manually create the HIS Administrators and HIS Runtime Users security Groups. (MS)
  4. Create logins for these security Groups on the virtual instance of SQL Server you created the database objects on. (MS)
  5. Add these logins to the database objects created. (MS)
  6. For each database object created, create 2 rolls – HISAdmin and HISRuntime.(MS)
  7. Add the HIS Administrators login to the HISAdmin roll in each of the databases. (MS)
  8. Add the HIS Runtime Users login to the HISRuntime roll in each of the databases. (MS)
  9. From the machine you installed HIS, copy the file HIPTables.sql from the \Program Files\Microsoft Host Integration Server\System folder to a folder where the clustered SQL Server instance is running.
  10. Run Enterprise Manager on the clustered SQL Server.
  11. Select ToolsàQuery Analyzer from the menu bar, and execute the Query Analyzer.
  12. Ensure that you are in the MSHISxx_HIP database.
  13. Open the file HIPTables.sql file – from within Query Analyzer.
  14. Execute this script at this time (MS).
  15. Close Query Analyzer.
  16. With Enterprise Manager still open, expand the MSHISxx_HIP database.
  17. Select Tables on the left tree, and local the table Computers on the right.
  18. Right-Click and Return All Rows of this table object.
  19. Here you will see the machine name of the computer you are on. You will want to change this to the machine name that HIS is actually going to be running from. NOTE: If you are running HIS from a NLB cluster, you will have more than one machine name here. For each HIS machine that will be using this database, enter those machines names now (KB 885003).
  20. Save the edits, and exit Enterprise Manager.
  21. On each machine that HIS is installed on, and that you want to interface with the clustered SQL Server, you must make the following registry edits.
  22. Execute the registry editor – StartàRun and type in regedit and press .
  23. Locate HKLM\Software\Microsoft\Host Integration Server\HIP and select HIP.
  24. You will see and entry for Connectionstring in the right pane – double-click this (or right-clickàproperties) to edit this entry.
  25. Change the database reference here to the \ of your clustered SQL Server (HAMILTON\SQLSERVERINSTANCE for us).
  26. Now, locate HKLM\Software\Microsoft\ENTSSO\SQL and select SQL
  27. You will see an entry for Server in the right pane – double-click this to edit this entry.
  28. Change the database reference here to the \ (HAMILTON\VIRTUALSSO) of your SSODB clustered SQL Server.
  29. Performing these registry edits on each HIS machine that must use the clustered server will allow all components of HIS to work.
  30. You will also need to do a command line prompt of “ssomanage – updatedb ssodb.xml” where the xml file contains the target SSO server (HAMILTON2 in this case – I note this because the domain HAMILTON runs on HAMILTON1 and HAMILTON2 servers. This has to be done for proper SSOENT setup on the clustered servers.).



Performing Installation on Secondary Node/Server (BTS2)


We are now ready to perform the same setup on BTS2 server – or secondary node.


All aspects of the setup are the same except for the ConfigFramework.exe setup in BTS 04 and HIS 04. We will not be creating a new BTS group, but rather, Joining and existing Group – already installed on BTS1.


You will otherwise follow the same steps already noted above.


NOTES: Joining the first BTS Server with server #2

If you are attempting this with 2 BTS servers, and you find that you cannot JOIN the first group/BTS Server, ensure that you have 2 machines that are 'member' servers of the same domain.


If you have 2 servers that you want to create this environment on, and these servers are not joined to the same domain controller as member servers, then one 'cannot' see the other.


NOTES: Link for ENTSSO Setup


NOTES: Good Point Pedro

Pedro, very good point. So the question is, are we working with Standard/Partner edition? Or are you using Enterprise? (I am directing this specifically to BHambert).

Microsoft's stance on the Standard and Partner editions is pretty straight-forward: They're for light weight, limited integrations. Please reference for comparison/review of each.

Standard/Partner versions will not deploy for multiple servers like the Enterprise/Developer versions. So you will not be able to JOIN like this document refers to - more than one server.

Posted on Wednesday, August 31, 2005 7:26 AM BizTalk | Back to top

Comments on this post: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Thanks for this wonderful document.
I am trying to setup multiple biztalk servers in our environment but ran into some issue when I try to join my second biztalk server to the existing BizTalk group as the configframework utility didn't show up "JOIN" option at all !!!
Details are as below:

1) Completed BizTalk installation under BIZ-SVR1 and BIZ-SVR2, applied BizTalk Server 2004 rollup fix 1, KB884532, KB887575
2) Configured BIZ-SVR1 using Domain gropus but not creating the hosts
3) BIZ-SVR2 configframework didn't give me an option to join the existing biztalk group, and I could see only option "Create"
Left by BHerbert on Oct 13, 2005 7:30 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Can you put a link to this article? Enterprise Single Sign-On (ENTSSO) Setup

Left by Avi on Oct 25, 2005 6:03 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
BHamert wrote "I am trying to setup multiple biztalk servers in our environment...I Try to join my second biztalk server to the existing group...utility didn't show up "JOIN" option at all"

During the set, the first info screen asks about Create a new BTS group, will this be the Master SSO, etc.

Here, you would CREATE your first BTS group on the BIZ-SVR-1

During the configframework on the BIZ-SVR-2 you can JOIN the first created group.

However... The group or JOIN is not an option...

Check / Ensure that both of these servers are member servers of the same domain. If you are trying to do this on servers that have not been 'joined' to the domain at all - you will run into what you are seeing.
Left by Michael Hamilton on Oct 26, 2005 6:37 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
About the "The group or JOIN" option, i think that you can run into that problem when you are trying to install a standard version of Biztalk... Is this the case?
Left by Pedro Almeida on Oct 27, 2005 8:16 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
BTS Standard, does not allow for more than one server to be a member of a group. For this scenario, you will need enterprise.
Left by Todd Sussman on Nov 04, 2005 12:40 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
I am having some SSO issues after installing Host Integration Server 2004 on the server that is already having Biztalk Server 2004 as both of them are sharing the common SSO features.

Can you please let me know what are the steps to be taken to properly install and configure HIS 2004 on the server that is aaready having BTS 2004?

Do i need to select the Security check box to install Enterprise SSO and Admin? I think it already comes with Biztalk.

Also, does this HIS 2004 installation and configuration disturbs any existing BTS 2004 running with some applications in Production?

Please suggest. Thanks,
Left by Durga on Jan 17, 2006 4:16 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Durga - this is not an uncommon problem.

First, you have to ConfigFramework.exe /U to un-do the BTS deployment.

Then run the ConfigFramework for HIS and use HIS's ENTSSO / SSODB - it is better and is much different than the one that ships with BTS.

Then run the ConfigFramework for BTS again, and join it to that SSODB.

Please feel free to ping me at mhamilton at nusoftsolutions dot com (if that helps).
Left by MikeH on Jan 17, 2006 4:24 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
I am already having some biztalk applications running on BTS 2004 and so i cannot do "ConfigFramework.exe /U".

Is there any other way to configure HIS 2004 without disturbing BTS or its running applications? I mean can i backup the biztalk databases before doing "ConfigFramework.exe /U" and import it after configuring HIS 2004?

Also, since i am having SQL cluster for Biztalk databases, can i use same Cluster database server for HIS 2004 databases? if not, should i install local version Sql Server 2000 enterprise to configure HIS 2004?

Left by Durga on Jan 17, 2006 4:46 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Durga, I understand that you have BTS processes running, but you will not be able to install the HIS because it requires the newer SSODB and ENTSSO.

It sounds like you have this clustered? That would mean that you have installed the ENTSSO on the SQL Server virtual instance, and then setup your BTS boxes?

You can stop the ENTSSO on each SQL instance. Uninstall the ENTSSO and then install the HIS version.

Once this is done, you'll be running the newer clustered version of the ENTSSO and you can then install HIS.

The root of your problem is that HIS requires the richer/newer SSODB (Enterprise Single Sign-On ENTSSO).

Hope this helps...
Left by MikeH on Jan 17, 2006 5:55 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Thanks for the information.
Left by durga on Jan 18, 2006 10:56 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
let say I want to upgrade our production BizTalk Server 2K4 database into cluster. Do I need to uninstall and reinstall BizTalk?
Left by rasyadi on Apr 17, 2006 10:52 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
We have already running biztalk 2004 and its working properly but whenever it connected to Cluster data base it fails. Can you give me the possible reason.
Left by SAMPA on Jul 25, 2007 4:39 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Hi Sampa,

Foremost, have you configured the ENTSSO to run on the SQL Server cluster first?

Once you have completed this, have you created the appropriate domain-level security groups, as well as the groups on the SQL Server cluster that will be needed by BTS?

Check these first to ensure they're created before attempting to configure BTS to go against the SQL cluster.

Left by MikeH on Jul 25, 2007 7:33 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
hi MikeH,
Yes it is configured
We have checked every groups are ok. But still its not working
Left by SAMPA on Jul 26, 2007 1:08 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Hi Sampa,

Without seeing your actual setup / deployment, it is obvious that it would be next to impossible to speak to the issue you are seeing.

You are saying that the service is failing. Are there event log entries, or a log files in the BTS install path that BTS is throwing because of an exception?

On the SQL Server, are there entires in any of the log files as a result of the service account that BTS is running as not having permissions to something?

Conversely, the BTS server itself, there may be a permissions issue on that box now.

When you originally install BTS - was it installed with SQL Server as a 'remote' server or were both BTS and SQL Server on the same host?

It sounds like the Configuration wizard needs to be run - disconnect from the previous setup altogether and reconfig on the clustered SQL Server instance. If this config wiz runs okay and you attempt to start the service and it stops - there will be entires in either the BTS host event logs or on the clustered SQL Server event logs or both.
Left by MikeH on Jul 26, 2007 7:24 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
What would be the OS requirement for the BizTalk Servers? Would Windows Server 2003 Standard edition suffice or is the Enterprise Edition the bare minimum....Any pros and cons would be helpful?

Left by ACorrea on Dec 03, 2008 1:44 PM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Hi ACorrea...

Windows Server 2003 Standard will work fine.

The following link provides some good / solid foundation for planning a BTS deployment, best practices and whatnot.

No real pros/cons to speak of - depending on the solution being design w/BTS - it may or may not be a set of web front ends (WFE's) that host part of the solution, vs. some back end servers that host non-web host instances. Again, the requirements are largely driven by the solution.

But you can use Windows 2K3 or 2K8 Standard with no issues.
Left by MikeH on Dec 06, 2008 11:00 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Why do we create Untrusted host while configuring?
Left by AC on Dec 16, 2008 1:56 AM

# re: Deploying BizTalk Server 2004 - Complete / Clustered - Production Setup
Requesting Gravatar...
Hi AC...

This was to simplify this setup - that's all - it is a matter of preference whether or not you want to go thorugh setting up a trusted host.
Left by MikeH on Dec 16, 2008 5:18 AM

Your comment:
 (will show your gravatar)

Copyright © Michael J. Hamilton, Sr. | Powered by: