from directory [path] ended with an error (Error returned from an ESE function call
The restore at the temporary location of the directory named in the message has failed. The error message included in the message text will vary, depending on the problem
encountered. Look for corresponding error messages reported in the event log.
The most common errors are listed below.
Error -610 = 0xfffffd9e= JET_errExistingLogFileHasBadSignature = Existing log file has bad signature.
This error applies to Exchange 2000 and later. You cannot mount the database
after an online restore. This behavior can occur because in order to
restore an online backup of an Exchange 2000 computer, you must have the
Microsoft Information Store running. At startup, the Information Store
attempts to mount the database. If no files are found, the Information Store
cannot mount the database; however the Information Store does create some logs
anyway. The logs signature does not match the ones from the backup and the
Information Store fails to replay logs and mount the databases.
- Error -552 = 0xfffffdd8 =
JET_errDatabasePatchFileMismatch = Patch file is not generated from this
backup. This error applies to Exchange 2000 with no service pack and Exchange
2000 SP1. After a restore of online backup for Exchange 2000 storage group,
stores do not
mount even if option to mount them automatically was checked. There are
two stores being restored in this storage group that have the same file names;
for example, two mailbox stores have file names “priv1.edb” and “priv1.stm”.
Of course, those stores have to be in different folders (two files with the
same name can not be in one folder) but when being restored, it appears that
the patch file gets confused and it tries to patch the wrong store, as both
stores have the same file name. Database names can not be the same as
long as they are in the same storage group. They can be the same in different
storage groups, but not in
the same one.
- Error -514 = 0xfffffdfe = JET_errBadLogVersion = Version
of log file is not compatible with Jet version. This error applies to
Exchange 2000 SP2 and greater. Restoring an Exchange 2000 with no service pack
or Exchange 2000 Service Pack 1 (SP1) database to an Exchange 2000 SP2 server
results in the databases not mounting after the restore. The reasons is
that beginning with Exchange 2000 SP2, Jet does not support restoring an
Exchange 2000 with no service pack or Exchange 2000 SP1 database using a Jet
engine (ESE.dll) version of Exchange 2000 SP2 or greater because SP2 had a log
format change to support elimination of the patch file.