paullawrie
asked on
OWA 2007 - Server Error in '/owa' Application
Hi, I have Exchange 2007 Standard Edition installed on x64 Windows Server 2003 R2. It was a fresh install with IIS and Sharepoint services installed beforehand. The server is also a DC with all FSMO roles and is a GC.
Exchange seems to be fine, but OWA refuses to work. I seem to have a dotnet error:
---------------------
Server Error in '/owa' Application
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad3 64e35' or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)
Source Error:
[No relevant source lines]
Source File: web.config Line: 51
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
---------------------
Line 51 appears to be <add assembly="Microsoft.Exchan ge.Data,
The rest of the parameters follow on the next line.
I have uninstalled and reinstalled the client access role twice, fiddled with IIS permissions and NTFS permissions until blue in the face, and also reinstalled IIS and tried a repair on the .net framework.
Right now I'm back to a vanilla install with the same error and I'm about fresh out of ideas.
Exchange seems to be fine, but OWA refuses to work. I seem to have a dotnet error:
---------------------
Server Error in '/owa' Application
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad3
Source Error:
[No relevant source lines]
Source File: web.config Line: 51
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
---------------------
Line 51 appears to be <add assembly="Microsoft.Exchan
The rest of the parameters follow on the next line.
I have uninstalled and reinstalled the client access role twice, fiddled with IIS permissions and NTFS permissions until blue in the face, and also reinstalled IIS and tried a repair on the .net framework.
Right now I'm back to a vanilla install with the same error and I'm about fresh out of ideas.
Have you reinstalled the dot net 2.0 distro pkg? it sound like a .net error. do you have 1.1 on here? You have to make sure that only 2.0 x64 is on or it will wipe out the OWA functionality.
Its possible your IIS has reverted to usign 32 bit .net, try running the following commands and see if it helps.
cscript %SYSTEMDRIVE%\inetpub\admi nscripts\a dsutil.vbs SET W3SVC/AppPools/Enable32bit AppOnWin64 0
%SYSTEMROOT%\Microsoft.NET \Framework 64\v2.0.50 727\aspnet _regiis.ex e -i
cscript %SYSTEMDRIVE%\inetpub\admi
%SYSTEMROOT%\Microsoft.NET
ASKER
I have tried IIS is 32 and 64 bit modes with no luck. In 32bit mode the error changes to a simple "Service unavailable".
Shawshanked, I have never installed 1.1 ... this was a clean install of R2. I also performed a repair of the 2.0 installation which didn't help.
Shawshanked, I have never installed 1.1 ... this was a clean install of R2. I also performed a repair of the 2.0 installation which didn't help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
awesome! I just totally uninstalled Sharepoint 2.0 and everything worked first go. A bit annoyed that I hadn't already tried that... but seeing as how 2.0 is an optional included component of R2 I figured it was a safe bet it wasn't that at fault :/
Thanks...
Thanks...
This did it for me as well!!! Thank you!
It would be nice if Microsoft would tell you that thier products break each other when you install the defaults!
It would be nice if Microsoft would tell you that thier products break each other when you install the defaults!