asked on

Exchange 2007 OWA errors

I have browsed all over the net and have not found a solution yet, so let me ask.

Windows 2008 Std Server
MS Exchange 2007

OWA was working but now it is not.

Event Application log:
Event ID 2274
ISAPI Filter C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll could not be loaded due to a configuration problem. The current configuration only supports loading images for a x86 processor architecture.

Event ID 2268
Could not load all ISAPI filters for site 'DEFAULT WEB SITE'. Therefore site startup aborted.

I have done the:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

solution, but it did not fix anything.

I am not an Exchange engineer, nor an IIS expert. I am just wondering what the heck I can do to get rid of this error so my OWA site can load.

Thanks

MichaelVH

Hi there,

1. shouldn't that be:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true ?
If you ran the command from the command-line; what was the output?

2. did you restart IIS after running the command?

Grts,

Michael

tcampbell_nc

ASKER

I have seen people recommend setting it to true(1) and False(0). Microsoft's site (which is talking about aspnetfilter) states that if you have MS Exchange 2007 installed, this should be set to false.

After running the cscript, it returns:

Enable32bitAppOnWin64 : (boolean) False

(By the way, I just tried to set it to true, but I still received the same event errors in the app log)

Yes, I did restart IIS after every run of this command.

Thanks

MichaelVH

Could you verify the event viewer and come up with an specific error number (0x....)?

tcampbell_nc

ASKER

There is no 0x error number in the event view Application log.

MichaelVH

And how about when you open OWA-page (with the error) and click the details?

ASKER CERTIFIED SOLUTION

tcampbell_nc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tcampbell_nc

ASKER

This fixed the problem in my case. It may work for others, so I want to have it posted on EE. This seems to be a common error with many possible causes.