Installing BizTalk on a Production Server without VS.Net

One interesting learning today…  I was building a BizTalk Server machine that was designed to be a production server (production defined to mean no locally installed Visual Studio.Net, no local SQL Server, etc…)  and ran into a problem where BizTalk couldn’t write a .dll file…  After some nashing of teeth, it turns out that the BizTalk installation program requires permissions to the C:WindowsTemp directory, and the file name is a temporary name (so it’s different each time you execute the install).  On a single server installation, VS.Net (and perhaps SQL Server), set the permissions on the WindowsTemp directory so that other apps can write to it…  By not installing VS.Net on this particular machine, that setting was missing.  Once I fixed that, the BizTalk instal finished fine.  This is a simple work around, but one that can kill an evening or two if you don’t know about it.  Enjoy.

2 thoughts on “Installing BizTalk on a Production Server without VS.Net”

  1. Before installing BizTalk 2004, you need to be a member of the local Administrators group. This is documented in the BizTalk 2004 installation guide at http://www.microsoft.com/downloads/details.aspx?FamilyID=32FF7D19-9E25-44CE-8A8C-03E3EB5D726F&displaylang=en

    Being a member of the local Administrators group should give you access to the temporary directory. Recommendation is to temporarily add the installing user to the local Administrators group and then remove after installation and configuration.

    Phil Bolduc
    Sierra Systems Group
    Vancouver, BC Canada

    Like

  2. To successfully install BizTalk 2004 you need to be a member of the local Administrators group. See <a target="_new" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=32FF7D19-9E25-44CE-8A8C-03E3EB5D726F&amp;displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=32FF7D19-9E25-44CE-8A8C-03E3EB5D726F&amp;displaylang=en</a&gt;
    <br>
    <br>Being a member of the local Administrators group should solve the access to the temporary directory. Recommendation is to add installing user to local Administrators group, log off, re-login, install BizTalk 2004 and configure BizTalk 2004. The finally remove installing user from Adminstrators group.
    <br>
    <br>Phil Bolduc
    <br>Sierra Systems Group
    <br>Vancouver, BC

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s