Hello

After upgrading to Outlook 2013 I get Send/Receive and PST file errors every day. I can repair the PST file and send/receive OK.

Next day same problem.

I have one POP3 email account which has worked with all versions of Outlook for maybe 15 years no problem.

These are the PST file errors (there are loads of these):-

>>

??BBT entry (2AF4CC4) has different refcount in RBT (6 vs 3)

??Couldn't find BBT entry in the RBT (2E43708)

Failed to add row to the FLT, RowID = 7F

<<

The only thing I can think of which is different is that I have moved my Calendar to Outlook.com so I can sync with my Windows 8 Phone. This requires adding a new Exchange Active Sync Account for the Outlook.com Calendar.

I have seen a post which says that Active Sync accounts are not compatible with PST files so I should use the Hotmail Connector. But the Hotmail connector does not work with Outlook 2013.

Please advise.

• Edited by BayTree Wednesday, January 02, 2013 10:20 AM

Hi Tony

When the previous PST file was scanned and fixed it worked for a few send/receive cycles, the I got errors again. I have SCANPST pinned to Start because I had to run it all the time.

I created a new PST file then Archived everything over 1 day old to Archive.pst. Archive.pst then required a repair which has never happened before.

Now Outlook seems to be working OK using the new PST file.

• Edited by BayTree Monday, January 07, 2013 5:48 PM
• Marked as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, January 11, 2013 8:00 AM

I'll just chip in that I also have a PST that is never repaired by Scanpst from Office 2013 (or the one from 2010, which I tried for good measure) no matter how many times you run it. It's only about a 500MB file.

Like the OP, the log shows a loooooong string of messages like: "Failed to add row to the FLT, RowID = 721," which is its attempt to "walk all folders."

The only other negative in the log is a single one of these, the details of which changes each time: "**Attempting to validate AMap !!AMap page <@527475712> has csFree of 5, but should have 255."

The twist is that there are apparently no problems that I've noticed with this PST. I just like to run checks on it from time to time, when I came upon this problem.