About UnableToReadPSTFolder Error<\/strong><\/p>\n\n\n\n

When you create a PST export request for a specified mailbox by using the New-MailboxExportRequest, the command may fail after a while and display the following problem,<\/p>\n\n\n\n

FailureCode                            : -2146233088
FailureType                            : UnableToReadPSTFolderPermanentException
FailureSide                            : Target
Message                                : Error: Unable to read folder ID \u201833154\u2019. Check the PST file for possible
corruption. \u2013> Heap id type does not match<\/p>\n\n\n\n

If you check the log, the end of the log file may look like this:<\/strong><\/p>\n\n\n\n

xx\/xx\/201x 12:13:04 PM [SERVER] Fatal error
UnableToReadPSTFolderPermanentException has occurred.<\/p>\n\n\n\n

How to Prevent Error UnableToReadPSTFolder?<\/strong><\/p>\n\n\n\n

When New-MailboxExportRequest failed to respond or export the PST, then it is usually presumed that the user may have missed out on the complete request or error occurred due to a typo. But even after creating the same mailbox export request several times, if the user gets the same error, then there is an issue with PowerShell command. It could occur due to the following reasons,<\/p>\n\n\n\n

1. Mailbox size is quite large, let\u2019s say 90 GB, and hence Mailbox Request is unable to export mailbox to PST<\/li>
2. Mailbox Import Export RBAC management role is not assigned to the user account. If the RBAC Management role is not assigned, then you can\u2019t create a mailbox export request<\/li><\/ol>\n\n\n\n

   Also, before reaching to any conclusion, verify the following:<\/p>\n\n\n\n

   1. View Detailed Statistics Report<\/strong><\/li><\/ol>\n\n\n\n

      Check the export request status to find out what caused the problem.<\/p>\n\n\n\n

      • Try to export mailbox to another folder<\/strong><\/li><\/ul>\n\n\n\n

        If the Exchange user can export mailbox to PST in another folder, then the problem is with the current mailbox permissions.<\/p>\n\n\n\n

        • Check if the mailbox is broken<\/strong><\/li><\/ul>\n\n\n\n

          Try exporting another large mailbox to the same folder. If it works, then the issue is with that particular mailbox. In that case, verify if the mailbox is broken or it is too large, say more than 50 GB (maximum size limit of PST file).<\/p>\n\n\n\n

          In most cases, there is an issue of oversized mailbox. You may resolve such issue by splitting the PST file by using the following PowerShell command.<\/p>\n\n\n\n

          New-MailboxExportRequest -Mailbox XYX -ContentFilter {(Received -ge \u201c01\/01\/2017\u2033) -and (Received -lt \u201c01\/01\/2018\u201d)} -FilePath \u201c\\\\SERVER21\\PSTFileShare\\XYZ.pst\u201d<\/code><\/pre>\n\n\n\n
          You can change the comparators in PowerShell command with any of the following to split the PST file accordingly,<\/p>\n\n\n\n
          -eq<\/td>
          equal to<\/td><\/tr>
          -ne<\/td>
          not equal<\/td><\/tr>
          -gt<\/td>
          greater than<\/td><\/tr>
          -ge<\/td>
          Greater than or equal to<\/td><\/tr>
          -lt<\/td>
          less than<\/td><\/tr>
          -le<\/td>
          less than or equal to<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
          In case this doesn\u2019t work, follow the steps discussed below to export mailbox to PST from Exchange database and avoid the UnableToReadPSTFolder error.<\/p>\n\n\n\n
          Step 1: Assign Permissions and Mailbox Import Export Role<\/strong><\/p>\n\n\n\n
          By default, the Mailbox Import Export role is not even assigned to administrators’ accounts. Thus, before executing the New-MailboxExportRequest cmdlet, you must assign the required role to the user account. For this, use the following command,<\/p>\n\n\n\n
          New-ManagementRoleAssignment \u2013Role \"Mailbox Import Export\" \u2013User \"user name\"<\/code><\/pre>\n\n\n\n
          Step 2: Use New-MailboxExportRequest Cmdlet with Additional Parameters<\/strong><\/p>\n\n\n\n
          If the export still fails and an error UnableToReadPSTFolder<\/em> is displayed, you can execute the New-MailboxExportRequest<\/em> cmdlet with some additional parameters to add an exception. This can help you avoid the error, if it occurs due to bad items in the mailbox.<\/p>\n\n\n\n
          Try the following modified cmdlet to export PST in Exchange,<\/p>\n\n\n\n
          New-MailboxExportRequest -Mailbox mailboxname -FilePath \\\\server\\d$\\Backup\\mailbox.pst -BadItemLimit 200 -AcceptLargeDataLoss<\/code><\/pre>\n\n\n\n
          The above command will try to export a PST file from the selected mailbox with an exception. The command will skip up to 200 bad items. It will export the PST even if the data loss occurs. You can increase or decrease the bad items limit. To know more about New-ExportMailboxRequest cmdlet, read How to use New-MailboxExportRequest Cmdlet.<\/p>\n\n\n\n
          Step 3: Export Mailbox from Exchange EDB to PST with Stellar Converter for EDB<\/strong><\/p>\n\n\n\n
          Stellar Converter for EDB<\/a>\u00a0is an Exchange database, i.e. EDB to PST converter software. By using this software, you can convert desired mailboxes from Exchange database to PST file, irrespective of the mailbox size.<\/p>\n\n\n\n
          Follow the steps below to convert Exchange mailbox into PST file,<\/p>\n\n\n\n
          Install and run Stellar Converter for EDB software<\/li>
          Select Hosted Exchange or Offline EDB file option based on where the specific mailbox is located<\/li><\/ol>\n\n\n\n
          <\/a><\/p>\n\n\n\n
          <\/figure>\n\n\n\n
          Select the EDB file and convert<\/li><\/ul>\n\n\n\n
          <\/figure><\/div>\n\n\n\n
          After conversion, you can preview the content of EDB file and view mailbox items before export<\/li>
          Then select the mailbox you want to export to PST<\/li>
          Click on Save and from the options, choose \u2018Export to PST\u2019<\/li><\/ul>\n\n\n\n
          <\/figure><\/div>\n\n\n\n
          Click \u2018Next\u2019 and choose a location where you want to save the PST file<\/li>
          Click \u2018OK\u2019<\/li><\/ul>\n\n\n\n
          You can also convert EDB mailboxes to other file formats such as MSG, EML, RTF, etc. If required, you can save the converted mailbox directly to the Live Exchange server or Office 365.<\/p>\n\n\n\n
          Why Use Software to Resolve the UnableToReadPSTFolder Error?<\/strong><\/p>\n\n\n\n
          Stellar Converter for EDB proficiently converts offline as well as online EDB (Exchange Database) files. The software successfully converts deleted and archived mailboxes to PST file and saves all components with 100% integrity. The file-preview option lets users verify the mail components before saving the file. The software also facilitates selective conversion.<\/p>\n\n\n\n
          Conclusion<\/strong><\/p>\n\n\n\n
          Exchange Admins understand the importance of keeping the Exchange up and running at all times. However, due to oversized mailboxes, the services may be hampered and rendered unavailable. In such cases, there are only one option remains, which is to export the mailboxes from the Exchange database to PST by using PowerShell command or with specialized software like Stellar Converter for EDB.<\/p>\n\n\n\n
          The Software converts Unicode EDB files available in multiple languages and makes sure that Exchange services are not hampered for a long time when the server gets affected due to \u201cMailboxExportRequest Fails\/ UnableToReadPSTFolderPermanentException\u201d errors.<\/p>\n","protected":false},"excerpt":{"rendered":"
          Summary: The error UnableToReadPSTFolder appears when a user attempts to export PST by using the New-MailboxExportRequest cmdlet in Exchange Management Shell. It occurs when the PST export process fails due to inadequate permissions, mailbox size, bad items, corruption, or any other reason. In this guide, we have discussed the UnableToReadPSTFolder error in detail and also addressed a few workaround steps to export PST from an online or offline Exchange mailbox database. There could be many reasons to export the PST file from a mailbox on the Exchange server. An Exchange administrator may export mailbox to PST for backup or migration <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/987"}],"collection":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/comments?post=987"}],"version-history":[{"count":13,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/987\/revisions"}],"predecessor-version":[{"id":1879,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/987\/revisions\/1879"}],"wp:attachment":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/media?parent=987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/categories?post=987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/tags?post=987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}