New-MailboxExportRequest remains "queued" at 0%

Greetings, my mailbox exports are going into "queued" status, and remain at 0% complete even after many hours.
This is occurring on every mailbox which we've tried to export (about a dozen so far), and they are scattered across all 16 of our DBs.
It was working fine in December, and we've been trying for months to find out why it stopped working.
The environment is 2x CAS/HT front-ended by an F5 appliance, and a two-member DAG with a FSW.  All servers are at Exchange 2010 SP3 RU5.
This is my command line:
New-MailboxExportRequest -verbose -Mailbox '<<mailboxname>>' -Name '<<exporttaskname>>' -BadItemLimit 999 -AcceptLargeDataLoss -ExcludeDumpster -FilePath '\\<<fqdn>>\Mailbox-Exports\<<filename>>.pst'
Which results in this ---
[PS] C:\>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Name Status SourceAlias PercentComplete
<<mailboxname>> Queued <<exporttaskname>> 0
...and the value in the PercentComplete does not increment, even when hours have passed.
MAPI is enabled on the mailbox.  All of the DBs are mounted or healthy.  We've rebooted all of the servers. We've restarted the replication service on all the servers. We've made sure the "MRSConfiguration" settings in MSExchangeMailboxReplication.exe.config
are at their defaults.  There's nothing odd in the system or application logs.
Here are the results of a status check ...
[PS] C:\>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics |fl
RunspaceId : bef8d2d9-4c7c-4dad-85c0-b7d4a6f4b5c1
Name : <<mailboxname>>
Status : Queued
StatusDetail : Queued
SyncStage : None
Flags : IntraOrg, Push
RequestStyle : IntraOrg
Direction : Push
Protect : False
Priority : Normal
Suspend : False
FilePath : \\<<fqdn>>\Mailbox-Exports\<<filename>>.pst
SourceAlias : <<mailboxname>>
SourceIsArchive : False
SourceExchangeGuid : 87945c65-ea8a-4a5c-808b-c35bb598d163
SourceRootFolder :
SourceVersion : Version 14.3 (Build 181.0)
SourceMailboxIdentity : <<ou+username>>
SourceDatabase : DB008
TargetRootFolder :
TargetVersion : Version 0.0 (Build 0.0)
IncludeFolders : {}
ExcludeFolders : {}
ExcludeDumpster : True
ConflictResolutionOption : KeepSourceItem
AssociatedMessagesCopyOption : DoNotCopy
BatchName :
ContentFilter :
ContentFilterLanguage :
BadItemLimit : 999
BadItemsEncountered :
QueuedTimestamp : 4/1/2014 10:57:02 AM
StartTimestamp :
LastUpdateTimestamp : 4/1/2014 10:57:03 AM
CompletionTimestamp :
SuspendedTimestamp :
OverallDuration : 01:57:04
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 01:57:04
TotalInProgressDuration :
TotalStalledDueToHADuration :
TotalTransientFailureDuration :
MRSServerName :
EstimatedTransferSize : 0 B (0 bytes)
EstimatedTransferItemCount : 0
BytesTransferred :
BytesTransferredPerMinute :
ItemsTransferred :
PercentComplete : 0
PositionInQueue : 7/7 (Position/Queue Length)
FailureCode :
FailureType :
FailureSide :
Message :
FailureTimestamp :
FailureContext :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : e60a43ca-a6de-438c-84b7-25a65c3ad26d
RequestQueue : DB008
Identity : RequestGuid (e60a43ca-a6de-438c-84b7-25a65c3ad26d), RequestQueue: (e90cea03-d8da-4870-b
1f9-95afcf6d2038)
Report :
[PS] C:\>
Has anyone else run into this problem and been unable to resolve it?

