Home / server / Questions / 259592
Accepted
SynerCoder
Asked: 2011-04-15 03:38:37 +0800 CST

IIS7 migrating from 32bit to 64bit problems

  • 772

We are currently in the progress of migrating multiple sites from a x86 win 2008 to a x64 win 2008. We have copied the config dir from and wwwroot's from the old server to the new server but when we start the server we get a 503 error page and in the event log are 5 warnings and then a error.

Warning:

A listener channel for protocol 'http' in worker process '2060' serving application pool 'SiteAppPool' reported a listener channel failure.  The data field contains the error number.

The xml of the event:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" /> <EventID Qualifiers="32768">5139</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-04-14T11:10:04.000Z" /> <EventRecordID>334493</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>WEBSRV64</Computer> <Security /> </System> <EventData> <Data Name="AppPoolID">SiteAppPool</Data> <Data Name="ProcessID">2060</Data> <Data Name="param3">0</Data> <Data Name="ProtocolID">http</Data> <Binary>7E000780</Binary> </EventData> </Event>

We get 5 of those but all with a different worker process number.

After that we get this error:

Application pool 'SiteAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

We have absolutely no clue why this error happens,, we did an 1 on 1 copy of the site. Currently we are still running on the 32 bit server but we like to migrate asap. Does anyone have a clue why we get this error?

migration iis-7 application-pools x86-64

2 Answers

  1. Best Answer

    Could be a lot of things but a few things jump to my mind :

    • Was the old site using a different ID for the application pool, perhaps a local machine user? If so, it could be something internal to the application itself that isnt handling the new ID properly.
    • Is the proper version of the .Net Framework installed on the new machine?
    • Have you compared the old and new application pools point-by-point using the Advanced Settings view?

    If you create a new site/application pool and accept the default settings, does it still do this for the new site?

    • 1

  2. It's likely a component in your site that isn't compatible with x64. It could be an isapi filter or possibly some managed code or a COM+ call.

    If it fails right away for an http request then it's likely an isapi filter. You can confirm by disabling all filters and testing a test.html page. Then add things back until it fails again.

    You have 2 solutions:

    • Easiest: run your app pool in 32 bit mode. That's a good setting anyway. You can set it from the app pool advanced properties, one of the top options. Set it as an app pool default and future app pools will also be set that way. In IIS7, you can leverage the high memory of x64 while still running app pools in 32-bit mode.
    • Alternately, once you narrow down the component in question, get an update from the vendor.
    • 0