Geeks With Blogs

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

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 to execute the BizTalk Server and SSO service on that machine (we’ll call this BtsService to simplify this documentation).
  • Do not make this account a member of any groups.
    • If this machine is a member of a domain, and the Group Policy does not allow us to add this account to the run as a part of the OS policy, then it will be necessary to make this local service account a member of the local machine’s Administrator’s Group – NOTE: This is not a best practice, but is acceptable for development work.
  • Run the Group Policy Editor (StartàRunà”gpedit.msc”).
  • Expand Computer ConfigurationàWindows SettingsàSecurity SettingsàLocal PoliciesàUser Rights Assignment
  • Under Act as part of the operating system, add our new service account. (NOTE: Some domain configurations will not allow this, so you can only make the service account a member of the Administrator’s Group on the current machine. This is acceptable for development, but should not be done for test or production.)
  • Be sure the following is installed on the workstation at this point:
    • Microsoft .Net Framework
    • MSXML 4.0
    • SQLXML 3.0 SP2 or later.
    • SOAP SDK 2.0 (optional, but recommended)
    • MS OWC (Office Web Components) 10
    • MDAC 2.8 (MS Data Access Components)
    • If workstations are XP, check KB Article 837119 to see if this update has been applied, and check to see if KB 329433 is applicable / applied.


  • Be sure the following is installed on the server at this point:
    • (This must be Windows 2003 Server)
    • 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
    • SQLXML 3.0 SP2 or later.
    • SOAP SDK 2.0 (optional, but recommended)
    • MS OWC (Office Windows Components) 10
    • 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



  • For the workstations, it is noted that Visual Studio 2003 is already installed. For the BizTalk server, VS 2003 w/C# should be installed to facilitate deployment in the development environment. (NOTE: IIS 6.0 must be installed before installing VS 2003). This is NOT a requisite, but will certainly make deploying your orchestrations easier for development purposes. For test / production a better practice would be to create batch files that can deploy an orchestration – much like you find in some of the online samples that are installed with BTS 04. This approach will make it easier for your development team to quickly role out orchestrations / changes to orchestrations, and will be simple enough for your support operations personnel to deploy.



Installation of Analysis Services


  • Ensure that a Typical Installation of SQL Server AS is performed (AS is found in the OLAP folder on the SQL Server installation CD).
  • Install Service Pack 3a for Analysis Services (SP3 for OLAP is found under the  ...OLAP\X86\SETUP folder under the SP3).


Network DTC Configuration


  • While on the BTSSERVER Server, select Start MenuàAll ProgramsàAdministrative ToolsàComponent Services. This opens the Microsoft Management Console (MMC) for Component Services
  • Expand Component ServicesàComputers and select My Computer (NOTE: This snap-in does not always expand the tree option just by clicking the “+” sign next to the option – you may have to select the option on the left to expand it).
  • Right-Click on My Computer and select Properties
  • Click the MSDTC tab
  • Click the Security Configuration button.
  • Be sure that Network DTC Access, Network Administration, Network Transactions, and Network Clients is checked.
  • Ensure that XA Transactions is checked.


NOTE: If MSDTC was already configured as noted above, restarting the machine is not necessary. Otherwise, restart the machine at this time.


SharePoint Services


  • 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 BASPool, 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 (NOTE: you can use our BizTalk service account (BtsService) or you may want to create a separate service account for SharePoint).
  • Restart IIS before  proceeding (it’s quickest to drop to a CMD prompt and type IISRESTART), then click OK.
  • Next, Set Configuration Database Server. Provide the SQLSERVER as the SQL Server.
  • Provide a name (such as BASSharePoint) for the configuration database in SQL Server 2000.
  • Select Users Already Have Domain Accounts for this configuration.
  • Click OK.
  • 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 BASPool application pool.
    • Provide the same username / password we used for our application pool setup.
    • We need to now test SharePoint by creating a test site.


To verify that SharePoint is configured correctly

  • 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://BTSSERVERsites/test.
  • In the “Site Collection Owner” section, enter a valid username using the format domain\user (or simply the user name if not on a domain), 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 for Development

Run the BTS 04 installation.

We want to Create a new BTS Group.

This will be the Master Secret Server.

Select UnTrusted for both Host and Isolated Host Application(s).

When prompted, we selected Yes to both, create an Analysis database for tracking and use an Analysis Server for BAM aggregations.

Next, we left the default names for the Windows Group Names, the BizTalk Host Name, Isolated Host Name, and left the Human Workflow Services Web Site the Default Web Site.

Next we specify the database for all of the database objects. NOTE: Analysis Services uses the machine name only and not the database instance name for this configuration. Also, we connect to this database using the user account current logged in as – which was used when the Analysis Services was configured (you can change this, but we are keeping it simple for this deployment).

Next we assign the service account that will be used as the log on as account for the specific Windows services. We used our new BtsService account created local to the machine.

Next, we left the default Bind Message Queuing to all IP addresses on this computer.

The last screen allows us to save the Configuration Setup.

