locked
Force IIS 7 to run in full 32 bit mode. RRS feed

  • Question

  • User-1395258269 posted

    A little background information first. 

    Our company has a .NET WebApp that I coded and we've been using/selling for quite a while. The original server it was on was running Windows Server 2003 on a 32 bit machine with IIS 6.0.

    We recently purchased a new server that has Windows Server 2008 64 on a 64 bit machine and runs IIS 7.0.

    Surprisingly enough, I was able to port everything over very smoothly except one thing.

     A third party DLL is giving my nightmares (Chase's Paymentech for taking payments).  It's basically just acting extremely strange.  Every time I invoke the DLL, upon postback, ALL of the current session information for the user is dropped.  I tried a couple of workarounds but they give me even stranger behavior.

    I currently have the app pool configured to enable 32 bit apps, but it doesn't seem to be much good.

     Interestingly enough, when I debug on the machine locally with Visual Studio 2005, everything works fine, no errors at all.

     I noticed when debugging, if I check the System Processes, the debug server is running in full 32 bit mode, whereas IIS 7 is running in 64 bit mode, but enabling 32 bit app pools.

     **************

     Is there a way to configure IIS 7 to run in full 32 bit mode on 64 bit Server 2008?  I can't seem to find much information out there other then showing you how to just enable the 32 bit app pool. 

    And if not, I guess the next thing to do would be to try Windows Server 2008 32 bit.

     ****************

    Any and all help is appreciated!

    Tuesday, October 21, 2008 1:50 PM

Answers

  • User511787461 posted

    If the app-pool is set to 32-bit mode, the worker process is completely 32-bit - WAS/W3SVC/iisadmin services would still be running 64-bit though.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, October 23, 2008 2:43 PM

All replies

  • User1073881637 posted

    Not really, even though the app pool is running 32 bit mode, the worker process is processing stuff in native 64 bit.  You should either A) load Hyper-V and create a 32 bit instance of W2k8 or B) reload with 32 bit version of w2k8. 

    Thursday, October 23, 2008 12:10 PM
  • User511787461 posted

    If the app-pool is set to 32-bit mode, the worker process is completely 32-bit - WAS/W3SVC/iisadmin services would still be running 64-bit though.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Thursday, October 23, 2008 2:43 PM
  • User1073881637 posted

    Thanks Anil for the clarification.  That helps!

    Friday, October 24, 2008 12:25 PM
  • User-1395258269 posted

     I reinstalled with Windows Server 2008 32 bit and I'm still getting the same behavior of .NET losing all session information after invoking the DLL.

    What's even more frustrating is that it works when I step through the code using Visual Studio 2005.

    So now, does anyone know why it's working with the Visual Studio Development Server and not IIS 7?  Are there any major discrepancies between the two? 

    Friday, October 24, 2008 4:58 PM
  • User1215323965 posted
    We have the exact same problem in the same environment.We have had specialists on iis and asp.net coders work for hours to try to resolve this issue. If you check Server Manager > Roles > Web Server (IIS) the log has a 5009 event ID - A process serving application pool [DOMAIN NAME](domain)(2.0)(pool)' terminated unexpectedly. The process id was '****'. The process exit code was '0xffffffff'.
     
    Did anyone ever find a resolve for this?
    Wednesday, February 8, 2012 6:10 PM