[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1402
  • Last Modified:

OWA permission problem after SP2 installation - event 65

After installing SP2, the owa page will not load.  Outlook works fine.  I have checked container and user permissions, reinstalled IIS and CAS, and re-created the virtual directories.  Anyone have any ideas as what to try?  Here is the OWA error message:

Request
Url: https://tsb0020.tsb.k12tn.net:443/owa/auth/error.aspx?replaceCurrent=1&url=https%3a%2f%2ftsb0020.tsb.k12tn.net%2fowa%2f
User host address: 10.1.2.15

Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance of an object.

Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication()
Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)

Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance of an object.

Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders(ADSystemConfigurationSession session, ADObjectId[] pfdbIds, Boolean& allLegacy, Boolean& allLater)
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
0
ses0511
Asked:
ses0511
  • 6
  • 5
1 Solution
 
LegendZMPrincipal Security ArchitectCommented:
SP2 changes the name of the site, when you change it back it should work...
0
 
ses0511Author Commented:
Thanks.  I have not tried to rename owa, only reinstall from 2007 SP2.  Do you know what would have been the name under 2007 SP1?  As far as I know, I had all the defaults.  The current name is "default web Site".  Is this done directly in IIS?  Would you mind sumerizing this process?
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
LegendZMPrincipal Security ArchitectCommented:
0
 
ses0511Author Commented:
Legend, Yes, I have already done this for all the exchage virtual directories.  I still get the same result.  Thanks.
0
 
LegendZMPrincipal Security ArchitectCommented:
When you uninstalled the CAS role did it uninstall successfully?

Try to uninstall the CAS role, and uninstall IIS from windows roles.

Reinstall IIS, then the CAS role.
0
 
ses0511Author Commented:
Yes, it uninstalled correctly.  I uninstalled IIS and then uninstalled CAS, rebooted, installed IIS, rebooted, and then installed CAS and rebooted.  After that I remapped the owa directories using get-owavirtualdirectories and everything seem to work fine.  I have done this twice.  You said unistall CAS and then IIS.  Do you think it matters that I uninstalled IIS before uninstalling CAS?

0
 
LegendZMPrincipal Security ArchitectCommented:
It's possible... Try uninstalling CAS then IIS and reinstall IIS then CAS without rebooting, see what happens.
0
 
ses0511Author Commented:
OK, I think I found the problem.  My DC's are Server 2008 R2.  Even though I found a technet article stating that Exchage SP2 will be compatable with Server 2008 R2, it looks like that hasn't happened yet.  Do you know differently?  Also, I konw that I can't downgrade, but do you know a link to step by steps to uninstall Echange SP2 and reinstall Sp1?  
0
 
LegendZMPrincipal Security ArchitectCommented:
DC's can be 2008 R2 as long as exchange isn't installed on that DC...
0
 
ses0511Author Commented:
I called Microsoft and after about 12 hours with them on phone support (with remote desktop assistance) and trying a number of things including uninstall and reinstall, they figured out that there were some errors in active directory.  After using ADSI edit, we manually made several additions, and owa started working again.  Turns out, the issue started a couple of years ago after upgrading from exchange 2003 to 2007.  It didn't surface until the exchange SP2 upgrade and SP2 referenced some objects that weren't necessary before.  I have to say Microsoft was very knowledgable and very helpful.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now