Posts Tagged ‘inconsistent state’
October 20th, 2009 | 
Author: In an EDB (Exchange Server Database) file, the transaction log is s history of activities, executed by the Exchange Server to guarantee the ACID properties over hardware failure or system crash. There are mainly helpful in aces of improper system shutdown to rollback the incomplete transaction and to recover the system from inconsistent state. But in some situations, the transaction log itself might get damaged and put your database in an inconsistent or damaged state. These situations cause critical data loss and require EDB Repair to be sorted out.
In order to check the integrity of log files, you can use Eseutil tool with /ml option. But in some cases, the Eseutil utility with /ml option fails in Microsoft Exchange Server 2003 and Microsoft Exchange Server 2000.
In order to test the transaction log file for corruption, you should the below command:
Eseutil /ml Log File Name
If the transaction log file passes the test, you will get below response:
Integrity check passed for log file: Log File Name
If the test fails, you get following message:
“CORRUPTION DETECTED in log file: Log File Name
Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is corrupt)”
The database inconsistency might take place due to torn writes, that require Repair Exchange database to resolve it. The torn write is actually an incomplete physical write operation, which is left in E00.log file after database service stops. The torn write results into checksums on affected transaction in log file to be incorrectly calculated and log is detected as corrupted by Eseutil. To resolve the Torn Write situations, when you apply Eseutil /ml, the following event might be logged into Application Event Log of Exchange Server:
Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: 12/9/1999
Time: 2:48:48 PM
User: N/A
Computer: Computer_Name
Description: Information Store (2428) Corruption was detected during soft recovery in log file E:\exchsrvr\THIRD\E00123ab.log. The failing checksum record is located at position 8189:328. Data not matching the log-file fill pattern first appeared in sector 8195.
In such cases, you need to repair and restore the damaged database to retrieve data from it. This is best possible with the help of powerful and advanced third party EDB Recovery software. These applications are capable of carrying out in-depth scan of damaged EBD file and retrieve all of its objects. The Repair EDB software are built-with interactive graphical user interface and thus do not demand sound technical skills.
Stellar Phoenix Mailbox Exchange Recovery is an efficient tool to ensure safe and absolute recovery in most of the EDB file corruption situations. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.
Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like EDB Repair and EDB Recovery. He is a professional writer and has written many blogs, article, press releasing and content for many websites.
Article Source: Transaction Log File Integrity Check Failure May Cause EDB Corruption
File Replication Service is a multiple-master replication, multithreaded engine included in Microsoft Windows Server versions. Abbreviated as FRS, this service is used by Windows 2000 server to replicate logon scripts and system policies for Windows 2000 based and other servers. When FRS performs any I/O operation on the disk, it maintains the data in cache in order to increase the performance. If operated on an NTFS volume, this cached FRS data might get lost under highly stressed conditions, which might leave the disk in inconsistent state. One of the solutions to resolve disk inconsistency is to reformat the disk. If you do so, you lose all the data that is stored on the disk. To recover this data, use your recent backup or if no valid backup is available, scan the disk using a powerful third-party Data Recovery utility.
To illustrate this, consider that FRS performs an I/O operation on a Windows 2000 based system. If the I/O is stressful and is being performed on a volume that is formatted to NTFS file system, you might come across the below error message:
“Event ID 41.
The file system structure on the disk is corrupt and unusable. Please run the Chkdsk utility on the volume “Name.”
Further, when you run Chkdsk to check the consistency of the disk, you receive one of the below error messages:
“Deleting corrupt attribute record (16, “”) from file record segment xxx.”
Or
“Correcting error in index $30 for file 100”
Windows 2000 system error log records this entry for dirty volume with event ID 55.
Cause
A Windows 2000 based system exhibits the above discussed behavior if some of the cached has not been successfully written to the disk. This particularly occurs under stressful I/O operations. This leaves the disk in corrupt state.
Solution
You are suggested to install the latest updates available for your operating system. However, to solve disk inconsistency, you need to reformat the disk and use your backup to restore data thus lost.
At times, backup fails to give the desired results. In such cases, you are recommended to use hard drive recovery software to extract the lost data. Data Recovery applications are highly influential and powerful utilities designed to perform safe data recovery using suitable scanning algorithms. These applications serve as valid Partition Recovery tools as well.
Stellar Phoenix Windows Data Recovery is a comprehensive Data Recovery Software designed for Windows 7 RC1, Vista, XP, 2003 and 2000. This application is competent to recover data in all cases and provides advanced options. It is a safe utility that is compatible with FAT32, VFAT, NTFS and NTFS5 drives.
K madhav is a data recovery expert and doing research on data recovery software and hard drive recovery
Article Source: Loss of Cached FRS Data Corrupts Disk
Exchange dirty shut down is the most common issue that Exchange Server administrators ordinarily need to deal with. The dirty shut down refers to abrupt Exchange Server shut down or appearing of Exchange Server in inconsistent state. The reason for dirty shut down can be abrupt system shut down or any hardware failure on the system where MS Exchange Server has been installed. When MS Exchange Server goes in inconsistent state, you encounter the following error message:
“error -550 (Jet_errDatabaseDirtyShutDown)”
The preceding error does not indicate that Exchange Server database is damaged or corrupted but the database files were not properly detached from the log stream. However, dirty shut down sometimes also leads into database corruption. When you encounter with the error message confirming dirty system shut down, you must recover the database before you restart the Exchange Server.
Process to Recover Exchange Database
You can recover the database files in following two ways:
Recover from Backup File: If you have already taken full backup of Exchange Server database then restore the storage group and log files from backup file at a new location. After restoring the storage group, mount the database in storage group.
Repair the Database: If you do not have backup of Exchange Server database then the only solution for you to recover database is to repair it. You can repair the database if execute the following steps:
Execute the Eseutil /p command from Exchange Server’s Bin folder
Delete the log and chk files
Defragment and rebuilt the database using the Eseutil /d command
Execute Isinteg –s exchange_server_name –fix –test alltests
Mount the database
After applying anyone of the aforementioned methods if you are not able to recover Exchange Server database then the best possible way for you to repair the MS Exchange Server database after encountering “error -550 (Jet_errDatabaseDirtyShutDown)” message is the use of third-party Exchange recovery utility. With easy to use interface, these utilities help you repair Exchange database within minutes. With their advance Exchange database recovery processes these utilities recover all database files from Exchange storage group.
Lots of Exchange Server database repairing and recovery tools are available in the market. And most of them offer free trial so that you can verify the software quality before making a purchase. On the basis of the result of the evaluation version you can easily decide that which Exchange database recovery tool will be best for you.
Author of the article is an. expertise in data recovery software, email recovery, email migration, hard drive recovery, password recovery fields.
Article Source: EDB Corruption and Recover Exchange Server Database
Input/Output Requests Packets (IRPs) are kernel mode structures that are used by Windows Driver Model (WDM) to interact with each other and with operating system. These data structures are usually created by I/O manager in response to I/O requests from user mode. An inconsistent state of IRP is primarily caused due to operating system malfunctioning, virus infection and more. In most cases of inconsistent IRP state, you encounter a STOP error message. Two major consequences of a STOP error message are unbootable hard drive and data inaccessibility. In such situations, an ideal solution is to restore your data from an updated backup. However, if no backup is available or backup is unable to restore the required information, you need to opt for advance data recovery software to recover your data.
As a practical instance, you encounter the below STOP error message due to inconsistent IRP state:
“STOP: 0×0000002A (parameter, parameter, parameter, parameter) INCONSISTENT_IRP”
Parameter 1: The address of the IRP that was found to be inconsistent
Parameter 2: Reserved
Parameter 3: Reserved
Parameter 4: Reserved
Data saved on the hard drive becomes inaccessible after you encounter the above error message. Additionally, you receive the same error message each time you attempt to boot your system.
Cause:
The root cause for the above error message is inconsistent IRP state. For example, an IRP has been completed, but is still as being queued to a driver’s device queue.
Resolution:
To resolve the above error message and access the data, you will need to follow these measures:
* Remove the new hardware and reboot your system.
* Verify that the compatibility of the hardware and drivers by using Microsoft Hardware Compatibility List (HCL).
* While booting your system, select Last Known Good Configuration option
If all the measures fail to resolve the issue, try using Emergency Repair Disk. In case, you do not have an Emergency Repair Disk or the disk falls short to resolve the problem, then you will need to perform a clean reinstall of Windows. A fresh reinstall of Windows will erase all the data from the selected hard drive partition. To recover your data under such scenarios, you will need to opt for advanced data recovery software. These data recovery tools use powerful scanning algorithms to recover lost data from a formatted hard drive.
Stellar phoenix windows data recovery is a powerful and reliable data recovery application. The utility recovers lost data from corrupted, deleted, formatted or lost hard drive partitions and volumes. The utility supports 185 different file types that can be further extended. It is compatible with FAT32, VFAT, NTFS and NTFS5 file systems. The utility supports Windows 7 (Currently in RC1), Vista, XP, 2003 and 2000.
K madhav is a data recovery expert and doing research on data recovery and hard drive recovery.
Article Source: Error Message in Windows -Resolving “INCONSISTENT_IRP”
Sometimes, when you put a relational database, created using Microsoft Access, on a shared network drive, it does not work. It opens fine 2 or 3 times but when you open it again and again, you receive the following error message:
“Microsoft Office has detected that this database is in inconsistent state and this database will attempt to recover the database. During this process a backup copy of the database will be made and all recovered objects will be placed in a new database. Access will then open the new database. The names of the objects that were not successfully recovered will be logged in the “Recovery Errors” table.”
When you click OK for recovery, in some cases it recovers the Access database but most of the times it shows you another error message stating:
“The database can’t be repaired or is not a Microsoft office access database file.”
After these error messages, you can not access even a single bit of your valuable data from your MDB file.
Grounds of the trouble
This problem occurs only with the shared database. When you create a backup copy of your Access database on network drive, you generally come across with this situation. The problem takes place due to corruption in the database, which is the result of improper closing of the database.
When you close the Access database from your client system, the server still thinks that the database is running and after some time it damages the database.
Work around of this issue
If you want to prevent this problem from occurring in future, you should always properly close the database on client as well as server computer. To work around the corruption scenario, you need to perform Access recovery.
Access recovery is the application through third party access repair software. These software are specially designed tools to meet different Access recovery related user requirements. Access recovery software systematically scan the damaged Access database, repair it and ultimately restore it in original state.
Stellar Phoenix Access Recovery is a highly developed and the most influential Access repair software which easily handles all of the MDB corruption cases. Phoenix Access recovery is applicable to all of the MS Access database objects including reports, forms, macros, database relationships, constraints and so forth.
It is read only and non destructive Access repair software, which allows you to have safe and original Access recovery. You can use this robust and comprehensive Access repair software with all file versions of Microsoft Access including Access 2000, 2002, 2003 and 2007.
Mahi Sony work as a freelancer and researcher of data recovery & partition recovery Software.
Article Source: Access Database Gets Corrupted Due To Inconsistency Problems
Exchange Server database corruption is not an unusual incident for the database administrators. Those who haven’t experienced it yet may strongly face it in the future. Virus attack, network malfunctions or unexpected system shutdowns are the reasons that corrupt your database and make it unusable.
Now, eseutil/p and eseutil/g are the utilities which can respectively repair and check the integrity of Exchange database (EDB). But sometimes, running these commands may not prove to be productive as some error messages like following may pop up, while trying to run the specified utilities:
“-1206, JET_errDatabaseCorrupted”
The command crashes out and database goes to the inconsistent state. Some of the users also report that the similar error message is encountered, when the upgrading of Exchange Server is tried. In such situations, the upgrade process may fail again with an additional error message, showing unexpected conditions in the database.
When you get error 1206 in Exchange Server, this is not always mandatory that the database is corrupted, as has been stated in the mentioned error message. So, see the recommended points:
.Try to mount the database and check that whether it is possible. If yes, make a backup of all the mailboxes to a new mailbox store.
.File level scanning and antivirus scanning should not include EDB and log files. So make sure that these files are not being scanned.
See into the System and Application logs. Here, you will get some hints of the actual problem. If it says corruption in Exchange database, go for EDB repair.
In case, the mentioned error message has resulted after an upgrade failure, this is quite possible that the database has upgraded, may be partially, but the upgraded Exchange Server files have not been copied to a folder known as the Exchsrvr folder.
If you find EDB inaccessible and also System and Application logs signifies the corruption, use EDB recovery solutions to solve the problem. The EDB repair software is available in the market, which can actually scan the corrupted database and correct it for use. It comes with advanced recovery ability and the read-only mode keeps the critical data safe and intact.
Stellar Phoenix Mailbox Exchange Recovery is the ultimate utility to fix such issues. This EDB repair application uses the most powerful scanning algorithms and repairs the corruption. It supports Microsoft Exchange Server 5.5, 2000 and 2003. The application performs EDB recovery for all the database objects.
Mahi Sony work as a freelancer and researcher of data recovery & partition recovery Software.
Article Source: Error 1206 in Exchange Server
RAID servers are considered as the most trusted and reliable storage medium. But sometimes, they may also lose all the hard drives, which include your important data, backups and other information.
Most of the organizations use RAID for storing their important SQL Server databases. When they fail, generally you may lose all of your data, but sometimes you may get some traces of data and can recreate the database.
In such situations, you can save your database by restoring the database from your backup. But unfortunately, when you try to restore backups, which were made through MS SQL Server for a database, which is running on DTP SmartRAID V controllers, you may receive the following error message:
“Msg 3270, Level 0, Sev 16.
An internal consistency error occurred. Contact Technical Support for assistance.”
In this case, when you attempt to detach the database using sp_detach_db stored procedure and then attempt to attach the database again with the help of sp_attach_db stored procedure, you may get the flowing error message:
“Server: Msg 5172, Level 16, State 15, Line 1.
The header for file ‘d:\pubs.mdf’ is not a valid database file header. The PageAudit property is incorrect.”
After this error message, the restoration process gets halted and you can not access anything from your SQL Server database.
Grounds of the trouble
As stated in the above error messages, this problem is either due to inconsistent state of the database or due to invalid header entry for the database. In both of these cases, the database may get damaged and thus even a single bit of data can not be retrieved from it.
In such disastrous situations, you need to perform SQL recovery to repair the damaged database and retrieve all of your data from it. SQL recovery can be carried out using the MDF recovery software.
MDF recovery software are easy to use tools, which allow you to have quick and trouble-free MDF repair in each and every case of MDF corruption. To ensure complete and successful SQL repair, always use effective SQL recovery software like Stellar Phoenix SQL Database Recovery software.
Phoenix MDF recovery software works well in all MDF corruption posers. This MDF repair software can effectively repair and restore all of the SQL Server database objects including tables, reports, forms, triggers, stored procedures, defaults, user defined data types and likewise.
With read only and non destructive conduct, this SQL repair software is safe to use. Phoenix SQL recovery applies on MS SQL Server 2000 and 2005. To get in-depth knowledge about the workings, user interface, and powerfulness of this robust MDF recovery software, download and use free demo version. Demo version is available on Stellar’s website.
Simpson is a freelancer for Stellar which offers data recovery software and file recovery programs for different OS and file system including data recovery mac, data recovery linux, SQL recovery , pst recovery and many other programs.
Article Source: Database Inconsistency and Invalid File Header Problems in MDF