Skip to main content

Async Plugins vs. Power Automate Flows

1 comment

The installer was interrupted before Application could be installed...

This error occured as I tried to install a custom installer web project, built with VS2008 in 32-Bit or 64-Bit mode on my 64-Bit target system.

To get more details on that error, I tried the following command in my console window:
msiexec /i /l*vx install.log

The log file pointed out the following error:
MSI (c) (60:54) [17:00:43:240]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (60:54) [17:00:43:240]: Connected to service for CA interface.
INFO : [06/22/2008 17:00:43:346] [SetTARGETSITE]: Custom Action is starting...
INFO : [06/22/2008 17:00:43:347] [SetTARGETSITE]: CoInitializeEx - COM initialization Apartment Threaded...
ERROR : [06/22/2008 17:00:43:349] [SetTARGETSITE]: FAILED: -2147221164
ERROR : [06/22/2008 17:00:43:349] [SetTARGETSITE]: Custom Action failed with code: '340'
INFO : [06/22/2008 17:00:43:350] [SetTARGETSITE]: Custom Action completed with return code: '340'
Action ended 17:00:43: WEBCA_SetTARGETSITE. Return value 3.
MSI (c) (60:E4) [17:00:43:352]: Doing action: AdminFatalErrorForm

After some "googling" I found the following two reasons for this problem and the solution to work around this issue:

1st reason:
In IIS 7 its called "IIS 6 Management compatability".

By default this module is not installed and enable. So we have to got to
"Control Panel\Programs and Features\Turn Windows features on or off" and then click the check box to enable that feature.



2nd reason:
Another issue might be the usage of 32-bit applications with a 64-bit IIS machine.
By default 32-bit applications are disabled. On the picture below you find a way how to enable them.

Labels:

Comments

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements. At-a-Glance Comparison This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details. Interactive Criterion Explorer Sel...
1 comment
Read more

CRM 2013: Translation import error: The value passed for ConditionOperator.In is empty

This week a very evil error drove me nuts. In CRM 2013 I tried to import a translation file into an organization. It always ended up with this error message: The value passed for ConditionOperator.In is empty I was like what in the world does this message mean. If an old school approach in splitting up the file into serveral smaller Import files I finally figured out that the following lines in the "Localized Labels" sheet caused this trouble: RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.HomepageGrid.Group0.Control0.ToolTip.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.LocLabel RibbonCustomization 11a15acc-61f1-e311-93f9-00505681252e Mscrm.Isv.orb_input.SubGrid.Group0.Control0.ToolTip.LocLabel To resolve t...
Post a Comment
Read more