jbmos2333
asked on
Increasing Exchange 2003 Database size with registry not working
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?
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?
If it's not working then I assure you that there is a typo somewhere.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
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.