3

Resolved

'enable32BitAppOnWin64' is not a valid attribute of the deployment object 'createApp'

description

I am trying to import the Orchard package build with clicktobuild.cmd using the deploy menu item through IIS Manager.

After the wizard displays the steps in the installation, I receive the following error: 'enable32BitAppOnWin64' is not a valid attribute of the deployment object 'createApp'.

The problem was already discussed at http://orchard.codeplex.com/discussions/243011/ and changing the manifest.xml to

<iisapp path="Orchard" managedRuntimeVersion="v4.0" enable32BitAppOnWin64="False" managedPipelineMode="Integrated" />

solves the problem.

comments

sebastienros wrote Aug 21, 2012 at 10:06 PM

Fixed in changeset 732db5ec5d16

sebastienros wrote Oct 31, 2012 at 12:20 AM

The change broke the deployment on Azure gallery, so I am reverting it for the moment for vNExt

sebastienros wrote Oct 31, 2012 at 12:21 AM

Maybe putting the enable32BitAppOnWin64 to true could fix both platforms

sebastienros wrote Nov 6, 2012 at 8:08 PM

Can you check if the suggested fix is working

IntranetFactory wrote Nov 6, 2012 at 8:54 PM

I'm not sure if this can be a solution at all - from my understanding switching enable32BitAppOnWin64 on means that apppool / Orchard will not run as a 64 bit application but with just 32 bit. Do we want this? Is everything tested with just 32 bit?

arbitrix wrote Jul 23, 2013 at 5:39 AM

This also manifests in Orchard 1.7 RC from

https://orchard.codeplex.com/downloads/get/705173

Error when importing in IIS Manager:

'enable32BitAppOnWin64' is not a valid attribute of the deployment object 'createApp'

sebastienros wrote Aug 9, 2013 at 7:50 PM

Could you provide some detailed repro steps ?

More specifically I'd like to know what version of Windows and IIS you are using, and how you deploy it.

arbitrix wrote Aug 29, 2013 at 8:46 PM

I originally encountered this on IIS7 (not 7.5) on Windows 2008 (not R2) with the then-latest MS web deploy installed. Since I'm out of office I can't get you exact details at the moment but it basically involves the workflow under the heading "DEPLOYING THE PACKAGE USING IIS MANAGER" on the following page:

http://www.iis.net/learn/publish/using-web-deploy/building-a-web-deploy-package-from-visual-studio-2010

I manually edited the deployment .zip file and added the missing 'enable32BitAppOnWin64' and 'managedPipelineMode' attributes, which allowed the import to proceed.

sfmskywalker wrote Mar 28 at 12:28 AM

Fixed in changeset 0a27c698fef6b25c78f65a3b3c167ed7ba86b86c