Outlook 2003 general errors

[jmt356]

I am running MS Outlook 2003 on a Windows XP laptop. A few weeks ago, Outlook would freeze up when I clicked Send/Receive. I would force shutdown, and upon re-launching, a message would appear stating that Outlook was not properly closed down and some kind of repair would launch. I would then click Send/Receive again, and the above process would repeat itself.

There is other abnormal activity, namely:
1. I have gotten the following pop up message twice today: “Cannot turn off the reminder. You may be reminded again. The file C:\Documents and Settlings\User Name\Local Settings\Application Data\Microsoft\Outlook\Outlook.pst could not be accessed. Data error (cyclic redundancy check).

2. Upon clicking Send/Receive for my Gmail account only, I got the error message “Task ‘[email account name] – Receiving’ reported error (0x80040116) : ‘Unknown Error 0x80040116’” (from a Google search, I believe this means my Outlook.pst file has been corrupted)

3. When I go to the folder C:\Documents and Settlings\User Name\Local Settings\Application Data\Microsoft\Outlook, the contents are very odd:
- Outlook.pst (2.8 GB) – written in blue
- Outlookasol.com-00000011.pst (1.71 MB) – file name written in black
- Outlook[account name]-00000005.pst (5.3 MB) –file name written in blue
My main concern with these files is that two of them are written in blue. I have never seen file names in blue in Internet Explorer, so I wonder if this is some kind of indication that the files are corrupt.

4. Switching between the Inbox and Sent items takes a very unusually long period of time.

I am considering using the Inbox Repair tool, but as the main .pst file exceeds 2 GB, I am not sure whether it would be to any avail.

Any tips / experience you can share would be highly appreciated.

[StuartR]

You should try the inbox repair tool, but make sure you allow it to make a backup copy.

Blue file names in Windows Explorer are usually just the result of you setting explorer to show compressed files in blue. Have you used disk cleanup to compress files on this drive?

[HansV]

If a file name is blue in Windows Explorer, the file is compressed. If you can't remember having set this yourself, it might be a result of Disk Cleanup - one of the options is to compress old files.

The error messages certainly point to a corrupted .pst file.
I'd create a backup copy first, then try the Inbox Repair tool scanpst.exe.

[jmt356]

I tried to run the Inbox Repair Tool but a message appeared that it could not be done (could not access the pst file or something like that) and that I had to do a Scan disk. I tried doing a scan disk to my C drive but it did not appear complete. It took about 2 seconds and then ended; normally it takes several hours.

[HansV]

Did you quit Outlook before running ScanPst.exe?

[jmt356]

I did. And to be sure, I tried a second time when I was sure Outlook was closed down.

I just scheduled another scan disk. The scan disk now appears to be working correctly. Perhaps before, I did not correctly choose the entire C drive but rather some isolated file.

[HansV]

Let us know the result...

[jmt356]

Scan Disk ran for several hours and found (and I believe repaired) many errors. I was then able to run the Inbox Repair Tool, which also found errors and repaired them. I am currently running an anti-virus scan and thereafter will see if Outlook is running better.

[jmt356]

I found no virus. However, the Scan Disk revealed many read failures. My guess is this is probably something to be concerned about:

Checking file system on C:
The type of the file system is NTFS.
Volume label is SQ004101P01.

