Solved

Exchange 2007 OWA errors

Posted on 2011-02-22
7
1,625 Views
Last Modified: 2012-05-11
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
0
Comment
Question by:tcampbell_nc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 11

Expert Comment

by:MichaelVH
ID: 34955679
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


0
 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34955827
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
0
 
LVL 11

Expert Comment

by:MichaelVH
ID: 34956330
Could you verify the event viewer and come up with an specific error number (0x....)?
0
SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

 
LVL 1

Author Comment

by:tcampbell_nc
ID: 34956506
There is no 0x error number in the event view Application log.

0
 
LVL 11

Expert Comment

by:MichaelVH
ID: 34958396
And how about when you open OWA-page (with the error) and click the details?
0
 
LVL 1

Accepted Solution

by:
tcampbell_nc earned 0 total points
ID: 34963259
I think that the problem is solved.  I performed another google search on the text "The current configuration only supports loading images for a x86 processor architecture', and eventually found the following web site:

http://www.m86security.com/KB/KnowledgebaseArticle12671.aspx

This site deals with a similar issue with a third party mail program called Marshall Mail.  Luckily, I read through the article.

The following lines caught my attention:

In the file %windir%\system32\inetsrv\config\applicationhost.config:

change the line
       <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
        path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true"  />

to the following
        <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
        path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />

change the line

        <filter name="Exchange ActiveSync ISAPI Filter"
        path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true"   />

to the following

        <filter name="Exchange ActiveSync ISAPI Filter"
        path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true"  preCondition="bitness64" />


I performed these two changes, stopped and restarted IIS Server, and OWA launched successfully.

This change appears to have had no adverse effects on any other process in the server.  The Application Log errors have ceased.  The users can access OWA.  Mail is flowing.

I will leave this topic open for a few more days to see if anyone has any negative comments regarding this fix.  If anyone can see anything wrong with thix fix, please let me know.

Thanks
0
 
LVL 1

Author Closing Comment

by:tcampbell_nc
ID: 35067651
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.
0

Featured Post

Is Your DevOps Pipeline Leaking?

Is your CI/CD pipeline a hodge-podge of randomly connected tools? You’ve likely got a tool to fix one problem & then a different tool to fix another, resulting in a cluster of tools with overlapping functionality. Learn how to optimize your pipeline with Gartner's recommendations

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
A phishing scam that claims a recipient’s credit card details have been “suspended” is the latest trend in spoof emails.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question