Re: Mailbox not re-enabled after increasing mailbox storage limits
- From: Bill Williams (DHL) <BillWilliamsDHL@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 8 May 2006 17:18:02 -0700
Thank you, Ben.
The specific problem did resolve itself in the two-hopur bracket described,
but I was distraught, because nowhere was there any indication of how long it
might take for it to happen, ie was it a Midnight thing, or a Sunday thing or
what?. This is another classic case where Microsoft has shoehorned this
Exchange server stuff, desighed for 4000+user setups into SBS which has (I
believe) at most 75 users and typically has only 5 to 30 users. These long
delays to avoid overstressing the Active Directory are irrelevant in the SBS
environment and a whole batch of registry entries should be set by Microsoft
to much more sensible values in the SBS environment.
====
Meanwhile I notice that the document you refer to describes the actual
symptoms as :
SYMPTOMS
Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 mailbox
size limits may not be enforced in a reasonable period of time. If users log
off and log on, performance does not improve. If you restart the information
store, the limits take effect immediately.
I notice that this mentions restarting the Information Store as doing the
trick. Again in the SBS environment it is much less traumatic to do such an
operation so it could well have been quoted as 'standard procedure'. However
this doesn't seen to be the same as dis-mount/mount the mailbox store, so
what exactly did they mean?
Bill
"Ben Hoffman [MVP Exchange]" wrote:
Hi Bill,.
How long has it been since you changed the setting, will take up to 2 hours
before the new limit will take affect, but good news is there is a registry
key you can modify to change the time it takes for the new limit to take
affect, see the following KB article:
http://support.microsoft.com/kb/327378/
Regards
--
Ben Hoffman
MVP Exchange
http://www.exchangeis.com
"Bill Williams (DHL)" <BillWilliamsDHL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:65F0DDF5-FEFD-4126-A774-9EFED06C4C8F@xxxxxxxxxxxxxxxx
There is a mailbox which exceeded its sorage limits last week.
By mistake on Friday last I set the limits to around 200 KB instead of
200MB
On discovering the mistake today, I have now set the mailbox limits to
much
bigger figures around 600 Mb upwards, but nothing I can do seems to make
Exchange pay any attention to the new figures. It is still rejecting
emails
to the account despite having manually run Mailbox Cleanup agent and
Mailbox
management process. I even tried dismount and mount of the mailbox store.
Why why why, are these new limits not having any effect? What do I need to
do to re-enable tthe mailbox. In the Mailboxes display in "Server
Management" I have turned on the extra columns and the Storage limits
Column
is showing "Mailbox Disabled".
- References:
- Re: Mailbox not re-enabled after increasing mailbox storage limits.
- From: Ben Hoffman [MVP Exchange]
- Re: Mailbox not re-enabled after increasing mailbox storage limits.
- Prev by Date: Re: Routing Group connectors & costs
- Next by Date: Re: Lost logs files
- Previous by thread: Re: Mailbox not re-enabled after increasing mailbox storage limits.
- Next by thread: Re: Public Folder Replication error
- Index(es):
Relevant Pages
|