Haha, I just ran into this one. You can enable and disable 32-bit emulation mode with this command (all on one line):
CSCRIPT %systemdrive%\inetpub\admi
The argument "zero" at the end of this command is important, as it turns 32-bit mode off. You can run the same command with a "one" to turn it back on.
It will return the following text:
enable32bitapponwin64
You might also need to re-register 64-bit ASP.NET.
- Change directory to C:\Windows\Microsoft.NET\F
ramework64 \v2.0.5072 7 - Run the command: ASPNET_REGIIS -i -enable
- it will return the following text: Finished installing ASP.NET (2.0.50727)
Note: you can switch back to 32-bit ASP.NET by changing directory to C:\Windows\Microsoft.NET\F
Now, as to the question of whether these two apps (i.e. vendor solution and WSS x64) can co-exist on the same IIS instance, I can't say. Give it a try, but if the vendor says they won't support their software if it's running in x64 mode, then you should believe them. Always err on the side of supportability, especially if you are not, as you say, an IIS expert.
You might follow Steve_NJ's suggestion and simply use the 32-bit version of WSS, which would not block the installation if you're running in 32 bit emulation mode.





by: Steve_NJPosted on 2009-04-27 at 04:32:06ID: 24240669
Have you tried installing the 32 bit version of WSS? Not the bet option and I'm not sure it'll work. In reality I'd suggest moving the 3rd party application to a VM or something and reinstalling everything so you can use WSS as 64bit. Next version won't be 32bit so it would save you having to upgrade it later.