Exchange 2007 Export-Mailbox Error Message on only certain mailbox

Sunday, March 02, 2008 5:41 PM

0

I have searched high and low for a solution to this, but no such luck. Hopefully someone has had the same issue and can help me out.

I am attempting to export and then remove a date range for mailboxes before I migrate to an Exchange 07 server. The mailboxes range in the 10 GB range. I am attempting to use the Exchange 2007 cmdlet to do this with due to it does not have a 2 GB limit like the Exmerge of past.

The command I am using is as follows:

[PS] C:\>Export-Mailbox -Identity User -StartDate "01/01/07" -EndDate "01/30/08"
-IncludeFolders "\Inbox","\Sent Items" -PSTFolderPath c:\PST\pst.pst

This command works fine on some of the mailboxes in the Exchange03 system. But on some of the mailboxes I am getting the following error.

Error occurred in the step: Moving messages. Failed to copy messages to t
he destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749164

Any ideas?
- Reply
- Quote

All Replies

Monday, March 03, 2008 4:50 PM

0
Hello,

Moving thread to Exchange Forum. Wrongly posted in the PerformancePoint Forum

Aseem Nayar - MSFT
- Proposed As Answer by ToddSWagner Wednesday, January 28, 2009 6:22 PM
- Reply
- Quote
Monday, March 03, 2008 5:29 PM

0

I have a similar issue with Exchange 2007 SP1

I am attempting to export but not remove a mailbox. I need to create a .pst file on several mailboxes, using the Exchange 2007 - 32bit cmdlet.

The command I am using is as follows:

[PS] c:\export-mailbox -Identity user@domain -PSTFolderPath C:\PSTFolder\user.pst

This command will not work on any mailbox and returns the following error:

Export-Mailbox : Error was found for FName, LName (user@domain) because: Error occurred in the step: Moving Messages. Failed to copy messages to the destination mailbox store with error:

MAPI or an unspecified service provider.

ID no: 00000000-0000-00000000, erroe code -1056749164

At line:1 char:15

+ export-mailbox <<<< -Identity user@domain -PSTFolderPath c:\PSTFiles\user.pst
- Reply
- Quote
Monday, March 03, 2008 5:35 PM

0

Hi there,

Try using the -ExcludeFolders '\Inbox' and I bet you won't get that error. It have found that if I exclude the Inbox from the export that it seems to work ok. We are calling Microsoft today to find a answer a little bit faster than it seems Technet can provide.

I will post anything I find out.

Thx
- Reply
- Quote
Tuesday, March 04, 2008 3:37 AM

0

I am trying to get help with the same issue in this thread,

http://forums.msexchange.org/Powershell_export-mailbox_error_1056749164__SAD_and_STUCK/m_1800467676/tm.htm

This is a nasty issue!!
- Reply
- Quote
Wednesday, March 05, 2008 5:12 PM

0

Hello Chrisgru,

It seems that when our team has contacted Microsoft directly over the issue they have no resolution to this issue. Apparently this is a new bug that no one can seem to figure out. Maybe when SP2 comes out there will be a fix for this issue.

I don't understand how they can put out a product and adverstise different features and it not be able to work like it should.

Thanks for you input.
- Reply
- Quote
Friday, March 07, 2008 7:21 AM

0

Hello Joe Rod (and others)

Thought I'd bring this over as a cross post because no-one seems to be picking it up in the 'admin' section. I believe I'm having a similar issue to yourself, as detailed below:

Hi all,

I've already posted this same question elsewhere, but if anyone here can resolve the issue or suggest a better way (without using archiving software - yet!), I'd be most grateful. I'd even be happy if someone can replicate the problem so I know I'm not going mad... I'm trying to set up a quick & dirty quarter year pst mail archive for one of our users on our Exchange 2007 (SP1) box. Using the command:

export-mailbox -id userA -pstfolderpath \\testpath\test.pst -enddate "01/03/2007"

I come up against this error:

Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an unspecified service provider. ID no: 00000000-0000-00000000, error code: -1056749164

Which I understand is a fairly standard permissions error. Problem is that I know the permissions are set correctly, having tested the function by removing the -enddate parameter; and getting a successful export.

I worked out after a while that the command seems to fall over when it hits a subfolder, so I tested this by using the -includefolders parameter. The command:

