Solved

Increasing Exchange 2003 Database size with registry not working

Posted on 2007-03-30
5
417 Views
Last Modified: 2008-11-02
We are running Exchange 2003 SP2.  One user started recieving the mailbox store message is full.  I checked the db and the file size was 17gb.  After seaching through this knowledgebase and MS KB articles, I added the registery entries to increase the database size to 75.  I restarted the Information Store.  The change did not take affect.  I dismounted and mounted the mailbox store, it still did not work.  Then I restarted the server and still did not work.  No other user has recieved the message and they continue to function normally.

The user that gets the message I have deleted his outlook profile and recreated with a new OST.  He has 1.8 gb of email but that is only second to one other person who has a 2 gb mailbox and does not get the error message.

Any ideas on how to get the new db size to work or is it a time thing?
0
Comment
Question by:jbmos2333
5 Comments
 
LVL 15

Expert Comment

by:czcdct
ID: 18825786
If it's not working then I assure you that there is a typo somewhere.
0
 
LVL 104

Assisted Solution

by:Sembee
Sembee earned 200 total points
ID: 18826583
If you have hit the 18gb limit then you would get some entries in the event viewer. Users do not get email messages. Therefore I suspect that this is a problem with the mailbox, not the store.

On the topic of the size of the store, if you have set the limit correctly then an entry will be made in the event viewer when the server starts.

Simon.
0
 
LVL 1

Accepted Solution

by:
tlcsupport earned 300 total points
ID: 18835919
I had a similar issue. I managed to (finally) get it working by deleting the registry key, and re-creating it - as per http://www.runpcrun.com/16gb-limit-exchange-2003. The important thing to look at is the Application Event Log File ID 1216 which should appear after you make the change.. If this does NOT show the new size limit that you entered after restarting the Information Store, then it has not worked. For some reason, I had to create the registry key about 4 times before it finally worked. Sorry this doesn't appear very scientific, but it worked for me!!!
0
 

Author Comment

by:jbmos2333
ID: 18836185
I finally got it to work.  It took on the second restart.  There weren't any typos, but on the second restart of the server it finally appeared in the Application log.  Strange, but I'm good now.
0
 

Expert Comment

by:CFRPC
ID: 22864157
Same issue, and I assure everyone that I didn't typo.

1) net stop msexchangeis
2) Added the dword registry key
3) net start msexchangeis

kb912375 helped, but I had to trial and error the net stop sequence.

Hope this helps someone else who isn't receiving the ID 1216 in the application event view.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question