I have an old .NET application which has some code that needs to be run in 32 bit mode. It is set to an application pool of v2.0 version Integrated pipeline mode.
On the local deployment server (Win 2008 R2 / IIS 7)
When the Enable 32 bit applications was set to True, the site immediately failed with a
503 Service unavailableerror. If I don't have this property to true, then the application fails with "Not a valid win32 application.", so obviously I need to make the above property to True. So after setting it to True and getting the
503 Service unavailableerror, something must have not refreshed properly inside and stopped and started the application pool. It did not help. I also recycled the application pool and it didn't help either. So I logged off the box (as it was not under my control) and tried after a while and to my pleasant surprise, the site opened up without any errors.
So in this situation, I really don't know at what point the site started working as it should with the property set to True.
Later in the day, I published the site to our staging server (Win 2008 R2 / IIS 7 External Host)
I set the property to true and got the
503 Service unavailableerror again. I started and stopped, recycled the application pool and it was of no use again. So I even restarted the server (as it was under my control). Even after the restart, I get the same
503 Service unavailableerror.
I am yet to resolve this problem. This site http://evonet.com.au/503-service-unavailable-errors-when-iis-running-in-32-bit-mode-on-64-bit-windows-server-2008/ suggests that
IIS seemed stuck in 32-bit compatibility mode after I enabled 32-bit application support, which then caused all my IIS worker processes to fail
and has an IIS admin script at the end of the article. I am not sure if this can be run directly without affecting anything else. Is is recommended or am I also missing something else?