• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 302
  • Last Modified:

Windiws 2003 server (Std) with Exchange store keeps dismounting

We have a single Windows 2003 (std) and Microsoft Exchange running, which is quite full. Every day or so, when we come in, we find that the Information Store is dismounted. If we mount it manually it starts just fine.

Can anyone advise what steps we shouild take to trap this problem.

Many thanks.
0
nigelbeatson
Asked:
nigelbeatson
  • 5
  • 3
1 Solution
 
zulumikeCommented:
I had the same problem a few years ago. The reason was databaselimit on exchange 2003.
Read this MS article to see if it can apply to you as well and follow the instructions to fix.

http://support.microsoft.com/kb/912375/en-us
0
 
zulumikeCommented:
It could also be cause by to little free space on disk drive.
0
 
nigelbeatsonAuthor Commented:
how can we tell where the information store size is at, is it the actual size of the store file, or do we need to check somewehere else?

We have quite a bit of space free on the server drive.

Many thanks.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
zulumikeCommented:
If you don't have to many mailboxes you can just view all the mailboxes in exchange system admin and add their sizes together.

Or you can find your .edb and .stm files (by default you can find them in c:\Program Files\Exchsrvr\MDBDATA) and add up the size of them.
0
 
nigelbeatsonAuthor Commented:
Sorry for the slow response.

We checked the files sizes and they totalled more than 75Gb so I suspect your answer is correct.

We have asked the users to archive and delete some of their older stuff, and seem to recall that there is a utility that reads through the data files and creats a new clean copy. Do you think that this would be a good idea, and do you know what the utility is called?

Many thanks
0
 
zulumikeCommented:
OK.
Then the issue I talked about in my first comment don't apply, because your exchange databaselimit is at max, which is 75GB. NB: the file size doesn't always tell the truth so You should check your application event log for event id: 1221. If this says that the amount of free space is less than 10GB theres not much to do other than deleting/archiving and this amount will rise after ca 14 days.
Archiving and deleting old stuff would in many cases be enough, and is the recommended solution I think.
The alternative is to move the exchange-database to an exchange 2007 or 2010 server.

A utility that reads through data files and creates a new clean copy? Do you mean the Exchange defragment utility? http://support.microsoft.com/kb/328804
0
 
nigelbeatsonAuthor Commented:
Yes! tahts the ticket! Many thanks.
0
 
zulumikeCommented:
Thanks for the points :-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now