Wonderful!  Thanks to all for their input.  It's a load off my mind to
know the reason this happened.

 

-Paul

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Wednesday, May 05, 2010 11:55 AM
To: MS-Exchange Admin Issues
Subject: RE: Information Store unmounts

 

Yes.

 

The number fields were expanded. They should not rollover during the
lifetime of the known universe.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Maglinger, Paul [mailto:pmaglin...@scvl.com] 
Sent: Wednesday, May 05, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Information Store unmounts

 

Interesting.  I can't find where the log numbers were before it
happened, but looking at the current numbers it appears that they may
have started over from zero again when I got things going.  The KB
article mentions this is a known issue with Exchange 2k and 2k3.  Has
this been addressed in 2k7 and 2010?

 

From: Sean Martin [mailto:seanmarti...@gmail.com] 
Sent: Tuesday, May 04, 2010 4:46 PM
To: MS-Exchange Admin Issues
Subject: Re: Information Store unmounts

 

Transaction log sequence numbers...

 

http://support.microsoft.com/kb/830408

 

- Sean

On Tue, May 4, 2010 at 1:13 PM, Maglinger, Paul <pmaglin...@scvl.com>
wrote:

Forgot to mention also that we're running Enterprise, so no such
limitation.

 

________________________________

From: Richard Stovall [mailto:rich...@gmail.com] 
Sent: Tuesday, May 04, 2010 3:17 PM 


To: MS-Exchange Admin Issues

Subject: Re: Information Store unmounts

Boy, I haven't seen that one for a long time.  What version of Exchange
2003?  SP2?  IIRC Microsoft upped the max database size for Exchange
2003 Standard in SP2 from 16GB to 75GB, but you still had to modify the
registry to make it work. 

 

A quick Google search brings up the following kb article.

 

http://support.microsoft.com/kb/912375

 

HTH

 

On Tue, May 4, 2010 at 4:11 PM, Campbell, Rob
<rob_campb...@centraltechnology.net> wrote:

        Disk space

        
        -----Original Message-----
        From: Maglinger, Paul <pmaglin...@scvl.com>
        Sent: Tuesday, May 04, 2010 1:09 PM
        To: MS-Exchange Admin Issues
<exchangelist@lyris.sunbelt-software.com>
        Subject: Information Store unmounts
        
        
        Has anyone seen any instances where the Private and Public
Stores in
        Exchange 2003 just unmounts without any apparent reason?  So far
it's
        only happened once (knock on wood).  With my diagnostic logging
for
        MSExchangeIS System General set at Medium, Private General at
Maximum,
        the only thing I saw in the Event Viewer was that the stores
unmounted.
        All the services were running.  I haven't found anything that
points to
        what may have caused this.  I ran checks against the priv1.edb,
        pub1.edb, and e00.log files and the results came back clean.
But I
        couldn't simply remount the stores, but had to clear out the
logs and
        run eseutil /r before they would mount again.  Odd?
        
        -Paul

        
************************************************************************
**************************
        Note:
        The information contained in this message may be privileged and
confidential and
        protected from disclosure.  If the reader of this message is not
the intended
        recipient, or an employee or agent responsible for delivering
this message to
        the intended recipient, you are hereby notified that any
dissemination,
        distribution or copying of this communication is strictly
prohibited. If you
        have received this communication in error, please notify us
immediately by
        replying to the message and deleting it from your computer.
        
************************************************************************
**************************
        
        
************************************************************************
**************************
        Note:
        The information contained in this message may be privileged and
confidential and
        protected from disclosure.  If the reader of this message is not
the intended
        recipient, or an employee or agent responsible for delivering
this message to
        the intended recipient, you are hereby notified that any
dissemination,
        distribution or copying of this communication is strictly
prohibited. If you
        have received this communication in error, please notify us
immediately by
        replying to the message and deleting it from your computer.
        
************************************************************************
**************************
        
        

 

 

Reply via email to