Oab Error 500
Contents |
the OAB using the Outlook 2007 or Outlook 2010 this article may be useful for you. Problem description When you try to download the OAB using Menu Tools -> Send/Recive -> Download Address Book you don't see the name of OAB in
Test Oab Exchange 2010
the drop down list. Diagnostics Firstly you have to check if the Autodiscover is configured an error occurred while opening the microsoft exchange offline address book files properly. You can use a Test E-mail AutoConfiguration wizard (Hold CTRL and right click the Outlook icon in the System Tray). You should see
Microsoft Exchange Offline Address Book 0x8004010f
the list of URL addresses. If the Autodiscover return an error you have to configure this service correctly (the configuration of the Autodiscover is out of scope of this article) If the XML is displayed you need to find the offline address book connecting to microsoft exchange OAB URL that looks similar to: https://yourservername.yourdomain.tlddomain/oab/guidnumber. Notice: The OAB address can be found in both "Protocol: Exchange RPC" and "Protocol Exchange HTTP" sections. The first one is for internal clients who are accessing the OAB from LAN and the second is for external clients who are accessing the OAB from the Internet. If one of the OAB URLs is empty or wrong, correct the configuration using set-OABVritualDirectory cmdlet. If everything is right then copy the OAB URL and try to open it using your Web Browser You probably will see the error 500 - Internal Server Error (Figure 1) Figure 1 In this situation check the following settings: Is the Web-Based distribution enabled? Organization Configuration -> Mailbox -> Offline Address Book tab -> display your OAB Properties -> Distribution tab -> Enable Web-Based distribution must be enabled. There has to be at least one Client Access Server on the list. If the settings are correct go to the next point. Using IIS Manager Console check if an OAB subfolder exists and contains a folder which name is a GUID. You should see a lot of files in this GUID subfolder. Check this on each CAS. Have you created the redirection to simplify the Outlook Web App URL, like in this articlehttp://technet.microsoft.com/en-us/library/aa998359.aspx? If yes go to the next point. Did you remove the redirection from virtual folders? If yes go to the solution. Solution When you configure Http Redirection a web.config file is created in the OAB directory. This file has incorrect permissions. Assign Read and Read & Execute permission to Autheticated Users group then restart IIS using iisreset /noforce. Now you can try to download the OAB using Outlook. It may be required to download it twice because sometimes the name of the OAB doesn't appear at first try. Notice: When you are trying to open the OAB URL from Web Browser you will get "
been using Exchange 2007, but the acquired company has been using Exchange 2010. The primary company was in the midst of a 2010 rollout, so I thought I would migrate all the users to the Exchange 2010 infrastructure. I was using ADMT to migrate the users and Exchange Prepare-MoveRequest.ps1 and New-MoveRequest CMDlets to move the mailboxes between forests. The migrations were successful, but for some reason the Offline Address Book would not download after the user was migrated. I thought this was an ADMT issue, but I found that it was an Exchange 2010 bug. Initial indication was that http://unified.swiatelski.com/2011/02/exchange-2010-cannot-download-offline.html my OAB was still showing the old company’s GAL. When I tried to manually download the address book, it would either never finish or give me the following error: Task ‘Test_Migration@domain.com’ Reported error (0x80072F0D): ‘Unknown Error 0x80072F0D’ The first thing I checked was that autosdiscover was working properly. When I checked the Test Email Auto-Configuration, everything looked correct. I found the internal and external URL’s. When I tested the http://andywolf.com/exchange-2010-offline-address-book-oab-will-not-download/ internal URL (add /oab.xml to URL), I found something strange. I received a 500 – Internal Server error. This definitely didn't look right to me. When I checked the oab.xml on the acquired company’s environment, the XML loaded fine. The issue ended up being with a rogue web.config file on one of the database servers on the primary companies Exchange 2010 servers. At one time, they had configured friendly URL’s for Outlook Web App. Apparently, there are permission problems on the /oab/web.config file. To resolve the OAB download issues, all I needed to do was give Authenticated Users Read and Read&Execute permissions. Now when I browse to Internal URL/GUID/oab.xml, everything looks fine. Note, if you don't append oab.xml, then you will see a 403 error. This is normal. Now when I manually try to download the Offline Address Book, everything works as expected: I thought that the issue was with ADMT or the Exchange Migration, but in the end it was simply an Exchange 2010 bug that the web.config did not have the appropriate permissions. Be Sociable, Share!
Tweet Related Posts: May 24, 2013 Customizing the Outlook Address Book (0) June 28, 2013 Migrating Exchange Mailbox from another Forest – Mailbox exce2, 20153 Share 0 0 Over the past several months, I've seen an increased number of Exchange 2013 cases where certain admin users received a 500 status error when attempting to log in to ECP:
The first question I ask when I https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ get these specific cases is "Does the admin account have a mailbox"? In pretty much every case that I can remember, the response is "No". And immediately, I know exactly where to look! A little history… As you may know, because of the design of Exchange 2013 - the CAS role simply locates your mailbox, then proxies the request back to your mailbox server - an "anchor mailbox" is used. This anchor mailbox is microsoft exchange simply your Exchange GUID, and is used for a number of reasons in Exchange 2013 connectivity. The most obvious, though, are: As mentioned above, so that an Exchange 2013 CAS knows what mailbox server to proxy a request to To prevent the 'Your administrator has made a change so you must restart Outlook' message that you get when a mailbox is moved to a different site. You can see evidence of the anchor mailbox offline address book when you configure an Outlook profile for an Exchange 2013 mailbox: Notice the ExchangeGuid is used as the 'Server' in the outlook profile, instead of an actual server name. OK that's great and all, but what does that have to do with thisstatus 500that I'm getting? Well, let's think about it. If the Exchange 2013 CAS needs to know where to proxy a request, but the request is coming from an account that has no mailbox, and thus no ExchangeGuid associated with it, how does Exchange know which mailbox server to proxy? In instances like this, Exchange 2013 uses the ExchangeGuid of system mailboxes to determine where to proxy the requests. In this specific scenario, Exchange uses the system mailbox SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} Note: When pulling up the system mailbox(es) using Get-Mailbox you must specify the -Arbitration parameter or the command will not work. So how do I fix this? Typically, what I've found is that this is caused by either the database with the system mailbox is unavailable, or some attribute on the system mailbox account has become corrupt or is missing. Many times, this issue is accompanied by another - such as users unable to connect to Exchange, and the 500 error is discovered when the admin attempts to log in to ECP to try and figure