Oftentimes, upgrading to Exchange 2000 Server Service Pack 3 (SP3) or later creates problems while mounting Exchange information store databases. You may also experience this issue when you upgrade from Exchange 2000 SP2 to Microsoft Exchange Server 2003. At this stage, the Application log of Event Viewer may display the following event ID error message: Continue reading
File-level damage is seen quite often on databases in MS Exchange that causes problems at the higher levels, i.e. database level and application level. File-level damages are known problems caused by defects in the driver, firmware, or hardware. These issues either indicate an invalid checksum or an accessed page returning invalid page header during a read operation. Generally, an invalid page number is encountered due to file system corruption or wrong mapping of various pages into your database file. This usually results in error -1019 (JET_errPageNotInitialized). Continue reading
MS Exchange 2010 introduced a handful of new features to facilitate easy database administration and high availability of information. A major enhancement was made to its recovery capabilities with the introduction of a powerful feature called ‘Single Item Recovery’. With the help of this feature, you can recover individual items in your Exchange database, thereby eliminating the need to restore from a point-in-time backup. Continue reading
MS Exchange Server is one of the advanced and finest email-server applications, used by many organizations around the world. Security, high availability, fast communication, effective management of user’s data etc. are some features that made it unique and popular. Despite these advanced features, there are times when an Exchange database file gets corrupt. When an item in database gets corrupt, it starts throwing errors and stops responding. Continue reading
