Microsoft is a registered trademark of Microsoft
Corporation in the United States and other countries
About
The EDP Utility(Exchange Database Permutation Utility)
Clean Shutdown - Dirty Shutdown
Repair Utility
Some data recovery companies refer to the Dirty
Shutdown message as the error of Doom! In the past,
this may have required sending your company's data
offsite for data recovery efforts, but this is no
longer the case. Instead of spending thousands of
dollars for data recovery, you can download Dirty
Shutdown Repair Utility for $250.00 and fix the
problem yourself within minutes!
Hundreds of our clients have already experienced
the success and ease of using this program. It
not only has an interface that is easy to navigate,
but it works within minutes. The interface of
this program has recently been redesigned.
This program repairs all these error messages:
•JET_errBadDbSignature -531
•JET_errDatabaseStreamingFileMismatch -540
•JET_errDatabaseDirtyShutdown -550
•JET_errConsitentTimeMismatch -551
•JET_errInvalidDatabaseId -1010
•JET_errInvalidDatabase -1028
•JET_errDatabaseSignInUse -1222
•JET_errDatabaseCorruptedNoRepair -1224
•JET_errFileInvalidType -1812
EDP can bring any version of the Exchange mailstore
(5.5, 2000, 2003 & 2007) database back to a
clean shutdown state. If your database is not corrupted,
then there is no need to run eseutil. If you simply
move out your .log files and .chk file then you
can mount your database back up in about 2 minutes.
Most of the time, if your database does not properly
dismount, it is because the database has written
a dirty bit that marks it as being in a "dirty
shutdown state" even though the underlying
database is really intact.
There is a very good possibility that you will
be able to mount the database even if there is corruption.
This will allow you to exmerge the data out to pst
files, then create a blank store and merge the exported
data back into your mailstore. Once the database
is back in a clean shutdown state, if you feel that
there may be corruption, you can run Isinteg, which
is the database repair utility.
Many users will confuse eseutil as a database repair
utility, but in fact eseutil is really a "File
Level" repair utility. If you are going to
run any utilities on your database files, make sure
you have a file level copy of your database files.
Sometimes when performing a restore, the database
will end up in a dirty shutdown state. EDP/ Clean
Shutdown can bring the file back to a clean shutdown
state, or to a consistent state if you are running
exchange versions below 2000.
With this utility you actually remove the log
files, enabling Exchange to generate log files
based on your current database.
Stream File Mismatch Error, Time Stamp Error
& Log File Disk IO Error
Often while running eseutil , users will receive
a DISK IO error right away; this tool will resolve
that error.
OTHER FEATURES
OF EDP
EDP is the only exchange database repair utility
on the market. EDP allows for the manipulation
of the exchange database at the page level.
It is the only program that can fix the following
database problems without the need to repair or
play log files.
Fixes for databases, including ones that are
restored from back up but have not had the log
files played:
Fixes Error: "JET_errDatabaseDirtyShutdown"
Fixes Error: "JET_errTimeCorrupted,Dbtime
on current page is greater than the global database
dbtime"
Change
a dirty shutdown state to a clean shutdown
state in only a few seconds. If you have restored
from backup and the log files are not valid,
this can be a time saving option to get the
exchange store back mounted. Or if you believe
the store to be in good condition, you can
change the state so that you do not have to
run eseutil /p or /r.
Remove
or add the link to the stm file
(2000/2003). If you need to get the store mounted
and you know your stm file is bad, or are having
problems accessing the SLV space, sometimes you
can remove the link to the stm file, mount the
database and exmerge the data out you need.
Correct the system area.
If you have ever ran eseutil /mh and have received:
"This is not an exchange databse or non-db
file" this may be able to resolve that issue.
Also, if for some reason the checksum is not valid,
this function may be able to help.
Check a single page for
errors. You have the ability to input
any page number to check and correct high level
page errors. You can also manipulate the checksum
and dbtime dirtied(Exchange 2000,2003,2007).
File copy and repair.
This function allows you to copy off the database
while checking and fixing page alignment issues.
If you have ever recieved an EOF error before,
this function might be able to fix this problem.
In addition,with exchange versions 2003 SP1,SP2
and 2007 the copy process can fix high level page
errors as well( you will still need to perhaps
verify and change the checksum to the correct
value using the "Check Page" function).