A disk check has been scheduled.
Windows will now check the disk.
Read failure with status 0xc000009c at offset 0x4f3f7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x4f3f7000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x4f3f7000 for 0x1000 bytes.
The multi-sector header signature for VCN 0x1 of index $I30
in file 0x14fdd is incorrect.
78 01 07 00 80 b0 9a 00 2f 65 4f 63 08 00 00 00 x......./eOc....
00 00 00 00 00 00 00 00 28 00 00 00 60 09 00 00 ........(...`...
Correcting error in index $I30 for file 85981.
The index bitmap $I30 in file 0x14fdd is incorrect.
Correcting error in index $I30 for file 85981.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff e5 48 01 00 00 00 25 00 .........H....%.
64 33 5d a7 d7 b4 cb 01 dc c7 45 3e 28 f1 cb 01 d3].......E>(...
Sorting index $I30 in file 85981.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file FE499D~1 (85982) into directory file 85981.
Recovering orphaned file fe499d5ab131469681a3fa3c50213e845849e4bf (85982) into directory file 85981.
Recovering orphaned file FE49D4~1 (85985) into directory file 85981.
Recovering orphaned file fe49d4a918c932cb03f5d0ed6fee6fb1d2b717d2 (85985) into directory file 85981.
Recovering orphaned file FE4FE0~1 (85986) into directory file 85981.
Recovering orphaned file fe4fe068706be20299dce5ba4723089b6b5d3bd1 (85986) into directory file 85981.
Recovering orphaned file FE4A2C~1 (85988) into directory file 85981.
Recovering orphaned file fe4a2c4eb0bb9a9d30336438a8877258293892ab (85988) into directory file 85981.
Recovering orphaned file FE4CA7~1 (85989) into directory file 85981.
Recovering orphaned file fe4ca7acb363f3fdde3190bffc83169dfbc440dd (85989) into directory file 85981.
Recovering orphaned file FE4A9C~1 (122510) into directory file 85981.
Recovering orphaned file fe4a9cd892bcbd77e03df9ed3a6275ef22307e8d (122510) into directory file 85981.
Recovering orphaned file FE4D76~1 (122512) into directory file 85981.
Recovering orphaned file fe4d76e885507d67b5ab9f88ef5f2553579f2a3f (122512) into directory file 85981.
Cleaning up 65 unused index entries from index $SII of file 0x9.
Cleaning up 65 unused index entries from index $SDH of file 0x9.
Cleaning up 65 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x619d5000 for 0x3000 bytes.
Read failure with status 0xc000009c at offset 0x619d7000 for 0x1000 bytes.
Windows replaced bad clusters in file 4030
of name \PROGRA~1\INSTAL~1\{80977~1\Setup.ilg.
Read failure with status 0xc000009c at offset 0x616c6000 for 0xa000 bytes.
Read failure with status 0xc000009c at offset 0x616ca000 for 0x1000 bytes.
Windows replaced bad clusters in file 24740
of name \WINDOWS\system32\REINST~1\0008\DRIVER~1\i386\usbui.dll.
Read failure with status 0xc000009c at offset 0x4ccbe000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4ccc1000 for 0x1000 bytes.
Windows replaced bad clusters in file 28032
of name \WORKSS~1\OFFICE\CM561401.CAB.
Read failure with status 0xc000009c at offset 0x4cd7f000 for 0x9000 bytes.
Read failure with status 0xc000009c at offset 0x4cd84000 for 0x1000 bytes.
Windows replaced bad clusters in file 37228
of name \PROGRA~1\HP\Temp\{F5936~1\setup\hpzrcv01.exe.
Read failure with status 0xc000009c at offset 0x50366000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x5036f000 for 0x1000 bytes.
Windows replaced bad clusters in file 51800
of name \DOCUME~1\ALLUSE~1\APPLIC~1\APPLEC~1\INSTAL~1\QUICKT~1.56\QUICKT~1.MSI.
Read failure with status 0xc000009c at offset 0x50432000 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x50432000 for 0x1000 bytes.
Windows replaced bad clusters in file 53023
of name \PROGRA~1\Audacity\help\manual\m\images\1\1f\TRANSC~1.PNG.
Read failure with status 0xc000009c at offset 0x6098e000 for 0xf000 bytes.
Read failure with status 0xc000009c at offset 0x6099b000 for 0x1000 bytes.
Windows replaced bad clusters in file 54319
of name \DOCUME~1\ALEXAD~1\LOCALS~1\APPLIC~1\MICROS~1\Outlook\Outlook.pst.
Read failure with status 0xc000009c at offset 0x3c4ec000 for 0x8000 bytes.
Windows replaced bad clusters in file 67790
of name \PROGRA~1\HEWLET~1\DIGITA~1\DEVICE~1\hpzmsi01.exe.
Read failure with status 0xc000009c at offset 0x4e90c000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4e912000 for 0x1000 bytes.
Windows replaced bad clusters in file 70947
of name \DOCUME~1\JMT\Desktop\INSTAL~1\MICROS~1\FRONTP~1\MH561401.CAB.
Read failure with status 0xc000009c at offset 0x49fbf000 for 0x9000 bytes.
Read failure with status 0xc000009c at offset 0x49fc2000 for 0x1000 bytes.
Windows replaced bad clusters in file 70960
of name \DOCUME~1\JMT\Desktop\INSTAL~1\MICROS~1\FRONTP~1\OWC11.MSI.
Read failure with status 0xc000009c at offset 0x6178a000 for 0xc000 bytes.
Read failure with status 0xc000009c at offset 0x6178d000 for 0x1000 bytes.
Windows replaced bad clusters in file 85746
of name \WINDOWS\system32\dllcache\nmft.dll.
Read failure with status 0xc000009c at offset 0x502a7000 for 0xe000 bytes.
Read failure with status 0xc000009c at offset 0x502ac000 for 0x1000 bytes.
Windows replaced bad clusters in file 134508
of name \PROGRA~1\ROSETT~1\ARABIC~1\data\65\0\650D23~1.
Read failure with status 0xc000009c at offset 0x4079b000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x407a0000 for 0x1000 bytes.
Windows replaced bad clusters in file 164102
of name \DOCUME~1\ALEXAD~1\MYDOCU~1\WEDDIN~1\JPIMAG~1\ceremony\JO0984~1.JPG.
Read failure with status 0xc000009c at offset 0x4adab000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4adb4000 for 0x1000 bytes.
Windows replaced bad clusters in file 176154
of name \WINDOWS\INSTAL~1\MSI119.tmp.
Read failure with status 0xc000009c at offset 0x3d097000 for 0xa000 bytes.
Read failure with status 0xc000009c at offset 0x3d09b000 for 0x1000 bytes.
Windows replaced bad clusters in file 178209
of name \WINDOWS\assembly\GAC_MSIL\PRD895~1\300~1.0__\PRESEN~1.DLL.
Read failure with status 0xc000009c at offset 0x4d426000 for 0xa000 bytes.
Read failure with status 0xc000009c at offset 0x4d427000 for 0x1000 bytes.
Windows replaced bad clusters in file 179553
of name \WINDOWS\assembly\GAC_MSIL\SYSTEM~1.REM\200~1.0__\SYSTEM~1.DLL.
Read failure with status 0xc000009c at offset 0x6080c000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x60815000 for 0x1000 bytes.
Windows replaced bad clusters in file 185953
of name \DOCUME~1\ALEXAD~1\MYDOCU~1\MYPICT~1\May 2009\SANY3151.JPG.
Read failure with status 0xc000009c at offset 0x504f5000 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x504f6000 for 0x1000 bytes.
Windows replaced bad clusters in file 199478
of name \SYSTEM~1\_RESTO~1\RP1185\A0213273.ini.
Read failure with status 0xc000009c at offset 0x4cf01000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4cf0b000 for 0x1000 bytes.
Windows replaced bad clusters in file 201020
of name \SYSTEM~1\_RESTO~1\RP1185\A0163329.dll.
Read failure with status 0xc000009c at offset 0x4d297000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x4d2a0000 for 0x1000 bytes.
Windows replaced bad clusters in file 205443
of name \WINDOWS\SOFTWA~1\Download\9866FB~1\i386\ip\sprc0414.dl_.
Read failure with status 0xc000009c at offset 0x4d363000 for 0x4000 bytes.
Read failure with status 0xc000009c at offset 0x4d363000 for 0x1000 bytes.
Windows replaced bad clusters in file 207410
of name \WINDOWS\SOFTWA~1\Download\9866FB~1\i386\wuau.ch_.
Read failure with status 0xc000009c at offset 0x3cbe8000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x3cbeb000 for 0x1000 bytes.
Windows replaced bad clusters in file 215687
of name \PROGRA~1\MI2020~1\411032~1.0\MICROS~1.DLL.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 22 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

244196000 KB total disk space.
88972380 KB in 206946 files.
90208 KB in 18159 indexes.
88 KB in bad sectors.
303732 KB in use by the system.
65536 KB occupied by the log file.
154829592 KB available on disk.

4096 bytes in each allocation unit.
61049000 total allocation units on disk.
38707398 allocation units available on disk.

Internal Info:
90 7b 03 00 5c 6f 03 00 42 8d 05 00 00 00 00 00 .{..\o..B.......
1c 1c 00 00 02 00 00 00 8a 02 00 00 00 00 00 00 ................
3a 0e cd 08 00 00 00 00 bc 7a 5e 9c 00 00 00 00 :........z^.....
a8 0f ae 08 00 00 00 00 5e a9 8e 91 0a 00 00 00 ........^.......
9a 6d 11 db 06 00 00 00 0a 64 8a 22 12 00 00 00 .m.......d."....
99 9e 36 00 00 00 00 00 98 38 07 00 62 28 03 00 ..6......8..b(..
00 00 00 00 00 70 71 36 15 00 00 00 ef 46 00 00 .....pq6.....F..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp" onclick="window.open(this.href);return false;.

[HansV]

I notice that Outlook.pst was among the files with bad clusters; this probably explains the problems you were experiencing.

Apparently there were many bad clusters - this could be a sign that your hard disk is about to fail. I'd make sure that you have backups of all important files, and keep a close watch on the functioning of the hard disk.