Another problem with export-mailbox to pst
Hi,I try to use the cmdlet export-mailbox to pst.(I always do export after using the add-mailboxpermission to give full access )with this command :export-mailbox -identity $login -pstfolderpath c:\test\export.pst....Export isOK, no errorwhen I use:export-mailbox -identity $login -pstfolderpath c:\test\export-diff.pst -StartDate 2009/03/01...Export begins, but stop/end with error:MAPI ou fournisseur de services non spcifi.N ID : 00000000-0000-00000000, code d'erreur : -1056749164But, the exported pst is successfully created, and seems to have all the emails from the request date and later.Alsothe error message seems to be a false warning !?Could someoneconfirm (export ok with false warning)or is the error real ?configuration:windows 2003x64 exchange 2007 SP1 update rollup 6export from windows 2003 32b + outlook 2007 + exchange admin tools (2007 SP1 update rollup 6)Thanks
April 1st, 2009 6:20pm

Looks like it is a fake message that Export-Mailbox throws though it does its work. Not sure if that is because of Windows Server 2003 32 Bit, did not check if that could be a problem. But on technical part of this... The error code -1056749164 translates into JET_wrnNyi (ESE98 Code) which further translates into "The function is not yet implemented". The other part of the same error is MAPI_DIAG_NO_DIAGNOSTIC which is considered to be a value of a property PR_NDR_DIAG_CODE whichhas nothing to do with export mailbox I believe.I can think of looking at logs located at <ExchangeRoot>\Logging\MigrationLogs\ and seeif they can help for the diagnosing the problem.May be that gives you some directives to dig into it further. Bottomline is dont worry about though it throws an error :-)MMilind Naphade
Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2009 7:10pm

Bad news, it's not a false warning :(I do more tests , and carefully review messages exported in the destination PST file:- when export-mailbox stop while exporting INBOX, all subsequent folders are empty- when I use "-startdate 2009/04/01", some messages received on 2009/03/30 are exported !? (maybe -startdate don't use the received date we can view in outlook, but use another (hidden?) date from another MAPI prorerty ? Or maybe-startdate is a little buggy ?)Log files in <ExchangeRoot>\Logging\MigrationLogs\ don't show more info (only the same error code -1056749164 and MAPI ID 00000000-0000-00000000)Googling "export-mailbox PST error code -1056749164" show a lot of items. I feel not alone with my errors :)....but no solution yet.When I use different mailbox as source for the export-mailbox, I always see the same behavior :without "-startdate" everyting go fine, with "startdate" I always get an error...grrrrrr !I will continue to do some testsThanks for any advices, ideas...JM
April 3rd, 2009 1:43am

Well, what I wrote earlier was all based on my previous experience related to that error code. This used to happen with ExMerge several times. I think I will research on it again and get back to you, meanwhile you can wait for others to comment on it. Hopefully, someone finds it faster than me ;)Thanks for the update though :)MMilind Naphade | MCTS:M | http://www.msexchangegeek.com
Free Windows Admin Tool Kit Click here and download it now
April 3rd, 2009 10:17am

JM, This seems to be a permission issue. Suggest you to create a new user account, do NOT add into Domain, Enterprise or Admin groups. Give just below permission required for Export-Mailbox. Exchange Server Administrator role for the source server and the target server Local Administrators group for the source server and the target server Full access to the source mailbox. You can also add -Verbose switch into your Export-Maibox cmdlet to troubleshoot further becuase it gives you detail of each and every steps of cmdlet and you can identify at which stage it gets error. Also make sure that you are running Exchange on latest SP & UR. Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
April 3rd, 2009 5:38pm

Hi,I allready use a account with no domain admin permission but with exchange organizational admin and server admin rights.I don't have a "target server". I want to export from Exchange to PST files.I allready use -verbose and -debug : this options don't give more info about this error.I don't think it's a permission issue because :export-mailbox -identity $login -pstfolderpath c:\test\export.pst : works OKexport-mailbox -identity $login -pstfolderpath c:\test\export.pst -startDate $someDate : don't work.If permissions are problematicthen the first command (without '-stardate') won't work too.Thanks for your comment....Another ideas ?jm
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2009 11:51am

Hey JM,I tried to repro this issue but seems like it didnt go the way I wanted. Probably I am missing on something. Can you please tell me what does "$login" means in your command? I dont know what that is but I guess the -Identity support AliasSimple Mail Transfer Protocol (SMTP) addressDisplay nameParameters only.Thanks,MMilind Naphade | MCTS:M | http://www.msexchangegeek.com
April 10th, 2009 5:09pm

Hi,Yes $login represente the alias of the user mailbox. ( In our setup alias = windows username)Thanksjm
Free Windows Admin Tool Kit Click here and download it now
April 10th, 2009 6:19pm

Alright! Thanks,What happens if you run the command as below:Export-Mailbox -identityalias -pstfolderpath "c:\test\" -StartDate "2009/03/01". Things to note here are, do not specify the name for the target PST file and enclose parameter values for -PSTFolderPath and -StartDate.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com
April 10th, 2009 7:39pm

Guys we are having the same problem i can not use Export-Mailbox with a Startdate or EndDate without getting the same error was this ever resolved?
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2009 5:37pm

Hi,No. No solution for me. I'm not working on exchange in the last month, so i don't now if latest rollup change something...I'm back in business now with upgrade to exchange 2007 SP2 and exchange 2010, and i probably try againt this export-pst/stardate task.jm
November 3rd, 2009 7:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics