none
Exchange 2003 Maximum Mailbox Size

    Question

  • Hi everyone,

    I know that Microsoft set Exchange 2003 mailboxes to a maximum size of 2GB, but with an edit to ADSIedit, that value can be changed.  Does anyone know if Microsoft supports Exchange 2003 mailbox sizes above 2 GB?  I have Exchange Enterprise, so I know database size is not an issue.  Thanks in advance for your help.
    Monday, September 08, 2008 1:24 PM

Answers

All replies

  • Hello Pete,

     

    I guess, it should be supported since many organizations require it for some of the VIPs....

    You receive a "Specify a value from 0 through 2097151" error on Limits in Mailbox Store properties

     

    Item count in various folders that matters not mailbox size.

     

    Some of the recommended readings...

    Recommended Mailbox Size Limits

    So you want to know about High Item Counts and Restricted Views

    Version Store issues revisited - Event ID 623 at Information Store service startup

    Monday, September 08, 2008 2:51 PM
  • Following the first article above, I've (unfortunately) configured many mailboxes > than 2GB in Exchange 2003 server in past projects and it works as advertised.  The 2GB limit is really just a limitation hard-coded into the Exchange System Manager console.

    Monday, September 08, 2008 11:32 PM
  •  

    Dear customer:

     

    Thanks for Amit Tank and Jeff Schertz’s reply.

     

    Yes, of course. You can set your mailbox storage limit to exceed 2 GB according to the previous knowledge base article. By default the maximum mailbox storage limit is 2 GB.

     

    Rock Wang - MSFT

    Tuesday, September 09, 2008 6:30 AM
  • This is just a FYI...  One of the mailbox size for an untouchable VP is currently currently at 5.1 gig and no major issue so far*.  We're still doing anything we could in trying to archive that mailbox.    Full backup runs fine nightly.  Exmerge to PST file gets an error.  other than that, it seems okay.

     

    Wednesday, October 08, 2008 6:26 PM
  •  Fiveby5 wrote:
      Exmerge to PST files get error.  other than that, it seems okay.

     

     

    I've used Exmerge numerous times on >2GB mailboxes.  What error message are you getting?  Is this the 2003 version of Exmerge?

     

    Also for everyone else, this article might help users with big mailboxes:

     

    Optimizing Outlook 2007 Cache Mode Performance for a Very Large Mailbox

    Wednesday, October 08, 2008 6:38 PM
  • here is the error part of the exmerge log:

     

    [15:43:19] Initializing worker thread (Thread1)
    [15:43:19] (Thread1) processing the range of mailboxes from 'John Smith' to 'Joe whoever' (index 13 to 25)
    [15:43:19] Copying data from mailbox 'John Smith' ('JOHN') on Server 'EXCHANGE' to file 'D:\PST.FILES\JOHN.PST'.
    [16:11:13] Error copying messages from folder '\Inbox - company1\ETA 777 and 757' (MAPI_W_PARTIAL_COMPLETION)
    [16:11:13] Trying to copy messages in folder '\Inbox - Company1\ETA 777 and 757', individually. To avoid duplicates in the target store, messages will be merged and not copied into the target store.
    [16:11:13] Error getting Contents Table.  - 0x80040600
    [16:11:13] Error encountered while individually copying messages from folder '\Inbox - Company1\ETA 777 and 757'.
    [16:11:13] Errors encountered copying the messages in folder '\Inbox - Company1\ETA 777 and 757'. One or  more messages may not have been copied.
    [16:11:13] Error getting Hierarchy Table (foldername1)
    [16:11:13] Error creating new folder  (foldername1)
    [16:11:13] Error getting Hierarchy Table (foldername2)
    [16:11:13] Error creating new folder  (foldername2)
    [16:11:13] Error getting Hierarchy Table (foldername3)
    [16:11:13] Error creating new folder  (foldername3)
    [16:11:13] Error getting Hierarchy Table (Inbox - Tim whoever)
    [16:11:13] Error creating new folder  (Inbox - Tim whoever)
    [16:11:13] Error getting Hierarchy Table (Inbox - name1)

     

    note:

    * Total items in this mailbox is 44,146 items; size is 5.09 gig; 

    * exchange 2003  with Merge Program, v6.5.7529.0

    * the PST file got created but only has 2 gig (even the mailbox size is at 5 gig)

     

    Below is the log for the second run of exmerge of the same mailbox at a different time.

    [13:30:02] Copying data from mailbox 'John Smith' ('JOHN') on Server 'EXCHANGE' to file 'D:\TEMP\JOHN.PST'.
    [13:57:12] Error copying messages from folder '\Inbox - differentname1' (MAPI_W_PARTIAL_COMPLETION)
    [13:57:12] Trying to copy messages in folder '\Inbox - differentname1', individually. To avoid duplicates in the target store, messages will be merged and not copied into the target store.
    [13:57:12] Error getting Contents Table.  - 0x80040600
    [13:57:12] Error encountered while individually copying messages from folder '\Inbox - differentname1'.
    [13:57:12] Errors encountered copying the messages in folder '\Inbox - differentname1'. One or  more messages may not have been copied.
    [13:57:12] Error getting Hierarchy Table (Inbox - differentname2)
    [13:57:12] Error creating new folder  (Inbox - differentname2)
    [13:57:12] Error getting Hierarchy Table (Inbox - differentname3)
    [13:57:12] Error creating new folder  (Inbox - differentname3)

     

    Mike, are you able to exmerge your 7 gig mailbox without any issue? 

     

     

    thank you

     

    Wednesday, October 08, 2008 8:01 PM
  • Hmm, I could be mistaken.  I just tried on a demo box and got errors myself.  Do you have any Exchange 2007 in the enviroment?  export-mailbox would allow you to get around this issue.

     

    there are also suggestions to use Outlook instead, or put a filter on exmerge so the content is less than 2gb. 

     

    Wednesday, October 08, 2008 10:00 PM
  • We’re on a pure exchange 2003 environment native mode.   Yes, those suggestions work.    I was just wondering what's the "real" max mailbox size before it kills the *.edb.   After reading all the links in this thread, this mailbox with 44K items and 5.1 gig in exchange 2003 still have room to grow.^_^  hahahaha   (I dont' think I can laugh when the real issue hits me).     I know exactly what to do...as you guys suggested, try to keep it below 5K in the number of items. 

    Thursday, October 09, 2008 3:03 PM
  • I know someone with a 15GB mailbox.  Their Outlook "Cached Mode" is just stupid slow, but nothing is actually "broken".

     

    Thursday, October 09, 2008 3:08 PM
  •  

    I have about 50 users over 5 GB, one grew to over 22GB with no problem other than causing Outlook issues on her notebook because on "cached mode".  If you uncheck the size limitation I don't know what the max is but, it is at least 23GB.  I have noticed that if you want to limit the size you cannot enter a limitation above 2GB, I would love to find a way to change that.
    • Proposed as answer by neogeo147 Friday, February 17, 2012 2:50 AM
    • Unproposed as answer by neogeo147 Friday, February 17, 2012 2:50 AM
    Thursday, October 16, 2008 2:20 AM
  • Follow the below steps when you get the error 0x80040600 , when you try to send and receive message:
     - Run the Inbox Repair Tool to diagnose and repair errors
     - To recover your data, you must first run the Inbox Repair Tool.

     

    To get more instructions on this refer: http://www.omnitechsupport.com/forum/topic/1092/0x80040600-and-an-error-message-an-unknown-error-has/

    Monday, March 29, 2010 6:06 AM
  • I just had this happen today 02_16_2012....

    First I started having users not be able to sync there mobile device to the exchange server but it was just there calendar items. They could add calendar items to there device but it wouldn't show up in outlook and vice versa.

    It then grew to having even more and more users getting issues and even myself on my own phone. So I went to my front end exchange server and I looked in the event viewer and noticed a bunch of 500 Error 3005 event ID..

    As I dived in more and more I noticed that some users were over 6GB and it wasn't really the size that matter it was how many Items were in there. Make sure you look at that in the ESM exchange system manager. So as I started having them archive and remove emails and purge other tombstone accounts things started to function a whole heck faster and sync better. To many items = problems syncing. I might add we had no problem with Outlook with it being that large it just messed up Active Sync.

    So I'm just saying, if you start getting 500error code or if you update your front end and back end servers and start getting 409 errors make sure that Store.exe and Massync.dll are on the same version. (right click properties - version tab)

    I unfortunetly listened to some other google folks and ended up deleting my Microsoft-Server-ActiveSync in IIS and wow after re-adding it, just make sure you name it just like how its spelled above otherwise you will run into more and more problems.

    Let me just say I was on No Lunch - No Sleep - No Luck road to a wonderful day of Permissions, Deletions and HELL!!!

    I've heard they have upped that in Exchange server 2010 to like 100,000 items.

    Friday, February 17, 2012 3:03 AM