export-mailbox -id userA -pstfolderpath \\testpath\test.pst -includefolders '\inbox' -enddate "01/03/2007"

will fail if there are any subfolders under '\inbox'. Add the names of the subfolders:

export-mailbox -id userA -pstfolderpath \\testpath\test.pst -includefolders '\inbox\subfolder1' -enddate "01/03/2007"

and as long as those subfolders don't have any subfolders, I will get a successful export.

Any help appreciated.

Cheers

Dan

If anyone is able to replicate this, please let me know, I'd love to get this sorted. If it is a known problem - can I use someone's PSS contact please?!
- Reply
- Quote
Friday, March 07, 2008 7:31 AM

0

Hello Dan,

Thanks for the input. I did try that very same thing and it does work. But the issue comes back if you try to lets say break them up in years for instance. After the third or fourth run on the same mailbox it will start to fail again.

I do have a trouble ticket in with Microsoft currently and he is setting up a test environment and said he would get back to me with some explanation tomorrow later on in the day. I will get back to you with what the Microsoft support finds out also.

Thanks,

Joe
- Reply
- Quote
Saturday, March 08, 2008 11:04 PM

0

I had this problem withj two user moving from exchange 2003 to 2007, i fixed this adding more space to the user's mailbox.

I had one almost reaching her size (~ 1GB) after adding 1GB it moved with no error

I hope this help!
- Reply
- Quote
Sunday, March 09, 2008 10:29 PM

0

Thanks Joe, I'll look out for your update.

Hello Angel, thank you as well for your suggestion - unfortunately there are no size limits currently imposed.

Regards

Dan
- Reply
- Quote
Sunday, March 09, 2008 10:36 PM

0

I think this is a bug since for some users i had error stating that the user has exceded the their mailbox size, but for this two users (having the same error as you got) i resolved it adding more space...

Confusing...

Angel
- Reply
- Quote
Monday, March 10, 2008 5:28 PM

0
Hello,

Type in PWD

Add-MailboxPermission -Identity AliasMailbox -User UsuarioPermissionFull -AccessRights FullAccess

And after that,

restore-mailbox -id USER -RSGDatabase 'Recovery Storage Group\Mailbox Database'

Ok?
- Proposed As Answer by Andrew M Morton - Oriium IT Support Friday, May 11, 2012 3:49 PM
- Reply
- Quote
Friday, March 14, 2008 6:08 PM

0

huh? Is the "-User" flag specifying the user that should have full access?

Also - no matter what I do I get a 265KB .pst file.

We're trying to archive any terminated users' mailboxes to a .pst file in a secured location via a web utility and need any and all subfolders included. Any help is appreciated.
- Reply
- Quote
Tuesday, March 25, 2008 5:33 PM

17
Here is a more detailed explination. Run this command before you run the import-mailbox command for each user. This has been working for me.

Add-mailboxpermission -identity <mailbox you are importing to> -accessrights fullaccess -user <who you are logged in as when running the exchange managment shell>
- Proposed As Answer by helsby Friday, January 16, 2009 9:34 PM
- Reply
- Quote
Saturday, March 29, 2008 2:45 PM

0

Bingo, give this guy a silver star.

Solved for me anyway, permissions issue.
- Reply
- Quote
Saturday, March 29, 2008 7:17 PM

0

Hello Again,

So if it is a permissions issue, then is there a way to set this up globally? I have 778 mailboxes and do 1 at a time is not very helpful. Is there a global command that you use to do this with? I would like to try it and see if this works.

Thanks.
- Reply
- Quote
Wednesday, April 09, 2008 1:22 PM

0

When I try to command to add premissions I recieved this error message

Add-MailboxPermission : Active Directory operation failed on (domain controller). The supplied credential for 'NETWORK\(my username)' on Bind operation is inval
id. Error Code: 0x31.
At line:1 char:22
+ Add-mailboxpermission <<<< -identity (mail box running the permissions modifaction on) -accessrights fullaccess -us
er (my username)

I obvisouly replaced some of the text in the above message but seems like I may have a bigger problem on hand then just this.
- Reply
- Quote
Friday, April 11, 2008 2:27 PM

0

To: Mbranham

