Problem with MSI installation after import in BizTalk 2010


I’m always on my migration of BizTalk 2009 to 2010 and this week I’ve seen that I’ve got a real problem when I try to install the msi BizTalk Application on Windows after importing in BizTalk.

I’ve got the following screen :

Ok, so I try to find some more explanation about this error.In the Application Log of the Event viewer, I can see :

Product: TestAppli — Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: CA_Install, location: C:\Applications\AppliTest\9239248D-5386-4E1B-97A5-DE9AC8810722\, command: C:\Program Files (x86)\Microsoft BizTalk Server 2009\CustomAction.exe /installtype=notransaction /action=install /LogFile= /LOGFILE=”” /PRODUCTNAME=”TestAppli” /PRODUCTVERSION=”″ /PRODUCTCODE=”{9239248D-5386-4E1B-97A5-DE9AC8810722}” /UILEVEL=5 /EXTRACTCABSONLY= /NOINSTALL= /DEPLOY= /MSITargetDir=”C:\Applications\Mediation\AppliTest\9239248D-5386-4E1B-97A5-DE9AC8810722\\” “” “C:\Users\USR_BT~4\AppData\Local\Temp\CFGA586.tmp”


Something catch my eyes :

command: C:\Program Files (x86)\Microsoft BizTalk Server 2009\CustomAction.exe

Ok, I’m working on BizTalk 2010 but due to the upgrade, the folder remains the same. But, when I first install BizTalk Server 2009, I decide to install this software on “Program Files” because I was on a x64 platform…

This point not seems to be a problem with the 2009 version of BizTalk.

So I’ve copied the executable CustomAction.exe and his config file CustomAction.exe.config into this location and all work fine…

My Question is :

Why there is always some hard coded element like this? In the registry, there is a key to know the BizTalk Install Path, so why this installer don’t use it? Bug with BizTalk 2010 msi generator? Maybe I will post a case at Microsoft


This entry was posted in BizTalk, Microsoft and tagged . Bookmark the permalink.

5 Responses to Problem with MSI installation after import in BizTalk 2010

  1. Hi Jérémie,

    I have brought this issue to the attention of all BizTalk MVPs. We’ll see what comes through.

  2. Pingback: BizTalk Application : Install MSI after Export get an Error (again??) | Jérémie – an other BizTalker

  3. Maulik Joshi says:

    I am using BizTalk2006 as a part of my application. I’ve created 7 application and they are working fine in BizTalk2006.

    But now, I want to upgrade my BizTalk2006 to BizTalk2010. So should I use import and export functionality to migrate my application on BizTalk2010?

    Will it be useful for me? Also, my applications are very straight forward application and does not contains any advanced feature of .Net framework 3.5.

    Thanks in Advance,

    • hello,

      As I know, BizTalk 2010 accept application that where build with an older version than .Net 4.0

      You said that your applications are very straight forward application and does not contains any advanced feature of .Net framework 3.5, you just use mapping and routing (no web service or sql adaptor, or specific pipeline component? ), so this method seems to be good. Don’t forget to export to make a Backup of your application

      I’m sorry, I can’t remember if I realize this (but I think, I did at least one application, because I said to my colleague that this was possible). The problem I’ve encountered is to rebuild old application on a platform (dev platform) that contains VS2010, .Net 2 to 4 and BTS 2010. The BizTalk Project refused to compile due to an error with the .net Reference. Indeed, some BizTalk assemblies must be used in .Net 4 project. (You may encountered this problem on your development server if you migrate your BTS and VS version)

      In your case, (you don’t need to rebuild) the problem should not appear.

      If I can suggest something, if your project have to change or evolve, re-build your project in .Net 4.

      feel free to ask more questions and post on how occurs your migration.

      Hope this help you

Leave a Reply

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

You are commenting using your 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