ArticleBiz.com :: Free article content
Authors: Maximum article exposure. Publishers: Reprintable article content.  
BROWSE ARTICLES
ArticleBiz.com Home
Featured Articles
Recently Added Articles
Most Viewed Articles
Article Comments
Advanced Article Search
AUTHORS
Submit Article
Check Article Status
Author TOS
PUBLISHERS
RSS Article Feeds
Terms of Service

EDB Corruption If It Exceeds 16 GB Size Limit
Home :: Computers & Technology :: Email
By: Axel Culver Email Article
Word Count: 467 Digg it | Del.icio.us it | Google it | StumbleUpon it

  

Mailbox Store is a critical part of Microsoft Exchange Server. It contains all of the user mailbox and related data. A separate mailbox is created for every user in Exchange Server, which is accessible through the user profile in Outlook. But in some situations, the mailbox store doesn’t mount when it reaches 16 GB size limit. In such situations, you can not access data from the Exchange Server database and thus critical data loss situations occur. At this point, you are required to opt for Exchange Repair solutions to get your business critical and precious data back.

In a practical scenario, when you attempt to mount the Exchange Server mailbox store, the following Event ID might be logged into the Application Event Log of Exchange Server:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1112
Description: The database "Mailbox

Store (Server Name)" has reached the maximum allowed size. Attempting to unmount the database.
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Description: Information Store

(3160) The database D:Program FilesExchsrvrMDBDATApriv1.edb has reached its maximum size of 16383 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.

In such cases, to gain access of your critical data, you are required to repair and restore your corrupted Exchange Server database by carrying out Exchange Server Repair.

Cause

This behavior of Exchange Server might take place when the Exchange Server database exceeds its size limit, which is 16 GB in Exchange Server 2003 SP1 and earlier. Due to the exceeded size limit, EDB file (Exchange Server Database) gets damaged and thus it can not be accessed. Increased size of EDB file causes MDB (Messaging Database) to shut down automatically.

Resolution

To prevent this problem from being occurred in future, you are recommended to migrate to latest version of Microsoft Exchange Server. In order to resolve database corruption issue, go for Exchange Server Recovery solutions. Recovery is potential through third party applications, known as Exchange Server Repair software. These applications are powerful enough to methodically scan entire database and extract all of its inaccessible objects. These tools allow you to easily repair and restore damaged database as they come equipped with interactive graphical user interface. With read only demeanor, these programs are totally safe to use.

Stellar Phoenix Mailbox Exchange Recovery is the best every made and the most robust recovery tool for Microsoft Exchange Server 2003, 2000 and 5.5. It recovers all of the EDB file objects and is designed for Microsoft Windows 2003, XP and 2000.

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Exchange Repair software and Exchange Recovery. He is also a professional writer.

For more information, visit: MS Exchange Repair

Article Source: http://www.ArticleBiz.com

This article has been viewed 21 times.

Rate Article
Rating: 0 / 5 stars - 0 vote(s).

Article Comments
There are no comments for this article.

Leave A Reply
 Your Name
 Your Email Address [will not be published]
 Your Website [optional]
 What is one + four? [tell us you're human]
Notify me of followup comments via email


Related Articles


Copyright © 2009 by ArticleBiz.com. All rights reserved.

Terms of Service | Privacy Policy | Contact Us | Submit Article | Editorial