I recieve this error most frequently after I have been logged in to my workstation for more than 24 hours straight. To resolve I just log off and back in again and the problem disappears. I have not researched the issue to find a more suitable fix, but interested if someone has found one.

For Main Topic:
Kuddos to kyBosh! Granting myself full access to the mailbox allowed me to export to PST successfully after receiving that error.
- Reply
- Quote
Friday, April 11, 2008 2:50 PM

0

To: Joe Rod

if you want to give your account full access to all mailboxes here is the cmdlet to run to do it.

don't use the curlies

{Get-Mailbox | Remove-MailboxPermission -User "Your account here" -AccessRights FullAccess}

If you have more than 1000 mailboxes be sure to add "-ResultSize Unlimited" to the Get-Mailbox cmdlet before the Pipe.
- Reply
- Quote

Monday, April 14, 2008 12:49 PM

jwDeaton wrote:

To: Mbranham

I recieve this error most frequently after I have been logged in to my workstation for more than 24 hours straight. To resolve I just log off and back in again and the problem disappears. I have not researched the issue to find a more suitable fix, but interested if someone has found one.

For Main Topic:

Kuddos to kyBosh! Granting myself full access to the mailbox allowed me to export to PST successfully after receiving that error.

jwDeaton

I have tried the restart when i get that error and it usually works. However, that no longer works as a fix for this problem for me. Have tried it mutiple times and still get the same error each time.

Thursday, May 29, 2008 2:25 AM

The size limit was the issue for me. I am trying to migrate to 2007 though. The PST issue is something altogether different.

Tuesday, July 01, 2008 2:21 AM

I was just trying to figure out this exact same problem, and found that the mailbox had an inherited deny on it for all administrative accounts. To work around this I added another permission to the mailbox with the -deny switch set to $false. This finally allowed me access to the mailbox to export it!

Example command:

Code Snippet

add-mailboxpermission -Id "<mailbox>" -User "<admin user account>" -AccessRights FullAccess -Deny:$false

Hope this helps...

Ashley Smith

Proposed As Answer by spyrule Tuesday, March 27, 2012 5:59 PM

Monday, July 14, 2008 1:09 PM

Hey Dan08. if its any consolation I have the exact same situation as you. If I do not include -enddate then it works and does all subfolders however if I include -enddate it fails. If I include -enddate and one of the subfolders it works until it hits a new subfolder.

I've not been able to figure it out. Looking at my permissions they seem fine and if I do not include -enddate it works and exports everything so I can't see how the permissions would be wrong if that works.

Thursday, July 24, 2008 8:41 PM

Silver?
Give this guy a gold star.
Solved for me, too, permissions issue.

add-mailboxpermission -identity <UserName> -accessrights fullaccess -user <ExAdminName>
export-mailbox -identity <UserName> -PSTFolderPath <\\ServerName\ShareName\UserName.pst>

Monday, August 04, 2008 1:57 PM

We had the same problem with the export from mailboxes. In our case was the solution to deactivate the cache modus in outlook. After deactivation the export works fine.

Maybe this information will help.

Greetings

Christian B.

Proposed As Answer by mr.mitsu Wednesday, September 15, 2010 3:12 AM

Tuesday, August 12, 2008 3:52 PM

Still no luck for me, Dan08 are you around? Wondering if you had any luck (is there no way to PM someone on these forums?)

I did figure out if I replace -enddate with -startdate it will work and get the subfolders, it doesn't give me what I need as I want to export old items not new ones but it makes me wonder what the issue really is. Like Dan08 has mentioned it only fails on subfolders, if I include them it will work as long as the subfolders don't have subfolders. Obviously that is a practical way to export as I have no idea what subfolders all the users would have.

Anyone have any further thoughts?

Tuesday, August 12, 2008 10:58 PM

Hello Ben,

