Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RE: Scanpst changes in Office 2007 SP2??

114 views
Skip to first unread message

dutch55

unread,
May 1, 2009, 10:16:09 AM5/1/09
to
Scanpst is reporting many more errors with Office 2007 SP2. Most recently I
ran scanpst.exe, got "minor inconsistencies" message, selected repair, ran
scanpst again, got no errors, then opened Outlook, processed a few mails,
exited normally, ran scanpst again, it detected errors.

"John A. Murphy" wrote:

> Using Outlook 2007 SP1, I ran scanpst (version 12.0.6315.5000) on a 512mb
> pst file and it came back with no errors. I then installed SP2, rebooted and
> immediately ran the new scanpst (version 12.0.6423.1000) and it came back
> with numerous errors which i pasted below (note that I only included a
> portion of the AMap errors to keep this post a reasonable length). Any ideas
> about what is going on?
>
>
> Microsoft (R) Inbox Repair Tool
> Copyright (C) Microsoft Corp 1995-1996. All rights reserved.
>
> **Beginning NDB recovery
>
> **Attempting to open database
>
> **Attempting to validate header
>
> **Attempting to validate AMap
>
> !!AMap page <@17408> has csFree of 2, but should have 8
> !!AMap page <@271360> has csFree of 2, but should have 11
> !!AMap page <@779264> has csFree of 2, but should have 11
> !!AMap page <@1033216> has csFree of 2, but should have 8
> !!AMap page <@1287168> has csFree of 3, but should have 8
>
> **Attempting to validate BBT
>
> **Attempting to validate NBT
>
> **Attempting to validate BBT refcounts
>
> ??BBT entry (86C224) has different refcount in RBT (3 vs 2)
> ??Couldn't find BBT entry in the RBT (C926C6)
> ??Couldn't find BBT entry in the RBT (C926C8)
> ??Couldn't find BBT entry in the RBT (C9B740)
> ??Couldn't find BBT entry in the RBT (C9B746)
> ??BBT entry (D59820) has different refcount in RBT (3 vs 2)
> ??BBT entry (D6BADA) has different refcount in RBT (3 vs 2)
> ??Couldn't find BBT entry in the RBT (D6BAEE)
> ??BBT entry (D6BAF0) has different refcount in RBT (3 vs 2)
>
> **Attempting to validate header NID high-water marks
>
> **Beginning PST/OST recovery
>
> **Attempting to recover all top-level objects
>
> **Attempting to walk all folders
>
> !!TC (nid=12E) missing required column (0E380003)
>
> !!TC (nid=200E) missing required column (0E380003)
>
> !!TC (nid=202E) missing required column (0E380003)
>
> !!TC (nid=204E) missing required column (0E380003)
>
> !!TC (nid=206E) missing required column (0E380003)
>
> !!TC (nid=208E) missing required column (0E380003)
>
> **Attempting to locate any orphaned folders/messages
>
> **Performing final HMP validation
>
> **Attempting to check top-level objects for consistency
>
> ??Deleting SDO
>
> **Updating folder hierarchy
>
> **Verifying message moves
>
> **Attempting to fix original file
>
> **Attempting to copy back BBT
>
> **Attempting to copy back NBT
>
>

Lucent

unread,
May 1, 2009, 1:41:01 PM5/1/09
to
Confirmed in SP2. I can run scanpst against my outlook, archive, imap, and
hotmail PSTs and generate several "AMap page ... has csFree of x, but should
have been y" errors per scan. Not only that, I can repair the same file two
or three times and continue to get errors without even opening Outlook.
Eventually it does resolve everything and subsequent scans cause no errors
until Outlook is opened again and touches the files. Then the process starts
again.

PST seems to be a fragile format based on my interactions over the past
decade. I think it's time Microsoft just switched to a real lightweight
database install. They install SQL Server compact edition for something as
silly as Live Photo Gallery. Perhaps it's time to do this for Outlook as well.

Allan

unread,
May 4, 2009, 6:28:01 AM5/4/09
to
The same thing happens to me.

I have a 400KB .pst file that is fine under Outlook 2007 SP1, but the new
Scanpst in SP2 finds numerous errors with it. If I run Scanpst 3 times on
the file, it will finally show up with No Errors Found, but then as soon as
Outlook is run with a Send/Receive, the errors will display again. These are
the same "AMap page ... has csFree of x, but should have been y" errors"
noted above.

I believe the errors don't show up until a Send/Receive is run.

I notice that after Outlook touches the file and it gets 'corrupted' again,
it also gets larger and I need to run a compaction to reduce the size back to
normal.

I wonder if the Outlook Connector 12.1 needs to be uninstalled and
re-installed?

Is the new Scanpst buggy?

I have no email antivirus installed. I do have Itunes installed but
disabled their COM add-in and the same thing happened.

I've gone back to SP1 in the meantime until this is sorted out.

Wilson

unread,
Jun 28, 2009, 6:36:01 PM6/28/09
to

Allan: i have the exact same problem that Lucent describes. frequent imap,
bbt, etc errors. i've tried formatting hdd and starting a new pst file. but
still lots of errors exactly as Lucent described.

You suggested going back to sp1. did this work for you?

funny thing: i wasted 1hr 35min with MS tech support regarding this. their
recommendation was "backup the file frequently".

Allan

unread,
Jun 28, 2009, 9:16:01 PM6/28/09
to

I have been running SP2 for a while now. I haven't run SCANPST and have
experienced no problems.

AndrewNKeller

unread,
Jul 1, 2009, 11:48:01 AM7/1/09
to

I have been struggling with GDI leaks in Outlook and Word (which I think is
connectect directly to the problems with Outlook) for quite some time. If my
PST file (which I have a password on) isn't opened, then I don't have these
problems.

Running scanpst on my pst file starts with "minor inconsistancies", but
after repairing it goes straight to "Errors were found", repeatedly, and
never comes back out of that state, even after multiple repairs and/or
compacts.

Creating a new pst file and copying the files over doesn't fix it.
Creating a new 2002 version of the pst file and copying the files over
doesn't fix it.

Even completely emptying and compacting the file down to nothing still comes
up with errors in the pst file (and the resulting GDI leaks in Outlook due to
it). So, after having Outlook running for over a few hours my display goes
crazy because Outlook is consuming over 10,000 GDI handles.

The whole thing is ridiculous, and I can't seem to fix it.

Microsoft: Please fix Outlook. Why are we still using PST's instead of
something more like a SQL database backend? Why doesn't the Inbox Repair
Tool (which is fixing archive data files, -not- the Inbox) actually repair
anything?

0 new messages