Re: Exchange 2003 sp2

Tech-Archive recommends: Fix windows errors by optimizing your registry

OK - it sounds like the first registry entry is ok. Did you create the
other registry keys? Are you sure that the SP2 install completed
successfully? If so, then as I previously asked, what does event 1216 show
when the Information Store service starts? It should show you what the
current size limit is set to.

If the event reports the correct size, but BPA isn't, I'd check and see if
there is a newer version. ExBPA (or the updates) do not show up in Windows
Update. Check on the exchange download site. I'm showing ExBPA current
version is 2.5.
http://www.microsoft.com/downloads/details.aspx?familyid=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


<alexpt@xxxxxxxxxxx> wrote in message
news:1144166475.822453.63460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Ben
What do you mean when you say "values entered in Decimal, NOT hex?"; i'
ve created the key respecting upper & lowercase, the value i entered
it's 22 decimal(16hex)
where am i in fall ?
thanks again
alessandro


Ben Winzenz [Exchange MVP] wrote:
And what does event 1216 say from your Application log when the store
starts?

Are you positive that you have configured all the registry settings
correctly? values entered in Decimal, NOT hex?
http://blogs.technet.com/exchange/archive/2005/09/14/410821.aspx

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"phildg" <phildg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DC91B9DC-0400-4ECD-8D24-683F54C7CDEF@xxxxxxxxxxxxxxxx
Hi Alex,

I'm experiencing exactly the same problem. Did you find a solution in
the
meantime?
--
Regards, Phil from Belgium


"alexpt@xxxxxxxxxxx" wrote:

Dear all

Sorry to disturb you, i've setup the sp2 onto our exchange server 2003
(sbs 2003 standard edition operating system equipped), to take
advantage of the 75gb exchange db limit.

The update seems ok, i've put the 3 dword key into registry and reboot
the server, but the Best Practices Analyzer Tools notify again the
16Gb
db limit.

I've check about updates of the "Best Practices Analyzer Tools" and
Exchange server sp2 update onto windows update but no update available
for both

The exchange release obtained from the exchange manager help is menu
6.5.7638.1, there are others way to check the db limit ? or may be
i've
made some mistakes during update

thanks in advance

Alessandro Piatti





.

Relevant Pages

  • OWA Setup - HELP PLS
    ... running Exchange Server 2000...all of these articles ... I don't have the "exact" registry key...I have ... >Access to connect to Microsoft Exchange Server ... two ports need to be statically mapped. ...
    (microsoft.public.exchange2000.setup.installation)
  • RE: exchange 2003 sp2 on sbs server 2003
    ... Justin's suggestion is right on the point, it is recommended you install ... and then install Exchange 2003 SP2. ... further reference after installing the Exchange 2003 SP2: ... You can update the IMF Version 2 in the Exchange Server 2003 SP2: ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 Gig mailbox storage limit
    ... service pack for SBS 2003 ... If you apply a registry hack it is. ... Without any changes, just applying SP2 for Exchange, the Store ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 sp2 intelligent message filter tab missing
    ... Either you are not running Exchange SP2. ... Management Tools are installed and SP2 was not applied on this machine. ... Open Add/Remove programs on the Exchange Server machine. ... IMF Tune - Unleash the Full Intelligent Message Filter Power ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with Outlook 2007 SP2 accessing Exchange 2003
    ... Outlook2007 SP2. ... I can connect to my exchange server 2003 if I logged as domain user on my ... Error I am getting is "The connection to Microsoft Exchange is ...
    (microsoft.public.officeupdate)