BizTalk version table

The following table provides an overview of all BizTalk versions and corresponding version numbers:

Product name Service pack Version number
BizTalk Server 2004 3.0.4902.0
BizTalk Server 2004 SP1 3.0.6070.0
BizTalk Server 2004 SP2 3.0.7405.0
BizTalk Server 2006 3.5.1602.0
BizTalk Server 2006 R2 3.6.1404.0
BizTalk Server 2006 R2 SP1 3.6.1404.0
BizTalk Server 2009 3.8.368.0
BizTalk Server 2010 3.9.469.0

You can find the version number of any BizTalk installation in the registry. Look for the key ‘ProductVersion’ in ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\x.x’

I also wrote a simple but handy PowerShell script to determine the BizTalk version number. You can find it here.

I’ll  try to keep this table updated for new releases and updates.

12 Responses to BizTalk version table

  1. Mikael Sand says:

    Seriously dude, is the version number tha same for 2006 and 2006 R2 or is it a typo?

    If it’s not, is there any perticular reason for the versioning that you know of?

  2. Zeeshan says:

    The version number after a SP1 install on BizTalk 2006 R2 comes out as 3.6.2149.10

    • Randal van Splunteren says:

      Hi,

      Thanks for your comment. So in your case the version number actually changed after applying sp1? Did you install anything else (in terms of hotfixes, etc.). I’ll try an installation again and see if can reproduce this.

  3. RDL says:

    I have noticed the same behavior as in the list, one thing I might comment on though is that all of the servers I’ve seen this on are upgraded from 2006 R1 to R2, then the SP. Maybe that is the difference? I thought it odd that the SP didn’t have a different version.

  4. Imre Zolnai says:

    You can add a new line to your great table.
    3.9.469.0 seems to be the RTM BTS 2010.
    At least DEV version gives this back and do not ask why not 4.0.0.0 ;)
    Imi

  5. Amy Zhao says:

    Hi Randal,
    I am a new guy for Biztalk study. my name is Amy. I am from China. and I got a issue about file name with ftp send port.
    I google biztalk then I found your blog. I really hope you could kindly help me with your ample experience.
    it is a dynamic send port, there are some traditional chinese characters in file name. english character is ok
    but traditional chinese characters all become “????” when I check file using ftp client “WinSCP” after file was deliveried

    to ftp flder. if I copy a file manually to FTP folder the file name show normally.
    below is my code in orchestration file. any help would be appreciate.

    msgSend=msgReceive;

    tmpString=msgReceive(FILE.ReceivedFileName);
    tmpVar=tmpString.Substring(tmpString.LastIndexOf(“\\”)+1); //get file name without directory

    tmpFilename=tmpVar.Substring(tmpVar.LastIndexOf(“_”)+1); //get last part of file name after character “_”

    msgSend(FILE.CopyMode)=2;
    msgSend(FTP.RepresentationType)=”binary”;

    msgSend(FTP.UserName) = “user”;
    msgSend(FTP.Password) = “123″;
    msgSend(FTP.BeforePut) = “CWD //opt/user/Unit Test/”;

    SendFolder(Microsoft.XLANGs.BaseTypes.Address) = “ftp://abc.com” +”//opt/user/Unit Test/” + tmpFilename;

    ps: SendFolder is send port. file name like NET_林頓際資合健康金.pdf. send pipeline is Microsoft.BizTalk.DefaultPipelines.PassThruTransmit.

    thanks again for you read my mail. :)
    my personal email is angel.34@163.com. looking forward to your reply.

    Regards
    Amy.

    • Randal van Splunteren says:

      Hi Amy,

      Thanks for your message.

      It is probably not surprising but I never had to deal with traditional chinese characters in my solutions :-) . Anyway I wonder what the value of the FILE.ReceivedFileName. As far as I understand your solution the incoming file already contains chinese characters, right? Use Tracking or write System.Diagnostics.Debug.Writeline(tmpString) in your orchestration to find out how the filename looks when it has arrived in BizTalk.

  6. Szymon says:

    Hi Randal

    Could you inform me, if there is any key in:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\x.x

    which contains type of edition, e.g. Developer, Enterprise?

    And could you paste here full key name and ProductVersion value of any BizTalk version?

    • Randal van Splunteren says:

      Hi,

      I believe you can use ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\ProductEdition’ for this purpose.
      I’m not sure of all the possible values. ‘Developer’ is the only value I checked.

      Regards,

      Randal

Leave a Reply

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

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com 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 )

Connecting to %s

Follow

Get every new post delivered to your Inbox.