Why does the Outlook PST repair tool always report that many errors?
I routinely run the Outlook PST repair tool (scanpst.exe) on my .pst file every few month. I like to make sure that my mails are not becoming corrupted slowly over time.
I never noticed any data loss. Outlook never reported any errors to me. Yet, the tool spits out very many errors on every check I perform. Here's a sample of the 2MB log file the tool generated:
**Attempting to validate AMap
...
!!AMap page <@17408> has csFree of 54, but should have 62
!!AMap page <@525312> has csFree of 135, but should have 177
...
??BBT entry (EBF8E5C) has different refcount in RBT (4 vs 3)
??BBT entry (EBFA99C) has different refcount in RBT (4 vs 3)
...
??Couldn't find BBT entry in the RBT (2BD4F74C)
??Couldn't find BBT entry in the RBT (2BD4F750)
...
!!Folder invalid high-water-mark (nidi=A8018, nidiHigh=C281B)
...
!!Search folder invalid high-water-mark (nidi=A798D, nidiHigh=BDE8F)
...
!!Contents Table for 8082, row doesn't match sub-object:
irow = 30641, RowID = 2BE37C4
Just tons of these worrying messages. My disk is fine. Nothing else is ever becoming corrupted on this machine.
Do I have to worry? What's causing these error messages?
microsoft-outlook microsoft-outlook-2010 pst file-corruption
edited Aug 25 '14 at 14:39
Kenster
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
add a comment |
I routinely run the Outlook PST repair tool (scanpst.exe) on my .pst file every few month. I like to make sure that my mails are not becoming corrupted slowly over time.
I never noticed any data loss. Outlook never reported any errors to me. Yet, the tool spits out very many errors on every check I perform. Here's a sample of the 2MB log file the tool generated:
**Attempting to validate AMap
...
!!AMap page <@17408> has csFree of 54, but should have 62
!!AMap page <@525312> has csFree of 135, but should have 177
...
??BBT entry (EBF8E5C) has different refcount in RBT (4 vs 3)
??BBT entry (EBFA99C) has different refcount in RBT (4 vs 3)
...
??Couldn't find BBT entry in the RBT (2BD4F74C)
??Couldn't find BBT entry in the RBT (2BD4F750)
...
!!Folder invalid high-water-mark (nidi=A8018, nidiHigh=C281B)
...
!!Search folder invalid high-water-mark (nidi=A798D, nidiHigh=BDE8F)
...
!!Contents Table for 8082, row doesn't match sub-object:
irow = 30641, RowID = 2BE37C4
Just tons of these worrying messages. My disk is fine. Nothing else is ever becoming corrupted on this machine.
Do I have to worry? What's causing these error messages?
microsoft-outlook microsoft-outlook-2010 pst file-corruption
edited Aug 25 '14 at 14:39
Kenster
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
add a comment |
I routinely run the Outlook PST repair tool (scanpst.exe) on my .pst file every few month. I like to make sure that my mails are not becoming corrupted slowly over time.
I never noticed any data loss. Outlook never reported any errors to me. Yet, the tool spits out very many errors on every check I perform. Here's a sample of the 2MB log file the tool generated:
**Attempting to validate AMap
...
!!AMap page <@17408> has csFree of 54, but should have 62
!!AMap page <@525312> has csFree of 135, but should have 177
...
??BBT entry (EBF8E5C) has different refcount in RBT (4 vs 3)
??BBT entry (EBFA99C) has different refcount in RBT (4 vs 3)
...
??Couldn't find BBT entry in the RBT (2BD4F74C)
??Couldn't find BBT entry in the RBT (2BD4F750)
...
!!Folder invalid high-water-mark (nidi=A8018, nidiHigh=C281B)
...
!!Search folder invalid high-water-mark (nidi=A798D, nidiHigh=BDE8F)
...
!!Contents Table for 8082, row doesn't match sub-object:
irow = 30641, RowID = 2BE37C4
Just tons of these worrying messages. My disk is fine. Nothing else is ever becoming corrupted on this machine.
Do I have to worry? What's causing these error messages?
microsoft-outlook microsoft-outlook-2010 pst file-corruption
edited Aug 25 '14 at 14:39
Kenster
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
I routinely run the Outlook PST repair tool (scanpst.exe) on my .pst file every few month. I like to make sure that my mails are not becoming corrupted slowly over time.
I never noticed any data loss. Outlook never reported any errors to me. Yet, the tool spits out very many errors on every check I perform. Here's a sample of the 2MB log file the tool generated:
**Attempting to validate AMap
...
!!AMap page <@17408> has csFree of 54, but should have 62
!!AMap page <@525312> has csFree of 135, but should have 177
...
??BBT entry (EBF8E5C) has different refcount in RBT (4 vs 3)
??BBT entry (EBFA99C) has different refcount in RBT (4 vs 3)
...
??Couldn't find BBT entry in the RBT (2BD4F74C)
??Couldn't find BBT entry in the RBT (2BD4F750)
...
!!Folder invalid high-water-mark (nidi=A8018, nidiHigh=C281B)
...
!!Search folder invalid high-water-mark (nidi=A798D, nidiHigh=BDE8F)
...
!!Contents Table for 8082, row doesn't match sub-object:
irow = 30641, RowID = 2BE37C4
Just tons of these worrying messages. My disk is fine. Nothing else is ever becoming corrupted on this machine.
Do I have to worry? What's causing these error messages?
microsoft-outlook microsoft-outlook-2010 pst file-corruption
microsoft-outlook microsoft-outlook-2010 pst file-corruption
edited Aug 25 '14 at 14:39
Kenster
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
edited Aug 25 '14 at 14:39
Kenster
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
edited Aug 25 '14 at 14:39
Kenster
4,83521933
edited Aug 25 '14 at 14:39
Kenster
4,83521933
edited Aug 25 '14 at 14:39
Kenster
4,83521933
4,83521933
asked Aug 16 '14 at 17:16
usrusr
1,35031525
asked Aug 16 '14 at 17:16
usrusr
1,35031525
asked Aug 16 '14 at 17:16
usrusr
1,35031525
1,35031525
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
These problems still exist in O365 Outlook 2019. The scanpst.exe tool has been updated but it still can't fix all problems. I recommend making a backup and deleting your PST files. They will be repopulated from the server next time you start Outlook.
Try to keep your PSTs small by deleting and archiving. The larger the file is the more likely Outlook is to make a mistake. It's always been this way. Microsoft has made improvements but they've never made Outlook bulletproof. Deleting your profile and Reinstalling Outlook are both official Microsoft recommendations on all support articles today.
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
Typically the point of an.PSTfile is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the.PSTfile (which is the backup) is confusing.
– Ramhound
Jan 3 at 18:40
add a comment |
protected by slhck Aug 16 '14 at 17:21
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
These problems still exist in O365 Outlook 2019. The scanpst.exe tool has been updated but it still can't fix all problems. I recommend making a backup and deleting your PST files. They will be repopulated from the server next time you start Outlook.
Try to keep your PSTs small by deleting and archiving. The larger the file is the more likely Outlook is to make a mistake. It's always been this way. Microsoft has made improvements but they've never made Outlook bulletproof. Deleting your profile and Reinstalling Outlook are both official Microsoft recommendations on all support articles today.
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
Typically the point of an.PSTfile is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the.PSTfile (which is the backup) is confusing.
– Ramhound
Jan 3 at 18:40
add a comment |
These problems still exist in O365 Outlook 2019. The scanpst.exe tool has been updated but it still can't fix all problems. I recommend making a backup and deleting your PST files. They will be repopulated from the server next time you start Outlook.
Try to keep your PSTs small by deleting and archiving. The larger the file is the more likely Outlook is to make a mistake. It's always been this way. Microsoft has made improvements but they've never made Outlook bulletproof. Deleting your profile and Reinstalling Outlook are both official Microsoft recommendations on all support articles today.
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
Typically the point of an.PSTfile is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the.PSTfile (which is the backup) is confusing.
– Ramhound
Jan 3 at 18:40
add a comment |
These problems still exist in O365 Outlook 2019. The scanpst.exe tool has been updated but it still can't fix all problems. I recommend making a backup and deleting your PST files. They will be repopulated from the server next time you start Outlook.
Try to keep your PSTs small by deleting and archiving. The larger the file is the more likely Outlook is to make a mistake. It's always been this way. Microsoft has made improvements but they've never made Outlook bulletproof. Deleting your profile and Reinstalling Outlook are both official Microsoft recommendations on all support articles today.
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
These problems still exist in O365 Outlook 2019. The scanpst.exe tool has been updated but it still can't fix all problems. I recommend making a backup and deleting your PST files. They will be repopulated from the server next time you start Outlook.
Try to keep your PSTs small by deleting and archiving. The larger the file is the more likely Outlook is to make a mistake. It's always been this way. Microsoft has made improvements but they've never made Outlook bulletproof. Deleting your profile and Reinstalling Outlook are both official Microsoft recommendations on all support articles today.
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
answered Jan 3 at 17:33
HackSlashHackSlash
1,9821620
1,9821620
Typically the point of an.PSTfile is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the.PSTfile (which is the backup) is confusing.
– Ramhound
Jan 3 at 18:40
add a comment |
Typically the point of an.PSTfile is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the.PSTfile (which is the backup) is confusing.
– Ramhound
Jan 3 at 18:40
Typically the point of an
.PST file is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the .PST file (which is the backup) is confusing.– Ramhound
Jan 3 at 18:40
Typically the point of an
.PST file is that the emails no longer exist on the server and are used to archive the emails. So your suggestion of "making a backup" and then deleting the .PST file (which is the backup) is confusing.– Ramhound
Jan 3 at 18:40
add a comment |
protected by slhck Aug 16 '14 at 17:21
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
