[Webinar] Streamline your web hosting managementRegister Today

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

Failed to create Exchange OAB Folder

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
blkfoot
Asked:
blkfoot
  • 2
1 Solution
 
Gareth GudgerCommented:
Lots of possible answers on this forum thread.
http://forums.msexchange.org/m_1800468241/tm.htm
0
 
blkfootAuthor Commented:
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
 
blkfootAuthor Commented:
I was able to resolve this myself by deleting the OAB.  This was a time sensitive issue for the client.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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