Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.
If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.
When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:
You may also want to review the installation or upgrading documentation.
Hi all,
I've been looking stuff up like crazy ever since this happened and so far, I've not found anything really useful. I went to test out mojo Portal's installation via Web Deployment tool under IIS 7.0 on Windows Server 2008 R2 with Mojo Portal version 2.3.6.5, and during the installation process, I was halted by this error: "Enable 32 bit app on Win 64 is not a valid attribute of the deployment object create app." The error came right after the step of where to install the application. I was unable to proceed further with it to the database step (which is MSSQl Server 2008 ExpressR2). I tried solving the problem by going to the properties of the application pool and changing the Enable 32 bit on Win 64 property to true. This didn't seem to do anything in this situation. I tried again, and got nothing but the same error in the same place. I can't remember now whether I restarted the app pool or not. I think I did, but that didn't do any good. What am I missing? And is this a common incompatibility between 32 bit and 64 bit applications with the Web Deployment tool? If you need more info, don't be afraid to ask. Thanks so much for any and all feedback and assistance.
Katherine
Unfortunately this is some kind of bug in IIS, it happens with any .NET 4 package when you use the "Import Application" link in IIS, but the same file works fine from the Web App Gallery.
Best,
Joe
I kind of figured it was something like that. Do you know if Microsoft is aware of it? Should I mention it over at the IIS board?