• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7259
  • Last Modified:

Outlook 2003 PST Size Limit Reached - Need advice on Repair procedure.

I have a user with an Outlook 2003 PST that has reached the maximum size of 20 gigs.  Fun Fun!  The file will not open and display properly in Outlook at this point.  It throws a message stating that the file has reached maximum size, this is displayed in the pane where the inbox items are usually listed. I had trouble finding info on a truncation utility that is specifically stated to handle the newer 03 style databases. So for starters,  I ran scanpst on the file, errors were found, so I hit repair.  The utility ran for hours and finally completed.  The database is still unreadable.  I've fixed plenty of older databases by running pst2gb to truncate then running scanpst.  I tried running pst2gb on the database but it throws a run-time 52 error when I select the broken database.  I can only assume that pst2gb is not designed to work on the new and larger db.  I don't know what to do next.  Is there a cropping utility for the 2003 style databases that have reached max size, or some other utility or method I missed?
0
fortier
Asked:
fortier
  • 3
  • 2
1 Solution
 
war1Commented:
Greetings fortier !

There is a registry edit to allow the file size to 33 GB.  Perform the registry edit.  
http://support.microsoft.com/kb/832925/en-us?spid=2520&sid=1379

Open Outlook with the file. Move the emails to other PST files.  A good operating PST file should not be over 1 GB.

Hope this helps, war1
0
 
war1Commented:
fortier, I meant to say that allow the file size to 33 TB.  You do not have to make it that big. Just big enough to be able to open Outlook and the PST file.
0
 
AhalwagyCommented:
Follow the instructions in the link below, i think this this will help you solve your problem.

http://www.slipstick.com/problems/repair2gbpst.asp

0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
fortierAuthor Commented:
Hmm, I did see the kb article about the registry edit.  Problem I ran into was that the path in the registry stopped short at HKEY_CURRENT_USER\Software\Policies\Microsoft\.  There was no Office 11 folder.  I also verified this to be true on another one of our workstations.  I did see that the reg entries may need to be created manually.  But it seems that this path should already be there "HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\Outlook".  Then I would need to create the PST key there.  But, the Office\11.0\Outlook part of the registy path does not exist.  I wonder if I need to manually create the Office\11.0\Outlook section then add the PST key?  This does not follow the MS article.  Just an fyi, the office 2003 installation is at service pack 2 level.
0
 
war1Commented:
fortier,

Yes, you need to create the registry key. Back up your registry first.
0
 
fortierAuthor Commented:
Thanks war1. I manually created the registry keys and was able to mount the database.  I could then move items to be salvaged to a fresh pst file.  One thing to note here is that I did see this article prior to posting this question, but the fact that the upper level registry key paths did not exist as the MS article suggested I got confused.  Once the entire registy path was created manually the database was able to be opened when over 20 gigs in size.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now