Yes, still around - but no nearer a resolution for the issue. To get out of the particular situation I ended up running a manual archive with the Outlook client. (When I said quick & dirty, I didn't mean that dirty)

Does anyone know if it's possible to get some indication from MS if this is a genuine issue, and if so, if a fix is being investigated? If not, how do we go about reporting it?

Cheers

Dan

Monday, August 18, 2008 1:22 PM

Hey,

Glad to hear i'm not the only one. I've found that if i change -enddate to -startdate it works just fine but obviously doesn't give me what I need.

I've found a couple posts stating its an issue and that the workaround is to do a manual export (like you did) but I'm not doing that for all the clients. Or to use exmerge as it can be used with exchange 2k7 which I may end up doing soon. I just wish MS would acknowlege the issue somewhere. An update would be nice....

Thursday, August 21, 2008 7:34 PM

dan08 wrote:

Does anyone know if it's possible to get some indication from MS if this is a genuine issue, and if so, if a fix is being investigated? If not, how do we go about reporting it?

Cheers

Dan

Thats a good point (missed it first time I read it), how would we report this as an issue? Clearly its an issue for more than a couple people. Any MS MVP's or something around here that can assist?

Wednesday, September 17, 2008 5:22 AM

Hi all,

I got same issue,but fix it.

Here is my step

Create a New User account (EX: ExportAdmin)
Add this account to a Exchange Server Administrator Permission Both Source and Target Exchange Mailbox Server
Add this account to Local Administrators Group Member Both Source and Target Exchange Mailbox Server
Make sure this account DO NOT HAVE ANY Domain Admin/Exterprise Admin permission(Just keep Domain User group permission)
Assign Mailbox Full Access to this account by follow Cmdlet
Get-Mailbox -Server "EX-CCR" | Add-MailboxPermission -User ExportAdmin -AccessRights FullAccess
Runas with ExportAdmin account (Open EMC)
Get-Mailbox -Server "EX-CCR" | Export-Mailbox -PSTFolderPath
Done

Monday, October 13, 2008 3:38 PM

i also have the same problem,

i can use -enddate if i choose

(***WORKS***)
10/10/2008
11/10/2008
12/10/2008
13/10/2008

but it (***fails***) on

9/10/2008 ( or anything previous to this date)

and just to note, last backup according to database is 09/10/2008 !!

Server
Exchange 2007 SP1 - Hotfix 4
2003 R2 x64

Powershell Client
2003 R2 x86
Outlook 2007
-
Backup Exec 12

Jtech

Monday, October 20, 2008 12:55 AM

asdfd1111 wrote:

but it (***fails***) on

9/10/2008 ( or anything previous to this date)

and just to note, last backup according to database is 09/10/2008 !!

Was it Sherlock Holmes who said "I think we could be onto something here..."?

Monday, October 20, 2008 8:48 AM

Just thought I would add,

I checked this by running a further full backup and it seems to not make a difference?

I cant think what else I did on this day ( 09/10 ).. nothing I'm sure.

A work around that worked:

Use MRM to move all old emails (+365days) to a managed folder, then run the export-mailbox for that folder ( -enddate ), seems very messy but it worked.

I have no idea what might cause this error.

Wednesday, November 19, 2008 7:54 PM

Thanks kyBOSH for saving my day ;-)

Tuesday, November 25, 2008 4:51 PM

Sorry, the MAPI error code got cut off http://www.study-aids.co.uk so in case anyone else is googling for this here's the real MAPI error:

errorCode="0xc1054005" The MAPI call failed. MAPI or an unspecified service provider. ID no: 80004005-0000-00000000

Please help...

Monday, December 01, 2008 12:06 AM

sounds like there is a design issue with export-mailbox command let ... It requires administrative logon permissions to the mailbox.
has anyone followed up that it's still an issue? Just curious

Tuesday, December 09, 2008 6:14 PM

For any of those that installed update rollup 4 for SP1 has it made any difference? I installed on both the exchange server and the machine I'm running the command from but no luck.

http://support.microsoft.com/default.aspx/kb/951747 states its fixed in rollup 4 but clearly its not.

The only solution so far is to move the mailbox to a new storage group and run it (or move it then move it back and then run) which is really cumbersome and annoying.

Wednesday, December 17, 2008 9:07 AM

Dan

Have you had an answer from MS yet about this, I have the same problem, can export the file great until I add the -enddate parameter and it gives up part way through.

Like others I would like to use this feature for an automated backend mailbox archiving solution, rather than a client solution

Do we know that MS are aware of the bug in the program?

thanks

Kevin

Wednesday, December 17, 2008 9:08 AM

Dan

Have you had an answer from MS yet about this, I have the same problem, can export the file great until I add the -enddate parameter and it gives up part way through.

Like others I would like to use this feature for an automated backend mailbox archiving solution, rather than a client solution

