Oab Url 500 Internal Server Error
Contents |
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 test oab exchange 2010 2010 infrastructure. I was using ADMT to migrate the users and Exchange Prepare-MoveRequest.ps1 and New-MoveRequest an error occurred while opening the microsoft exchange offline address book files CMDlets to move the mailboxes between forests. The migrations were successful, but for some reason the Offline Address Book would not download
Microsoft Exchange Offline Address Book 0x8004010f
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 my OAB was still showing the old company’s GAL. When I
Offline Address Book Connecting To Microsoft Exchange
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 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 exceeds target quota (1) May 24, 2013 Exchange 2010 Public Folder Management Console Error (0) June 28, 2013 Export-AutoDiscoverConfig – Logon Failure: unknown user name or bad password (0) May 26, 2014 Export-AutoDiscoverConfig(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: OAB Problems Previous Versions of Exchange > Exchange Previous Versions - Outlook, OWA, POP, and IMAP Clients Question 0 Sign in to vote Hi all, I'm having some OAB issues.Working online with the Exchange server allows users to see the full GAL, but no one is getting their OAB udpates, so working from the OAB results in missing/incorrect information. I've done the following to troubleshoot: -Looked at the .oab files on my system, whichwere all modified 5/18/2011. I even deleted them and tried to redownload, but to no avail. http://andywolf.com/exchange-2010-offline-address-book-oab-will-not-download/ -Looking inthe database server's ExchangeOAB share
2, 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 https://blogs.technet.microsoft.com/brenle/2015/05/02/http-500-internal-server-error-when-logging-into-exchange-2013-exchange-control-panel-ecp/ attempting to log in to ECP:
The first question I ask when I get these specific cases is "Does the admin account have a mailbox"? In pretty much every http://www.confusedamused.com/notebook/oab-never-downloads-for-outlook-2007-clients-with-exchange-2007-on-server-2008 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 microsoft exchange 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 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 offline address book 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 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