Solved

Failed to create Exchange OAB Folder

Posted on 2014-02-08
3
1,258 Views
Last Modified: 2014-02-14
Hello,
I am stuck in my migration from Windows 2008 SBS to Windows Essentials 2012 with an on premise Exchange 2013 server.  I have installed my new Essentials server and my new Exchange 2013 server (both or created in VMware on separate hardware from the SBS 2008 server).  My problem now is OWA and removing the Exchange 2007 server.

I see through posts and comments that the ARRconfig command that I need to run as a part of the rerouting of mail.domain.com for OWA access won't complete successfully until the Exchange server is integrated with the Essentials server which won't complete successfully until the Exchange 2007 server is uninstalled.

I have migrated the mailboxes to 2013 and the public folders to 2013 but now when I try and uninstall Exchange 2008 it hangs on moving the OAB.  The error I get is

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00


Default Offline Address Book
Failed

Error:
Failed to create the 'ExchangeOAB' folder on the target server 'PPM-EXCHANGE'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform this operation. Error message : 'Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))'.

Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

Exchange Management Shell command attempted:
move-OfflineAddressBook -Identity '\Default Offline Address Book' -Server 'PPM-EXCHANGE'

Elapsed Time: 00:00:00

I have restarted the Microsoft Exchange Message Assistant service but still no joy.  Can someone help me move past this point so I can try to complete the rest?

Thanks soo much!
0
Comment
Question by:blkfoot
  • 2
3 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 39845358
Lots of possible answers on this forum thread.
http://forums.msexchange.org/m_1800468241/tm.htm
0
 

Accepted Solution

by:
blkfoot earned 0 total points
ID: 39845377
Thanks.  I did come across that in all of my research but none of that helped.  The customer I am working with only has 20 employees so I deleted the OAB and created a new one on the new server.  After that I was able to remove Exchange.
0
 

Author Closing Comment

by:blkfoot
ID: 39858519
I was able to resolve this myself by deleting the OAB.  This was a time sensitive issue for the client.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
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
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 from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

789 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