How to solve Exchange Server Error – “Non-database file or corrupted database.” ?

February 6th, 2011 | bobluisusa

In MS Exchange Server, the database bears two types of inconsistencies – Physical and logical. Hardware failure problem lead to physical database corruption situations and the logical database corruption is occured due to deletion of edb.log file and write-back caching issues. The physical corruption affects the database pages and could be resolved easily. On the other hand Logical database corruption is hard to be detected by the Server administrator. However, Anyone using Exchange Server has likely experienced the error message (as mention below) at times when the user tries to access data from a corrupted database. This is a common database error that occurs whenever there is either logical or physical database corruption and you need to go for EDB Recovery solution.

As discussed, you might face the error message as mention below:

“msgidJetDatabaseCorrupted.”

This error is fugacious and under its detail, you see the following error message:

“Non-database file or corrupted database.”

This error description is logged with Event ID 9511 in aapplication event log file.

Cause:

Such behavior is usually exhibited when the information store service of server is trying to access data from a corrupted or non database file that is logically or phsically corrupted.

Solution:

To fix this problem, It is necessary to find the specific cause of this issue. You can use inbuilt database recovery tool to get rid of this problem. Follow these steps to solve the Exchange database corruption issue:

1)Dismount the corrupted database
2)Backup the Exchange database
3)Use eseutil /g command to check database integrity
4)Use eseutil /p command to repair the Exchange database

Sometimes this problem will go away with above steps but in case of failure of the repair utility, you need third party EDB Repair tool to repair corrupt exchange database. This Exchange Server Repair software uses extensive scannning algorithm to scan the completed database and repair the database in each instance of corruption.

Stellar Phoenix Exchange Mailbox Recovery Software is an advanced Exchange Repair tool that repairs and restores corrupted databases. The tool is devised and developed with highly graphical user interface feature and no prior technical skill is needed to operate it. The EDB Repair Software supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. This amazing tool has the capability to recover all deleted user mailboxes and is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Posted in Uncategorized | No Comments »

Repair and Restore Unmountable Exchange Server Database

July 9th, 2010 | bobluisusa

Source: http://www.ms-exchange-server-recovery.com/blog/

Microsoft Exchange Server lists all the transaction, which you performed on the server, in Transaction Log File. It helps you to find out the details about failed transactions and fix the particular problem. There are some cases where the transaction log file of MS Exchange Server may corrupt and leave your database in unusable state. In case of transaction log file corruption, you may not mount the database and encounter critical data loss situations. At this stage, Exchange Server recovery is the only way to get your precious data back.

For instance, you may run across the below error message when you attempt to mount an Exchange Server mailbox or public store after log file corruption:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: c1041724”

At the same time, you may see any of the below events in Application Event Log of Microsoft Exchange Server:

1. Event ID: 465
Source: Ese98
Type: Error
Computer: Server1
Information Store (2184) Corruption was detected during soft recovery in logfile C:\Programme\Exchsrvr\mdbdata\E00000E8.log. The failing checksum record is located at position 6531:471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable.
For more information, click http://search.support.microsoft.com/search/?adv=1.

2. Event ID: 454
Source: Ese98
Type: Error
Computer: Server1
Information Store (2184) Database recovery/restore failed with unexpected error -501.

Subsequent to the above errors, you cannot mount the database and access stored data from it. In order to gain access of your valuable data, you must fix this problem through Microsoft Exchange recovery solutions.

Root of the problem:

This behavior generally occurs due to log file corruption or Exchange Server public store corruption. In both the situations, database can not be mounted and accessed.

Resolution:

You need to remove the log file and reboot Exchange Server, if problem is caused by log file corruption. On the other hand, if public store corruption is causing this behavior, you need to repair database using Exchange recovery software. The Exchange recovery tools successfully handle all corruption scenarios.

Stellar Phoenix Mailbox Exchange Recovery is a read-only software with simple graphical user interface to offer safe and easy recovery. The software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Tags: , , , , , , , , ,
Posted in Exchange Recovery | No Comments »

What Causes Hard Recovery Failure in Exchange Server?

June 30th, 2010 | bobluisusa