[PS] C:\Windows\system32>New-MailboxExportRequest -Verbose -Mailbox '**mailbox**' -Name '**exportrequest**' -BadItemLimit 999 -AcceptLargeDataLoss -ExcludeDumpster -FilePath '\\**fqdn**\Mailbox-Exports\**mailbox**.pst'
VERBOSE: [15:20:59.458 GMT] New-MailboxExportRequest : Active Directory session settings for 'New-MailboxExportRequest'
are: View Entire Forest: 'True', Configuration Domain Controller: '**fqdn**', Preferred
Global Catalog: '**fqdn**', Preferred Domain Controllers: '{
**fqdn** }', User Preferred Global Catalog: '**fqdn**', Preferred
Domain Controllers: '{ **fqdn** }'
VERBOSE: [15:20:59.473 GMT] New-MailboxExportRequest : Runspace context: Executing user: **domain**/Admin
Accounts/Admin **ME!**, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [15:20:59.473 GMT] New-MailboxExportRequest : Beginning processing &
VERBOSE: [15:20:59.473 GMT] New-MailboxExportRequest : Instantiating handler with index 0 for cmdlet extension agent
"Admin Audit Log Agent".
WARNING: When an item can't be read from the source location or can't be written to the target location, it will be
considered corrupted. By specifying a non-zero BadItemLimit, you're requesting that Exchange not copy such items to the
target location. When the request is complete, such corrupted items won't be available at the target. When the source
is deleted, these items will be completely lost.
VERBOSE: [15:20:59.567 GMT] New-MailboxExportRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [15:20:59.614 GMT] New-MailboxExportRequest : Searching objects "**mailbox**" of type "ADUser" under the
root "$null".
VERBOSE: [15:20:59.614 GMT] New-MailboxExportRequest : Previous operation run on global catalog server
'**fqdn**'.
VERBOSE: [15:20:59.629 GMT] New-MailboxExportRequest : Rereading object "**domain**/**ou**/**ou**/**account**" of type "ADUser" under the root "CN=**account**,OU=**ou**,OU=**ou**,DC=**domain**,DC=COM".
VERBOSE: [15:20:59.629 GMT] New-MailboxExportRequest : Previous operation run on domain controller
'**fqdn**'.
VERBOSE: [15:20:59.645 GMT] New-MailboxExportRequest : Searching objects "DB008" of type "MailboxDatabase" under the
root "$null".
VERBOSE: [15:20:59.645 GMT] New-MailboxExportRequest : Previous operation run on domain controller
'**fqdn**'.
VERBOSE: [15:20:59.692 GMT] New-MailboxExportRequest : [DEBUG] MDB e90cea03-d8da-4870-b1f9-95afcf6d2038 found to belong
to Site: **domain**/Configuration/Sites/**site**
VERBOSE: [15:20:59.692 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: attempting to connect to
'**cas**.**domain**'
VERBOSE: [15:20:59.739 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: connected to '**cas**.**domain**',
version 14.3.178.0 caps:07
VERBOSE: [15:20:59.785 GMT] New-MailboxExportRequest : Processing object "RequestGuid
(492b4d0c-1982-4f94-b7c5-603c5383cdcf), RequestQueue: (e90cea03-d8da-4870-b1f9-95afcf6d2038)".
VERBOSE: [15:21:00.565 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:Validate.
VERBOSE: [15:21:00.565 GMT] New-MailboxExportRequest : Admin Audit Log: Exited Handler:Validate.
VERBOSE: Creating mailbox export request 'RequestGuid (492b4d0c-1982-4f94-b7c5-603c5383cdcf), RequestQueue:
(e90cea03-d8da-4870-b1f9-95afcf6d2038)'.
VERBOSE: [15:21:00.581 GMT] New-MailboxExportRequest : Resolved current organization: .
VERBOSE: [15:21:00.581 GMT] New-MailboxExportRequest : [DEBUG] 4/3/2014 10:20:59 AM [**cas**]
'**domain**/Admin Accounts/Admin **ME!**' created request.
VERBOSE: [15:21:00.597 GMT] New-MailboxExportRequest : [DEBUG] 4/3/2014 10:20:59 AM [**cas**]
'**domain**/Admin Accounts/Admin **ME!**' allowed a large amount of data loss when moving the mailbox (999 bad items).
VERBOSE: [15:21:00.612 GMT] New-MailboxExportRequest : Saving object "RequestGuid
(492b4d0c-1982-4f94-b7c5-603c5383cdcf), RequestQueue: (e90cea03-d8da-4870-b1f9-95afcf6d2038)" of type
"TransactionalRequestJob" and state "New".
VERBOSE: [15:21:00.643 GMT] New-MailboxExportRequest : [DEBUG] Updating Index/ADUser data for RequestJob 'RequestGuid
(492b4d0c-1982-4f94-b7c5-603c5383cdcf), RequestQueue: (e90cea03-d8da-4870-b1f9-95afcf6d2038)'.
VERBOSE: [15:21:00.815 GMT] New-MailboxExportRequest : Previous operation that ran on:
'**fqdn**'.
VERBOSE: [15:21:00.815 GMT] New-MailboxExportRequest : Reading new object "RequestGuid
(492b4d0c-1982-4f94-b7c5-603c5383cdcf), RequestQueue: (e90cea03-d8da-4870-b1f9-95afcf6d2038)" of type
"TransactionalRequestJob".
VERBOSE: [15:21:00.862 GMT] New-MailboxExportRequest : Previous operation that ran on:
'**fqdn**'.
Name Mailbox Status
**mailbox** **domain**/**ou**/**ou** Queued
VERBOSE: [15:21:00.971 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [15:21:00.987 GMT] New-MailboxExportRequest : Admin Audit Log: Exited Handler:OnComplete.
VERBOSE: [15:21:01.002 GMT] New-MailboxExportRequest : Ending processing &
[PS] C:\Windows\system32>

Similar Messages

  • New-MailboxExportRequest Stuck in QUEUED and 0% no solutions work

    Hello,
    i have been trying for two weeks to export a user's mailbox with the following cmdlet:
    New-MailboxExportRequest -Mailbox [email protected] -FilePath \\servername\c$\users\ADMINISTRATOR\desktop\exports\username.pst
    It stays hung at Queued and 0% status.  No matter what I do, it does not move past that.
    I have tried the following after looking through the forums.
    Get-MailboxExportRequest |Get-MailboxExportRequestStatistics
    Name                                   Status                   
    SourceAlias                           PercentComplete
    MailboxExport                        Queued                   
    USERNAME                             
    0
    Test-ReplicationHealth
    Server          Check                      Result     Error
    EXS01           ReplayService              Passed
    EXS01           ActiveManager              Passed
    EXS01           TasksRpcListener           Passed
    I stopped and started the following services on my 2 CAS server and 2 Exchange Servers:
    EX and EXS servers--Microsoft Exchange Replication
    CAS Servers---Microsoft Exchange Mailbox Replication
    No Change
    I rebooted all of my mail servers....no change.
    Tried a different user....same results...nochange
    tried exporting to a different location...no change
    tried the export request on different mail servers...no change
    I am extremely tired of losing this battle for something that should be such a simple process.  Any help or suggestions would be greatly appreciated. 
    Thanks
    Cheston

    Belinda,
    I created a new MDB and attempted to do a MoveRequest for the mailbox.  It also hung in QUEUED and 0%.
    I didn't know the answer to your DAG question, but I did look and found no DatabaseAvailabilityGroups listed.
    I ran it with a -BadItemLimit parameter...no change.  below is the report.
    [PS] C:\Windows\system32>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics -IncludeReport  |fl
    RunspaceId                    : 534b8de7-4ac8-41fa-b1ae-47c52a3d30ba
    Name                          : MailboxExport
    Status                        : Queued
    StatusDetail                  : Queued
    SyncStage                     : None
    Flags                         : IntraOrg, Push
    RequestStyle                  : IntraOrg
    Direction                     : Push
    Protect                       : False
    Suspend                       : False
    FilePath                      : \\ex01\pstback$\USERNAME.pst
    SourceAlias                   :
    USERNAME
    SourceIsArchive               : False
    SourceExchangeGuid            : f4ada6c7-a574-4003-8fd8-c4e8d20e2821
    SourceRootFolder              :
    SourceVersion                 : Version 14.1 (Build 289.0)
    SourceMailboxIdentity         : DOMAIN.COM/OU OF EMPLOYEE/USERNAME
    SourceDatabase                : Employee
    TargetRootFolder              :
    TargetVersion                 : Version 0.0 (Build 0.0)
    IncludeFolders                : {}
    ExcludeFolders                : {}
    ExcludeDumpster               : False
    ConflictResolutionOption      : KeepSourceItem
    AssociatedMessagesCopyOption  : DoNotCopy
    BatchName                     :
    ContentFilter                 :
    ContentFilterLanguage         :
    BadItemLimit                  : 100
    BadItemsEncountered           :
    QueuedTimestamp               : 7/31/2014 9:32:43 AM
    StartTimestamp                :
    LastUpdateTimestamp           : 7/31/2014 9:32:43 AM
    CompletionTimestamp           :
    SuspendedTimestamp            :
    OverallDuration               : 00:12:51
    TotalSuspendedDuration        :
    TotalFailedDuration           :
    TotalQueuedDuration           : 00:12:51
    TotalInProgressDuration       :
    TotalStalledDueToHADuration   :
    TotalTransientFailureDuration :
    MRSServerName                 :
    EstimatedTransferSize         : 0 B (0 bytes)
    EstimatedTransferItemCount    : 0
    BytesTransferred              :
    BytesTransferredPerMinute     :
    ItemsTransferred              :
    PercentComplete               : 0
    PositionInQueue               : 1/1 (Position/Queue Length)
    FailureCode                   :
    FailureType                   :
    FailureSide                   :
    Message                       :
    FailureTimestamp              :
    FailureContext                :
    IsValid                       : True
    ValidationMessage             :
    OrganizationId                :
    RequestGuid                   : d03f9afd-202d-4ce0-80b6-6352bf21669a
    RequestQueue                  : Employee
    Identity                      : RequestGuid (d03f9afd-202d-4ce0-80b6-6352bf21669a),
                                        RequestQueue: (f233259e-d404-4aff-b35e-a4137218f895)
    Report                        : 7/31/2014 9:32:43 AM [EX01] 'DOMAIN.COM/Users/Administrator' created request.
                                    7/31/2014 9:32:43 AM [EX01] 'DOMAIN.COM/Users/Administrator' allowed a
    large amount of data loss when moving the mailbox (100 bad items).

  • What is the max number of New-MailboxExportRequest that can be InProgress at the same time?

    I haven't been able to find an answer for this, so I'm hoping someone can clarify off the top of their head.
    If you queue up a large number of New-MailboxExportRequests, how many of them can be "InProgress" at once? I'm assuming there is an upper limit on the number that will be processed, with the others remaining queued.
    As a follow up, is that default number something you can modify?

    Hi,
    The default maximum simultaneous move requests is different for each parameter:
    MaxActiveMovesPerSourceMDB
    MaxActiveMovesPerTargetMDB
    MaxActiveMovesPerSourceServer
    MaxActiveMovesPerTargetServer
    To override the default value, you can refer to the article provided by Josh above. Even though this article is for Exchange 2010, these values in Exchange 2013 are exactly the same ones set by default in Exchange 2010, Exchange 2013 follows them.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • New-MailboxExportRequest questions

    I'm hoping someone might be able to clarify a couple of questions on New-MailboxExportRequest:
    1. How many export request can be in progress at the same time, by default? For example, if an administrator creates export requests for 1000 mailboxes, how many will be queued versus in progress?
    2. A 10 GB mailbox is exported. One week later, another export request is generated for the same mailbox, which has gained an additional 50 MB of data. The export is pointed to the same PST used for the original 10 GB. Will the second export complete in
    a more timely fashion since most of the content will not have changed from the original 10 GB export?

    Hi,
    Please find below answers of your questions.
    1. In Exchange 2013, the maximum concurrent move request are 20 and i believe it's the same as of Export Request.
    2. No, it will take the same time as it took before for exporting the mailbox.
    Kindly mark this as answer if found helpful. thanks.
    Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365
    Many thanks!

  • What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

    Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
    How can i do export mailbox to pst file in exchange 2013 SP1?

    You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
    Follow the steps given below in order to export the mailboxes into PST file
    1. Open the Exchange Console and run:
    New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
    This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
    You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
    restarted. Now move to the next steps.
    2. Assign “Mailbox Import Export” role to it.
    3.  Add Desired Users to Role Group
    4.  Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
    5. Run PS New-MailboxExportRequest
    6. Monitor New-MailboxExportRequest
    Verify PST File has been created on the network Share and you are done.
    If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
    use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

  • Removing mailbox (Remove-Mailbox) right after mail export to PST request (New-MailboxExportRequest)

    Hi all,
    I have a PowerShell script for archiving employee mailboxes after they leave the company. The script uses WinRM to connect to Exchange CAS where it:
    exports user mailbox to PST files (New-MailboxExportRequest -Mailbox $user -FilePath $USER_ARCH\mail\MAIL_$user.pst)
    export user archive mailbox to PST file (New-MailboxExportRequest -Mailbox $user -isarchive -FilePath $USER_ARCH\mail\Archive_$user.ps)
    delete user mailbox (Remove-Mailbox $user
    These 3 steps are executed one after another. Since New-MailboxExportRequest is asynchronous (only creates requests and exists), the
    Remove-Mailbox is triggered right after the request is submitted. Since PST file is not created or is truncated, I believe
    Remove-Mailbox actually removes mailbox even though there is active request for that mailbox. Logically the mailbox with bound active requests should not be removed and there should be warning.
    I know there are many possible workarounds. Just want to know if this is by design or am I missing an option to above commands?
    Best regards,
         Blaz

    The same happens in Exchange 2010 making this seem like it is by design.  I can find no reference as to how to avoid this other than by changing your script.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • New-MailboxExportRequest -ContentFilter {size -gt 10KB} Invalid filter syntax

    I would like to export massages of a mailbox, where mail item or attachment or anything is larger then XXKB
    New-MailboxExportRequest
    -Mailbox "User1"
    -FilePath "\\server1\pst\User1.pst"
    -ContentFilter {size
    -gt 10KB}
    The provided ContentFilter value is invalid. ContentFilter is invalid. Invalid filter syntax. For a description of
    the filter parameter syntax see the command help.
    "size -gt 10KB" at position 12. --> Invalid filter syntax. For a description of the filter parameter
    syntax see the command help.
    "size -gt 10KB" at position 12.
    + CategoryInfo         
    : InvalidArgument: (size -gt 10KB:String) [], ContentFilterInvalidPermanentException

    Build is CU5.
    I did not try other parameters.  I`m looking how to find and remove e-mail massages grater then 25MB, because users do not clan there mailboxes. They ignore warning, ect. And to cover my »arsh«, priory moving massages to O365, i will do
    export to PST, then delete and delete dumpster.  But simple task like mailbox search, eDiscovery does not 
    search  by size.
    That does not work eider :
    -SearchQuery "Size -gt 2024KB"
    "Size > 1024KB"
    'Size:>1024KB'
    "Size:>1024",

  • New-mailboxExportRequest exports the entire folder in spite of filter conditions

    Hi there,
    got an issue with exporting mailboxes,
    script below exports entire inbox folder rather than just emails in the mentioned time frame
    $export_date= [datetime]"10/29/2014 12:00:00 AM"
    New-MailboxExportRequest -FilePath \\server\export\matthew.pst -IncludeFolders "#inbox#" Mailbox matthew_2014 -ContentFilter {( received -ge $export_date) }
    already checked the value of $export_date it returns the right datetime value

    Hi Mcmilad,
    Try this and let me know if it works.
    I removed the var with direct input, just to check if its working now for you.
    The script shot above has missing hypen before -Mailbox parameter, And I have changed -gt instead of -ge
    New-MailboxExportRequest -FilePath \\server\export\matthew.pst -IncludeFolders "#inbox#" -Mailbox matthew_2014 -ContentFilter {(Received -gt "10/29/2014") }
    New-MailboxExportRequest -FilePath \\server\export\matthew.pst -IncludeFolders "#inbox#" -Mailbox matthew_2014 -ContentFilter {(Received -lt '11/29/2014') -and (Received -gt '10/29/2014')}
    Filterable properties for the -ContentFilter parameter:
    http://technet.microsoft.com/en-us/library/ff601762(v=exchg.150).aspx
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • New-MailboxExportRequest - All mailboxes between defined range

    Environment: Exchange 2010, Update Rollup 6 for Exchange Server
    2010 SP1
    I am looking over the knowledge base for this cmdlet (http://technet.microsoft.com/en-us/library/ff607299.aspx) and I'm unable to determine if I can use this for all mailboxes on
    all of our databases.
    We had an issue with our mail archiving system and they were not able to capture all of the emails between 8/8/2013 and 8/14/2013. The messages are still on the exchange server for the time being. So I want to export that range into a network share in case
    anyone comes to us asking for an email between those dates. We are essentially making our own copy to "CYA."
    What I see in ever google result that uses the above command is it being used to export one mailbox. Can anyone help me with the syntax on the cmdlet to capture everyone between the dates above?

    Hello Toobar,
    Here is solution for you........
    Step 1: Add the Mailbox Import Export Role to a Role Group .
    New-ManagementRoleAssignment -Name "Import Export_YourGroupName" -SecurityGroup "YourGroupName" -Role "Mailbox Import Export"
    http://technet.microsoft.com/en-us/library/ee633452(v=exchg.141).aspx
    Step 2 :  Create the  Mailboxes.csv file , include all user's mailbox Alias in this file as below  and save in C: drive ( path may be different)
    Alias
    user1
    user2
    Step 3:   Create the Shared folder (ex -
    \\server01\PSTShare ) and grant read/write permission to the group Exchange Trusted Subsystem to the network share where you'll export  mailboxes.
    Step 4:  save file below script as Export.ps1 in C: drive ( path may be different)
    $mailboxes=import-csv c:\mailboxes.csv
    foreach($mailbox in $mailboxes)
    New-MailboxExportRequest -Mailbox $mailbox.alias -ContentFilter {(Received -lt "08/15/2013") -and (Received -gt "08/07/2013")} -FilePath "\\server01\PSTShare\$mailbox.alias.pst"
    step 5 : Go to EMS , C drive  and run the  .\export.ps1  script.
    it will export all mailbox's included in  mailboxes.csv list.
    You are done .
    Cheers  !

  • New-mailboxexportrequest error file could be locked

    try to export pst to a unc path- works locally
    Permisssion set on share per ms docs.
    was hoping to run script per OU but cant get one to work.
    [PS] C:\>New-MailboxExportRequest -FilePath "\\servername\TEST\user.pst" -MRSServer "cas-b0x" -mailbox user
    The server or share name specified in the path may be invalid, or the file could be locked.
    + CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
    + FullyQualifiedErrorId : 914C862C,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    Hi Totalnet,
    I would like to clarify the following things for troubleshooting:
    1. The user account that you use to run the cmdlet needs to be part of Windows domain and must have permissions granted to the "Exchange Trusted Subsystem" group.
    2. You can create only one export request at a time per .pst file. This is because the .pst file is locked as in-use when the request begins to run.
    3. If the issue persists, I recommend you use a local shared folder to see if it works.
    What's more, here is a thread for your reference.
    Backing up mailboxes via PST files
    http://social.technet.microsoft.com/Forums/exchange/en-US/bfa645e0-6196-4c79-a3e2-8264b2e85eb1/backing-up-mailboxes-via-pst-files?forum=exchangesvrgenerallegacy
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2010 SP3 RU6 - Problems with New-MailboxExportRequest

    New-MailboxExportRequest seems to ignore -ExcludeFolders and -IncludeFolders and export the entire mailbox. For example:
    New-MailboxExportRequest -IncludeFolder TestExport -Mailbox TestUser -FilePath \\SomeUNCPath\test.pst
    will exportsthe entire contents of the mailbox. I believe this used to work before, but it is possible I have lost my mind. 
    The folder TestExport is on the root, as in, if you were to run Get-MailboxFolderStatistics, the FolderPath is /TestExport. I've also tried using -ExcludeFolders to exclude every other folder with no luck.
    Any confirmation of an issue or help is appreciated. 

    Hi,
    From your description, I recommend you use the following cmdlet to check the result.
    New-MailboxExportRequest -IncludeFolders "#Inbox#" -Mailbox TestUser -FilePath
    \\SomeUNCPath\test.pst
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • New-MailboxExportRequest fails

    I'm running Exchange 2010 SP1 Enterprist edition.  I have never had a problem exporting mailboxes to pst files in the past.  However, I can't export them any longer.  I start the export, and it runs fine for a long time, and it seems that
    it's going to work.  However, it ends up in a Failed state.  There aren't any application logs being generated.  Are there log files in another location I can check?
    thank you
    JScott2

    So, I finally got one of many mailboxes exported successfully.  I had to run the following syntax: New-MailboxExportRequest -Mailbox username -FilePath
    \\servername\pst\username.pst -baditemlimit 200 -AcceptLargeDataLoss
    But, the exported pst file is over 4gb in size.  However, the user's mailbox is only showing that it's 200mb, and this particular user has a 500mb mailbox quota.  How can the export be so much larger than the actual mailbox size?
    thanks
    JScott2

  • New-MailboxExportRequest gives PSTs which need repairing

    Hi,
    We're currently exporting a large number of mailboxes to PST in preparation for an Office 365 migration using the New-MailboxExportRequest command as follows: New-MailboxExportRequest -Mailbox $username -ContentFilter {Received -lt $date } -BadItemLimit
    50 -FilePath \\servername\archives -MRSServer CAS1
    This works however the archives contain a large number of corrupt items (in the hundreds) and need to be repaired using PST repair tool.
    How can we prevent this from happening?
    Thanks,
    Bryan

    Hi,
    First of all, New-MailboxExportRequest cmdlet will not cause items corruption.
    We can set the BadItemLimit parameter to more than
    50 with AcceptLargeDataLoss
    parameter. The valid input range for this parameter is from
    0 through 2147483647. If we set the value to more than 50, the value should be around the number according to the numbers of corrupt items. But
    any corrupted items aren't available after the process is complete. Apart from this, there is no way to prevent New-MailboxExportRequest from giving PSTs which need repairing based on my knowledge.
    If these corrupt items are very important, I don’t recommend this operation. And I suggest to use PST repair tool to repair corrupted items after we use New-MailboxExportRequest function.
    Best Regards.

  • Deleted Playlists Reappear New Playlists Remain Local ONLY

    I've been having issues when enabling iTunes Match on my iPhone 6 Plus.
    That is to say, my playlists are in disarray, in completely random locations (not in the folder structure on my Mac).
    I then proceeded to delete & re-create each playlist from scratch on my Mac.  However when updating iTunes match all my deleted playlists re-appeared.  The new replacements I created (with new names) remained on my laptop, but when I re-enabled iTunes match on my phone, nothing had changed at all (all existing playlists remained in the same places, un-deleted, new playlists did not exist).
    I then (after doing some searching) proceeded to delete the playlists from my iPhone instead.  This worked (they were removed from my Mac), however, since the new playlists I created on my Mac seem to be remaining local ONLY, I now have no working playlists on my phone.
    Anybody have any idea how to fix this?  It's really annoying and I don't believe I'm doing anything incorrectly on my end.

    Wonderful, its fixed! Thank you so much.
    I hope everyone get the fixes they need.
    My Pod is like my bike, my car, or my guitar. If its not working, I can't think properly until its fixed. Thanks again, I really appreciate the help.
    cheers

  • New-MailboxExportRequest -ContentFilter Issues

    Hello,
    Recently I've been working with the ContentFilter switch with the New-MailboxExportRequest command (part of Exchange Management Shell).  The command seems to work on a very basic level and even properly if the filter user the "All" parameter. 
    The problem comes in when using either "To" or "Sender" parameters within the ContentFilter where everything ends up getting excluded.  I've seem several people refer to this issue, but never a solution.  Is this a bug in Exchange
    2010 SP3?
    Just for reference, my syntax is:
    New-MailboxExportRequest -Mailbox '[email protected]' -ContentFilter {Sender -eq '[email protected]'} -FilePath 'Valid UNC Path'
    Most people seem to suggest using -like instead of -eq, but that doesn't seem to work and according to MS at http://technet.microsoft.com/EN-US/library/ff601762%28v=exchg.141%29.aspx , this is not a valid operator for 'To' and 'Sender'.
    Does anyone know of any workarounds to this that would get the same results?
    Thanks.

    Hi,
    I have some tests in my environment using Exchange 2010 SP3. I recommend you use the following cmdlet to achieve your goal.
    New-MailboxExportRequest -Mailbox amy02 -ContentFilter {(sender -eq "[email protected]")} -FilePath "\\mail\test\1.pst"
    Please change the amy02 to your mailbox name, change the "[email protected]" to your sender's email address and change the "\\mail\test\1.pst" to your file
    path.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for