[ 
https://issues.apache.org/jira/browse/AMQ-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned AMQ-7379:
-----------------------------------------

    Assignee: Jean-Baptiste Onofré

> OST recovery made easy with EdbMails OST to PST tool
> ----------------------------------------------------
>
>                 Key: AMQ-7379
>                 URL: https://issues.apache.org/jira/browse/AMQ-7379
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Rose Watt
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>
> OST files are often thought of as an Offline copy of your Exchange mailbox. 
> They allow you to continue working even when not connected to the internet 
> and sync all the changes that you make in Outlook with Exchange once the 
> connectivity to Exchange is restored. However, like any other database, the 
> Exchange OST file can also get corrupted and put all the data stored inside 
> it in jeopardy.
>  *Some of the reasons for OST corruption include:*
>  Corruption in the file system
> Sudden termination of main Outlook process resulting in its closure of Outlook
> Synchronization issues
> Malicious software infection
>  *Here are some of the common OST file errors:*
>  
>  * Error code 0x8004103b
>  * Internal error of OST file (error code=0000000E)
>  * OST Internal (error code=00000003)
>  * Error-message/c5e20916-9359-43fc-9bd9
>  * Error 8004011D-526-80040115-0
>  
> The best way to deal with all such OST issues is to use EdbMails [OST to PST 
> Converter|https://www.edbmails.com/] that can help recover all information 
> from even the most heavily corrupted OST files with ease. There is even a 
> Free demo version of the OST to PST tool that allows us to export up to 30 
> items from each mailbox/folder to the PST file. The OST Recovery tool from 
> EdbMails maintains the folder structure intact and also does not make any 
> alterations to the data in the original OST file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to