In Microsoft Exchange Server, you must replay the log file after restoring your EDB (Exchange Server database) from an online backup. This process is known as Hard Recovery. It helps you to recover your Exchange Server database in case of database corruption or database failure. However, in some situations, the Exchange Server hard recovery fails and the database remains in inaccessible and unusable state. At this point, you need to repair and restore the corrupt database using advanced Exchange Server Recovery tools.

As a practical example of this problem, the hard recovery of Exchange Server with Eseutil /cc may fail and you come across the below error message:

“Operation terminated with error -939523485 (Existing log file is not contiguous.) after 0.481 seconds.”

At the same time, you may see any of the following Events in the Application Event Log of Microsoft Exchange Server:

1.Event Type: Information
Event Source: ESE
Event Category: General
Event ID: 101
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) The database engine stopped.

For more information, click http://search.support.microsoft.com/search/?adv=1.
2.Event Type: Error
Event Source: ESE BACKUP
Event Category: Callback
Event ID: 904
Date: 8/30/2002
Time: 11:32:31 PM
User: N/A
Computer: ServerName
Description: Information Store (1504) Callback function call ErrESECBRestoreComplete ended with error 0xC8000263 Existing log file is not contiguous.

For more information, click http://search.support.microsoft.com/search/?adv=1.

After this behavior, you may come across critical data loss situations. To retrieve data in such cases, you need to figure out the cause of this behavior and perform Microsoft Exchange recovery by fixing it.

Root of the problem:

You may come across this problem if the old log files are not in sequence with log, which is mentioned in the Restore.env file. You can file all the required log files using Eseutil /mh utility.

Resolution:

To fix this problem, follow the below steps:

1.View the content of Restore.env file using Eseutil /mh utility.
2.Record range of log files.
3.Remove the log files that are out of range.

If the above method does not work, you need to repair and restore the damaged Exchange Server database using third-party EDB recovery software.

The Exchange Recovery tool are powerful enough to thoroughly scan entire database and extract all inaccessible data from it. They have rich and interactive graphical user interface to ensure easy recovery in all corruption scenarios.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and powerful exchange database recovery utility to offer assured recovery of damaged database. The exchange 2003 recovery software restores all EDB file objects, such as emails, notes, contacts, tasks, journal, attachments, and appointments. It works with Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Tags: , , , , , , , ,
Posted in Edb Recovery, EDB Repair, Exchange Recovery, Exchange Repair | No Comments »

Low Disk Space or Database Corruption Prevents you to Write Data to EDB File

June 14th, 2010 | bobluisusa

Are you unable to write data to Microsoft Exchange Server database? Is your EDB (Exchange Server database file) inaccessible? This behavior may occur due to either low disk space on Exchange Server computer or corrupt EDB file. If the database is corrupt, you need to restore it from the most recent backup to prevent data loss situations. However, in case backup is not valid or updated, you need to opt for Exchange Recovery solutions to retrieve data from the database.

In a practical scenario, the Information Store Service of Exchange Server may fail to start and you encounter the below errors in Application Event Log of Exchange Server, while read/writing data from/to EDB file:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 482
User: N/A
Description:
Information Store (4360) First Storage Group: An attempt to write to the file “D:\Program Files\Exchsrvr\mdbdata\res2.log” at offset 4194304 (0×0000000000400000) for 1048576 (0×00100000) bytes failed after 0 seconds with system error 112 (0×00000070): “There is not enough space on the disk.”. The write operation will fail with error -1808 (0xfffff8f0). If this error persists then the file may be damaged and may need to be restored from a previous backup.”

You can not access the database after above error. To gain access of your valuable data in the EDB file, you need to identify the root of this issue and perform Microsoft Exchange recovery by resolving it.

Root of the problem:

You may face this behavior of Exchange Server due to any of the below reasons:

1. You do not have sufficient free space on the Exchange Server hard drive. The Error 0×00000070 entails ERROR_DISK_FULL and Error 0xfffff8f0 entails JET_errDiskFull.
2. EDB file is corrupt and Exchange Server can not recognize it.

Resolution:

You can try out any of the below methods to sort out this problem:
1.If problem is caused by low disk space, remove some files to free up disk space.
2.If database corruption is causing the issue, repair and restore the database using powerful and advanced commercial Exchange recovery software.

