[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Microsoft Exchange Server reported error (0x8004011D): The server is not available

Posted on 2008-10-08
4
Medium Priority
?
2,904 Views
Last Modified: 2012-05-05
All workstations on a system I support can no longer send/receive email through Outlook 2003. This started late yesterday.

ERROR Message:
Task 'Microsoft Exchange Server' reported error (0x8004011D) : 'The server is not available. Contact your administrator if this condition persists.'

Event Viewer Error:
The MAPI call 'OpenMsgStore' failed with the following error:
The attempt to log on to the Microsoft Exchange Server computer has failed.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0512-00000000

Operating System: Small Business Server 2003 SP1

All of the Microsoft Exchange Services are running and the Mailbox Store is mounted. The database sizes are: PRIV1.EDB - 10.5GB, PRIV1.STM - 6.2GB, PUB1.EDB - 215MB, PUB1.STM - 958MB. Total for all four files is about 18GB.

Is the 16GB limit per file or total? Will SP2 need to be loaded to increase the limit? Is there anyway to purge older emails since I cannot connect with Outlook 2003?

I am going in circles on this one - HELP!

I am tech savy, but I am an Exchange neophyte - so please be gentle.  :-)

Thanks

0
Comment
Question by:cpumantx
  • 2
  • 2
4 Comments
 
LVL 12

Assisted Solution

by:michaelgoldsmith
michaelgoldsmith earned 2000 total points
ID: 22671452
If you found yourself over the 16GB limit, the mailbox store would dismount itself and not mount until you ran an offline defrag of the database - a safety feature built into Exchange. If your mailbox store is really mounted, than you have another issue on your hands.
0
 

Author Comment

by:cpumantx
ID: 22672690
Do I need to load SP2 for SBE 2003? Run a defrag on the database? Where do I start?
0
 

Accepted Solution

by:
cpumantx earned 0 total points
ID: 22675054
Thanks michaelgoldsmith for "hitting me upside the head" with the obvious. Buried in the Event Manager Application Log was the error message about the database reaching its maximum size.

I successfully ran the ESEUTIL /D on the database (D:\APPS\Program Files\Exchsrvr\mdbdata\priv1.edb). After that, I was able to start the MS Information Store and mount the mailbox store. Outlook 2003 clients can now connect to Exchange.

I'll start trimming the emails immediately.
0
 
LVL 12

Expert Comment

by:michaelgoldsmith
ID: 22675673
Glad to assist.
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There’s hardly a doubt that Business Communication is indispensable for both enterprises and small businesses, and if there is an email system outage owing to Exchange server failure, it definitely results in loss of productivity.
Organisation is organized in a pattern to flow the day to day business, every application and system is interdepended on each other and when very important “Exchange Server downtime” happened.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
In this video I will demonstrate how to set up Nine, which I now consider the best alternative email app to Touchdown.
Suggested Courses

590 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question