Do we know that MS are aware of the bug in the program?

thanks

Kevin

Friday, January 02, 2009 1:20 PM

Hi

I've just tried an export also using -enddate parameter - I still get the error (with Rollup 5):

Error was found for User Name (user@domain.com) because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749164

Regards
Brian

Brian

Wednesday, January 07, 2009 4:05 AM

Fixed it for me, too. Thanks kyB0SH!

Michael

Friday, January 16, 2009 9:41 PM

Glad to say that kyBOSH's reply worked for me too - thanks a lot. interestingly, this was meant to be fixed in rollup4 but we're on rollup5 and still have this issue.

Wednesday, January 28, 2009 6:23 PM

Outlook on your computer needs to be in online mode and not in cached mode. I just found this out and it works. Thanks Microsoft.

ToddSWagner

Wednesday, February 11, 2009 5:27 PM

Hi Guys,

Thanks for this thread. It really helped me out with the permissions problem.

However, granting a user "-AccessRights FullAccess" is a permanent setting, right?
Let's say somebody uses the Administrator account to import mailboxes and grants FullAccess to all mailboxes... it can access all mailboxes after that, right?

If so, how can you remove the FullAccess for this user, and reset is to the default value. (by the way, what is the default AccessRights for the Administrator user?)

Thanks,

Thursday, March 19, 2009 9:06 PM

FYI - I had this same error message coming up when doing a cross forest migration from exchange 2003 to 2007 using the move-mailbox cmdlet. the issue was that i had removed the default limits which the users well way over but the change did not take effect until i dismounted and mounted the store. once i did that all was fine.

HTH

-Eddie Espino

Thursday, April 23, 2009 3:18 PM

This thread has been hugely helpful in resolving the "MAPI or an unspecified service provider" error I'd originally been getting for all mailboxes. But as with many folks here, I'm now encountering issues when I try to use add [-EndDate "04/21/2009"] to our Export-Mailbox cmdlet call. And it's only happening for some of our mailboxes.

It's not a big deal for me, since I can just do a full export. But it's aggravating to still not have a concise answer on how this his happening and how to fix, despite all of the people who have posted so far.

Thursday, April 30, 2009 12:54 PM

To export mailbox to pst you need Receive-As permission (FullAccess not needed)

The permission can be added for all mailboxes on the database level using the following cmdlet:

Get-MailboxDatabase -identity "Server\Storage Group\Database" | Add-ADPermission -user "Domain\Username" -ExtendedRights Receive-As

Regards,
Wissam

Proposed As Answer by Wissam Harfouche Thursday, April 30, 2009 12:57 PM

Wednesday, May 06, 2009 10:26 AM

Hi All,

I'm getting this error "

1056749164">Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an unspecified service provider. ID no: 00000000-0000-00000000" when i use the move-mailbox cmdlet to move a mailbox from Exch2k3 to Exch2k7. The user does have a storage limit set but the mailbox is not over the set limits. Any idea how i can resolve this issue? Also, is there a switch that i can add to the move-mailbox cmdlet to ignore any mailbox that has reach it's limit and still move it anyway?

Thanks

Dankwax

Monday, September 21, 2009 3:47 PM

MpDay,

not that it helps any but I never did get a resolution for this. I've read that the latest update does fix it but at this point I'm waiting on SP2 and hoping that will fix it. Manually doing the exports have been a pain.

Ben Bechard

Monday, September 28, 2009 7:18 PM

I re-read my post from January and that fixed my problem again. Put Outlook in Online Mode, instead of Cached mode and it will work. You also have to have the permissions as well.

ToddSWagner

Tuesday, May 11, 2010 10:25 PM

Yep, this worked for me as well! Thanks kyBOSH!

Tuesday, June 01, 2010 7:17 PM

After many struggles with this issue we simply add -BadItemLimit with the following command:

Restore-Mailbox -Identity Scott -RSGDatabase MyRSGDatabase -RSGMailbox John -BadItemLimit "0" -TargetFolder Recovery

The user appeared to have too many corrupt items in their mailbox.

Thursday, July 15, 2010 6:30 AM

Thank you vey much Guys,

I was having the issue to export mailbox to PST, but this discussion chain helped me out to resolve the issue.

Regards,