After saving, click Next.

If there are no issues with our Groups / Permissions, the configuration will complete successfully.


Groups Needed on the Remote SQL Server

NOTE: These groups must be created manually on SQLSERVER server, and the names must match the default groups BTS ConfigFramework created on our BTSSERVER server.

·        BizTalk Application Users

·        BizTalk Isolated Host Users

·        BizTalk Server Administrators

·        SSO Administrators

Once these groups are created, we need to create the BtsService user account on the SQL Server SQLSERVER server. Create it just as you did for the BTSSERVER server. Remember to set it to run as part of the operating system.

Finally, add the BtsService account to the BizTalk Server Administrators and SSO Administrators groups that we just created on the SQLSERVER server.


This provides you a complete deployment of a stand-alone BTS environment that you can now develop / deploy against. This is not necessarily the deployment you would use where varying security  issues come into play. For example, you may have web services that interact with a mainframe via Host Integration Server’s TI – and these may require a specific service account that is different from the BtsService account; also, a different instance of BTS may be needed for these orchestrations. I’ll cover this in another document addressing Multiple Instances of BizTalk Server 2004.

Posted on Sunday, May 1, 2005 1:18 PM BizTalk | Back to top

Comments on this post: Deploy BizTalk Server 2004 Complete - Stand-Alone Server

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
It was a great article and I really hoped to be able to install biztalk server,but it did not happen.There is an errror at the end of configuration wizard: failed to create sql login for Biztalk server Administrator group on database server SERVERNAME
I really do'nt know what to do.Please help me.
Left by Azin on Dec 13, 2005 7:27 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Azin, the first thing that comes to mind is that BTS cannot find the 4 Security Groups mentioned at the end of the article. These have to be created on the remote SQL Server box - manually - before you run the ConfigFramework.exe. Did you ensure these were created first?
Left by MikeH on Dec 13, 2005 9:36 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Microsoft BizTalk Server 2004 Configuration Wizard

Error is
:Failed to Create SQL Login for BIzTalk Administrators Group on Database Server 'xyz' Windows NT user or Group 'xyz\BizTalk Server Administrators' not found. Check the name again.

Kindly need help to solve this problem.
Left by jagadeesh krishna on Dec 29, 2005 6:14 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Got BT up ok however am having a problem with VS2003 on Win2003 - will not allow me to create Web Applications projects or Web Services - must be a 2003 configuration point I have missed. All help appreciated
Left by Geraint Jones on Jan 30, 2006 3:42 PM

# Biztalk 2004 Configuration error
Requesting Gravatar...
I am getting the follwing configuration error for Biztalk 2004.

An unexpected error occurred while validating the
configuration for the Single Sign-On server (The Server
service is not started.).

Single Sign On I can see installed but its not in the services mmc.

My environment is Windows xp sp2,Biztalk 2004, Stand alone installation.

Any help is appreaciated.
Left by Seshu on Jul 12, 2006 3:07 PM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Hi Seshu,

If I understand correctly, you are trying to build out a Windows XP/pro workstation to run a development environment for BTS 2004 - stand-alone on that workstation?

I know there were issues well over a year ago where XP SP2 created problems working with the Single Sign-On service on XP/Pro workstations after SP2 was applied (see:

I am not sure if trying to actually run a new master secret server under XP is even supported - if this is what you are trying to do.

I apologize for not being much help here. The only time I have used BTS under XP is for development purposes, and the ENTSSO was not configured when I did it.
Left by MikeH on Jul 13, 2006 6:03 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
wanna entire process of configuration of biztalk server 2004
Left by Abhi on Oct 24, 2006 10:41 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Can we reinstall MSDTC after installing and configuring BTS 2004? If not will it never work?
Left by Sandeep on May 12, 2007 7:30 AM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...
Hi Sandeep,

If you have already installed BTS then you'll notice that it installed some COM+ applications when you look at Components Services Computers My Computer COM+ Applications.

MSDTC, and in particular, the network security configuration - must be setup properly for these applications to work when SQL Server is not running on the same box that BTS is running on.

So, you can enable MSDTC (install it) and configure it.

The question is - has your BTS installation been working prior to this?

In any event, you should be ablet o install and configure the MSDTC setup, yes, and do so without uninstalling re-installing BTS. I have not had to do this before that I can remember, so I cannot really share a whole lot regarding the subject.
Left by MikeH on May 12, 2007 12:47 PM

# re: Deploy BizTalk Server 2004 Complete - Stand-Alone Server
Requesting Gravatar...

I followed the above methods and created BtsService User in my BTS Server. Since i didnt get access to make it a part of OS i added the user in the Administrator group(as it was a dev server) and then added all the groups mentioned in the SQL server...Im still getting an error while i configure the Group

"MSSQLServerOLAPService does not exist,SQL Analysis service is not running on this machine.Reconfigure detected.
ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

What should i do further to prevent this error
Left by Sudha Rajkumar on Sep 21, 2009 8:44 AM

Your comment:
 (will show your gravatar)

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