The Exchange recovery tool carry out in-depth scan of entire Exchange Server database and extract all inaccessible data from it. You need not to be technically sound to use these tools and repair the database as they have interactive graphical user interface.

Stellar Phoenix Exchange Mailbox Recovery is the most powerful, yet easy to use exchange database recovery application to ensure easy recovery in all EDB corruption scenarios. The Exchange 2007 recovery software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores inaccessible objects of EDB file, such as emails, notes, tasks, contacts, journal, calendar items, and more.

Tags: , , , , , , , , , ,
Posted in Exchange Recovery | No Comments »

How to recover corrupted PST file when it is inaccessible in Outlook 2000

June 7th, 2010 | bobluisusa

A PST (Personal Storage Table) file is the proprietary file for Microsoft email applications such as Microsoft Outlook. It stores all the related information of MS Outlook such as emails, contacts, calendar entries, tasks, meeting notes, journals, etc. At times, this PST file can get corrupt that leads to its malfunctioning and, at times, inaccessibility. Such behavior is caused due to virus infections, power outages, exiting Outlook abruptly, CRC errors, etc. In such cases, you should use appropriate methods to resolve the issue. However, if you are unable to sort out the issue then you should use a third-party PST Recovery software to recover PST file.

Consider a scenario wherein you have Outlook 2000 installed in your system. When you attempt to run it, it fails to open. An error message is displayed, that is:

“Unable to display the folder,[path]Outlook.pst could not be accessed, access denied.”

Cause:
The root cause of this error message is that the Outlook.pst file has corrupted as it contains several errors in it. Because of this, Outlook is unable to read the hierarchy information from the PST file and, hence, the error message is displayed.

Resolution:
To resolve the error message and to be able to successfully access Outlook again, you need to perform the following steps:

1.Exit Outlook.
2.Locate the Scanpst.exe file to run the Inbox Repair tool.
3.Run the Inbox Repair tool. This tool is able to read and rebuild the item headers and destroys whatever it fails to read. So, make sure that you have made a backup of the PST file before running this tool.
4.Open Outlook and check if the issue is resolved. If it is not so, then you can perform the following methods as well:
i.Run Scandisk.exe to check for errors in the file.
ii.Try shifting the location of the PST file to check whether this error is location specific or not.
iii.Try creating a new Outlook profile and add the PST to the new profile. Now check whether it is resolved or not.

The aforementioned methods should be able to sort out the issue. However, if it is not so then you should use a third-party PST file recovery software. Such PST recovery tools are read-only in nature that do not overwrite the original data while scanning the corrupted file.

Stellar Phoenix Outlook PST Repair is a PST Recovery Software that enables you to recover data from corrupted PST files. It is supported by Outlook 2010 (Beta), 2007, 2003, 2002, and 2000. This PST recovery tool is able to recover various objects of Outlook such as emails, contacts, calendar entries, notes, journals, etc. In addition, this tool preserves the formatting of the RTF and HTML messages after the PST recovery. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.

Tags: , , , , , ,
Posted in PST Recovery | No Comments »

Resolving Event 1148 with Rule Synchronization Error

April 17th, 2010 | bobluisusa

A storage group in Microsoft Exchange Server Information Store contains one or more mailbox stores, depending on the version of Exchange Server you use and requirements of the organization. Mailbox stores are the most critical components from data preservation perspectives as they comprise of system and user mailboxes. If corrupted, mailbox store causes serious problems in the working of an organization. A mailbox store is further comprised of two files, namely Priv1.edb and Priv1.stm. Corruption usually affects Priv1.edb file and occurs because of typical reasons like, database dirty shutdown, anti-virus software scan, virus infection, and network issues. When corrupted, EDB file on being accessed, prompts errors under a few event IDs, which can be read from application event log. Following is one such event IDs that generally occurs because of database corruption and requires EDB Recovery solutions.

Suppose you are an Exchange Server administrator with a mailbox store that contains hundreds of user mailboxes. Since the store contains critical information required for uninterrupted working of the organization, its consistency cannot be compromised. But you observe that the below mentioned event ID is repeatedly observed in application event log:

Event Type: Error

Event Source: MSExchangeIS Mailbox Store

Event Category: Rules

Event ID: 1148

Date: date

Time: time

User: N/A

Computer: Computer_Name

Description:

A rule synchronization error (Read verification error) has occurred.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This error occurs irrespective of the fact that all Exchange Server services are working without any issue.

Cause

Exchange database is corrupt.

Note: The same error can also occur if required data is missing.

Solution

Following are the possible solutions that can help you recover from such database corruption issues:

  1. Run ‘Eseutil’ with ‘/r’ switch for soft database recovery

  2. Restore database from the last available backup

  3. Execute ‘Eseutil’ with ‘/p’ switch to repair the database. But make sure to backup the database before running this command. This prevents data loss.

  4. Use a third-party EDB Recovery Tool to repair and restore the corrupted Exchange database

EDB Recovery software are exclusive tools built to scan and repair the damaged EDB database file safely and effectively. One of the best utilities is Stellar Phoenix Mailbox Exchange Recovery software with deleted mailbox recovery capability, this EDB Recovery Tool supports MS Exchange Server 2007, 2003, 2000, and 5.5 and can extract individual mailboxes as *.pst files.

EDB Recovery

Tags: , , , , , , ,
Posted in Exchange Recovery | No Comments »

Solve MS Outlook Error – 0×80040154

April 16th, 2010 | bobluisusa

Microsoft Outlook error ’0×80040154′, is one of the most common errors that you receive when sending or receiving an e-mail message. In Outlook, this error appears, prefixed with ‘unknown error’ and requires Outlook Inbox Repair steps.

Error ’0×80040154′ generally occurs because of unregistered file(s) or some registry corruption issues. When it comes to Microsoft Outlook 2003, this problem may root from inetcomm.dll file. Here are some common solutions that can help you isolate the given problem:

  1. First, you need to click ‘Start’ and then ‘Run’.

  2. Next, type ‘regsvr32 inetcomm.dll’ and restart your computer.

  3. Then you can start Outlook and see if the problem goes away. In that case, you can stop here as the problem was due to an unregistered inetcomm.dll file.

  4. If the problem persists, you should restart your computer in ‘Safe Mode with Networking’ and then start MS Outlook. In case, this method works for you, the problem is related to a conflicting program or a virus. So, you need to uninstall the problematic program and/or run an antivirus software.

  5. If the above method also fails, you should remove the Outlook profile you use, after backing up all the e-mail folders and settings. You can either delete the profile or add a new one. Next, you can setup a new account and later import old folders.

  6. In case, the issue still persists, you should try repairing Microsoft Office or Microsoft Outlook. If this doesn’t work, you can reinstall MS Outlook. Make sure that you backup your PST and settings first.

However, if MS Outlook is damaged as a result of corrupted PST, the above methods will not work. This is because when you reinstall or repair Outlook, the old PST file(s) are not deleted. Thus, you need to repair them using PST Repair solutions.

Stellar’s Outlook Inbox Repair Software can repair and restore corrupted PST files. These repair software also restore the data to a secure location, while maintaining the original indexes and data structure of the original file. Moreover, these utilities can be used in any case of PST file corruption.

Stellar’s Inbox Repair Tool is a reliable, high-end tool that is used to repair a corrupted PST. This Repair Inbox tool creates a new PST to restore its e-mails, notes, contacts, etc. The software supports MS Outlook 2007, 2003, 2002, and 2000 and is a safe tool, as it uses risk-free algorithms.

Tags: , , , , , , , ,
Posted in PST Recovery | 1 Comment »

Resolving MS Outlook 2003 Error: Unable to send this item

April 5th, 2010 | bobluisusa

Most of the Microsoft Outlook problems are reflected when a user tries to send or receive e-mail messages. These issues can be related to Outlook profile, mail configuration, a third-party application, Outlook data file (*.pst), and various similar factors. In comparison to other concerns, PST file damage can bring severe consequences as this is the only file that holds all your e-mails, contacts, calendars, and information of Outlook. Many PST corruption problems can be easily resolved by Outlook’s built-in tool called Inbox Repair Tool (Scanpst.exe), but one should always backup PST before running this tool. In cases when Scanpst fails to repair the damaged file, a commercial PST Recovery utility can be used.