Nadeem Afzal

Tuesday, August 03, 2010 1:08 PM

I have had the same problem with Export-Mailbox

But when I gave the administrators account that I was making the Export with full access to the mailbox the export worked fine.

Monday, August 09, 2010 9:55 PM

i've got this problem as well...

It will fail on 1 out of every 10 or so mailboxes. Moving the mailbox to another storage group seemed to prove as a worthy workaround... but it's such a pain in the

I've updated Exchange to SP1 Rollup 10

I've verified permissions

I've checked cache mode for the user

I've run the export with -baditemlimit switch

Still fails!!

Friday, August 27, 2010 1:52 PM

Since i've been working on this for about a month now i feel the need to share my experience and a workarounds I have successfully used:

If your reading this post I'm sure you already have permissions set correctly but if not... give yourself full access permissions over the mailbox

Get-Mailbox | Remove-MailboxPermission -User "Your account here" -AccessRights FullAccess}

Run the export with the "exclude folders switch" ..... don't export items you don't need. "Junk E-mail" "Drafts" "Deleted Items" ... i found that alot of my exports succeeded after this step.
Run isinteg on the mailbox database.... this did nothing for me but some say it helps.
Run fixmapi on the local XP machine your are running the exports on

Start>Run>cmd>fixmapi.exe

*FIX* set "Deleted Item Retention" to 0 days on the problem mailbox and run online maintenance... THIS IS WHAT FINALLY FIXED IT FOR ME

*Workaround* - Use ExMerge to export the mailboxes. Yes, exmerge will still work with 2007 you just have to have the 2003 management tools installed.
*Workaround* - Move the mailbox out of the database it is in. You can even move it out and then move it back in to the original and it should work.

Apparently what was causing most of my mailboxes to fail were the dumpster items... once online maintenance ran with the deleted item retention set to 0 ... it cleared out all the corrupted items and the exports worked flawlessly.

Hope this works for some of you!

DEMPC

Proposed As Answer by DEMPC Friday, August 27, 2010 1:56 PM
Edited by DEMPC Friday, August 27, 2010 3:26 PM forgot to add the mailbox move workaround

Friday, August 27, 2010 2:47 PM

I had a same problem yesterday. I changed the switch to gigabyte switch and also i rebooted the mail server and make sure all exchange services running. Move mail boxes and all migrated perfectly.

thanks

Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Proposed As Answer by nbhatti Friday, August 27, 2010 3:53 PM

Friday, August 27, 2010 3:27 PM

Hi

I had a same problem yesterday. I changed the switch to gigabyte switch and also i rebooted the mail server and make sure all exchange services running. Move mail boxes and all migrated perfectly.

thanks

Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Yes.. you are right. I forgot to add that.

While this is a painful solution... you can move the mailbox out of the EDB it is in to a new or existing one. This will allow you to run the export.

Monday, August 30, 2010 5:59 PM

Thank you. I gave myself Full Access on Exchange Management Console to the account, that didn't work. So I ran the Add-mailboxpermission command and now I am exporting the mailbox with no problems. Weird...

Friday, December 10, 2010 10:17 AM

I had same problem with Export-Mailbox and this did the trick!

Thanks

Proposed As Answer by AhhhhKOOLFM Saturday, March 05, 2011 2:52 AM
Unproposed As Answer by AhhhhKOOLFM Saturday, March 05, 2011 2:52 AM

Saturday, March 05, 2011 2:59 AM

I experienced the same problem when moving a mailbox from 2003 to 2007 Exchange. After about 1 hour of troubleshooting, the problem was related to a client rule in Outlook. Run the following two commands on the client PC of the user you are trying to migrate. Then try to move the mailbox from within Exchange 2007 again.

"C:\Program Files\Microsoft Office\Office11\Outlook.exe" /Cleanreminders

"C:\Program Files\Microsoft Office\Office11\Outlook.exe" /Cleanfreebusy

Error Example - when moving mailbox in Exchange 2007 SP3, Rollup 2.

Event Type: Error
Event Source: Exchange Migration
Event Category: Move Mailbox
Event ID: 1008
Date:  3/4/2011
Time:  5:57:05 PM
User:  N/A
Computer: XXXXX

Description:
The move-mailbox task for mailbox 'John, Big' failed.
Error: Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000

Sunday, April 17, 2011 11:29 PM

I got exactly the same error "MAPI or an unspecified service provider." as ahhhhKOOLFM, and the fix suggested did not work for me, I experienced the same problem when trying to move a few mailboxes from 2003 to 2007 Exchange

What I eventually discovered is that some mailbox subfolders folders had permissions on, from users that was not even recognised by AD "S-1.xxxX.x.x.x." and only after I checked each folder and reset permission to default I was able to do export to PST.

The only way I could get mailbox to migrate from my exchange 2007 after about 6 or 7 tries on a 15Gb mailbox was to reset most folders, export to PST and leave as little as possible in mailbox, excluding contacts and calendar. Not even mailbox as small as 270Mb can migrate unless permission is reset and export. Lucky it was only two that had the same problem, which happened to be the two users that use a MAC and a iPad.

Wednesday, May 18, 2011 9:51 PM

Perfect Solution

Monday, June 20, 2011 6:49 PM

This is a permissions issue. I have seen this pop up when permissions have not propagated from the top down to the mailbox properly. Go into the mailbox and add the account that needs to have access (Exchange Admins/User/Whatever). Have also noticed that sometimes exchange thinks accounts do not have full access permissions even though the account is listed as having full access. If you remove the account and re-add it, this usually resolves the problem. These are probably all the result of some accidental permission issue set by an admin.

Monday, June 20, 2011 6:52 PM

This is what I found to be the resolution as well. I have found weird issues with exchange security at times where a user is listed as having full access but doesn't really. Removing and adding the user/group back usually resolves the issue.

Monday, August 22, 2011 12:59 PM

I had the same problems, but discovered that the problem for me was lack of space on the destination path. More data than I expected to come out.

Daren

Thursday, September 08, 2011 6:48 AM

Turns out that even if you are an Exchange admin you still need to give yourself permissions to the users mailbox either through the GUI - Right click users mailbox, Manage full access permission or at the Exchange Management Shell -

Add-mailboxpermission -identity <mailbox you are importing to> -accessrights fullaccess -user <who you are logged in as when running the exchange managment shell

Regards,
Imran Khan
Email: imran@dhruvsoftonline.com, support@dhruvsoft.com
Web: www.dhruvsoft.com

Regards, Imran Khan Email: imran@dhruvsoftonline.com, support@dhruvsoft.com Web: www.dhruvsoft.com

Thursday, September 15, 2011 2:52 PM

I strongly urge anyone still having this issue to delete dumpster items for the mailbox.

You can do this by setting deleted item retention on the mailbox to 0 and waiting for the nightly mailbox maintenance to run.

I have run hundreds if not thousands of exports and every time i receive this error one of two things fixes it..

Set Full Access Permissions
Clear Dumpster Items

-DEMPC

Tuesday, January 03, 2012 4:15 PM

I did what KyB0SH suggested but it didnt work for me.

What I did to get it working was to unmount and remount the datastore I was moving the mailbox to and it worked a treat!

Obviously be cautious doing this if you have users on that datastore!

Tuesday, March 27, 2012 3:50 PM

This worked for me! Thanks!

Tuesday, May 08, 2012 3:44 AM

I created this script which worked perfectly for me:

$adminUser = '<Domain>\<User>' # user account running the script
$targetMailbox = '<exchangeMailboxName>' # mailbox to export all messages to
$targetFolder = '<FolderName>' # Folder to save exported messages in
$searchString = '<SearchKeywords>' # Search string for exporting messages
$searchDatabase = '<Database>' # Exchange Database to search for messages

$mailboxes = get-mailbox -Database $searchDatabase

foreach ($mailbox in $mailboxes)
{
	$mailbox | Add-MailboxPermission -AccessRights fullaccess -User $adminUser -Confirm:$false
	$mailbox | Export-Mailbox -SubjectKeywords $searchString -TargetMailbox $targetMailbox -TargetFolder $targetFolder -Confirm:$false
	$mailbox | Remove-MailboxPermission -AccessRights fullaccess -User $adminUser -Confirm:$false
}

Edited by Bunta126 Tuesday, May 08, 2012 3:50 AM

Exchange 2007 Export-Mailbox Error Message on only certain mailbox

All Replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support by product

Other support links

Not an IT pro?