To illustrate, consider a user of MS Outlook 2003. The user receives all e-mails with no issues, but each time when he/she tries to send an e-mail message, the operation fails and the below error message pops up:

“Unable to send this item.”


When the message is viewed in Outbox folder, it has no corresponding item, but Sent Items has, even when the message has not been sent.

Cause


MS Outlook 2003 exhibits the described behavior in case:

  • Some problems appear in your e-mail account configuration
  • Connection problems occur with ISP (Internet Service Provider)
  • Outlook PST is damaged

Solution:


  • Create a new Outlook profile that includes all those services that are giving problem and attach the old *.pst file. If this doesn’t solve the problem, then,

  • Check if a secure and proper Internet connection is available.

  • Make sure that TCP/IP is your default protocol

  • In case the problem is due to PST damage, repair the PST using Outlook Inbox Repair Tool. For this, locate the program file-’scanpst.exe’, double-click it and proceed as prompted

However, Inbox Repair Tool is the not the perfect PST Recovery Tool in all instances of PST corruption. To repair the PST that cannot be repaired by this tool, you need to use a third-party PST File Recovery utility. These software run most effective scanning algorithms to repair a corrupted PST.


PST Recovery Software is an advanced PST file repair application that is designed to restore data from damaged PST created with MS Outlook 2007, 2003, 2002, and 2000. The simple PST Recovery Tool can also recover deleted e-mails and is compatible with Windows 7, Vista, XP, 2003, and 2000.

Tags: , , , , , , , ,
Posted in PST Recovery | No Comments »

IIS Metabase Corruption May Cause Exchange Server Database Corruption

March 23rd, 2010 | bobluisusa

Microsoft Exchange Server is a well-known application that is used to create collaborative messaging environment. It is installed on server and can be accessed from client computer using Microsoft Outlook. Exchange Server 2003 and Exchange Server 2000 use MS IIS (Microsoft Internet Information Services) to provide Exchange-related services. All configuration settings of the IIS are stored in IIS metabase. The formation of metabase contains various settings of properties of different nodes. However, in some situations the metabase may get damaged and cause critical EDB (Exchange Database) corruption scenarios. To sort out this problem, you need to opt for Exchange Server Recovery, in case of unavailability of backup.

Corruption of IIS metabase and Exchange Server database is a very serious concern. It can cause several Exchange Server vulnerabilities and make Exchange-related services unusable. In case of metabase corruption, you may encounter the below error message:

“[15:52:34] – The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server. — ID:62145 –
[15:52:34] Prerequisites for Microsoft Exchange Messaging and Collaboration Services failed: The component ‘Microsoft Exchange Messaging and Collaboration Services’ cannot be assigned the action ‘Upgrade’ because:- The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server.”

The above error, in particular, occurs due to missing metabase entries. If various users perform transactions after metabase corruption, the EDB file may encounter several inconsistency issues. In such situations, to bring your Exchange Server in working state, you need to fix this behavior using Microsoft Exchange Recovery Tool.

Resolution

You can use Adsutil.vbs, an inbuilt utility of Microsoft Exchange Server, to locate metabase objects. However, if you encounter the following error while using Adsutil.vbs tool, you have to reinstall Internet Information Service and Microsoft Exchange Server:

“-2147221020 (0x800401e4)
Error trying to enum the object (GetObject failed)”

Although, reinstalling the Exchange Server and IIS may fix this problem, but it can not repair the corrupted Exchange Server database. In order to repair and restore the damaged EDB file, you need to use third-party Exchange Recovery Software.

The applications are particularly designed to carry out systematic scan of entire EDB file (using advanced scanning mechanisms) and to extract all damaged and inaccessible objects. They enable you to perform Exchange Recovery on your own, as they have simple and self-descriptive graphical user interface.

Exchange Mailbox Recovery software repairs damaged EDB file and restores all user mailboxes as individual PST files. The Exchange Database Recovery software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, journals, appointments, and attachments.

Tags: , , , , , , , , ,
Posted in Exchange Recovery | No Comments »