Error access to source database failed with jet error 1811

Microsoft Exchange Server works with different files to maintain consistency and health of the databases in the setup. An Exchange Server creates EDB file, which is the main database file that holds all the information. To prevent the file from being locked, corrupted, and to keep high performance of the data being accessed, the database uses a combination of transaction log files and stores information in memory. It uses both transaction logs and memory as a buffer to increase performance and prevent the database from getting corrupted. Once an application backup of the server is executed and a healthy backup is taken, the database purges the transaction logs since these were committed to the database during a backup.

The transaction logs cannot be purged manually as these hold temporary data before being committed to the database. If a transaction file is manually deleted, you may encounter data loss and even corruption in the database.

As mentioned, in a normal scenario, after taking backup with a backup software which is built for and supports the Exchange Server version you have installed, the transaction logs are automatically purged during the daily backups. If the transaction logs keep increasing and never purged, it means that there are issues with your Exchange Server, backup application, or there is something which is locking or preventing the Exchange to purge the files.

Why Do Exchange Server Databases Get Corrupt?

There could be many reasons that may lead to corruption in database. Some common ones are:

• Hardware failure (storage, motherboard, or others)
• Sudden loss of power which will not allow the database to safely shut down
• Malware, virus, or ransomware attack
• Issues during patching or update installation
• Consequences from no disk space on the data or log partition/drive

What Happens If a Database Gets Corrupt?

Usually when a database file (EDB) is corrupt, there could be items in the database which are damaged. If a transaction file is corrupt or missing, Exchange database will fail to mount. You can use the native tools – Eseutil for Repairing Exchange databases.

In this article, we are going to explore one of the many errors message that could occur during such situations.

When the database fails to mount and you use EseUtil to check the status of the database, you may get the following error:

Error: Access to source database ‘.edb’ failed with Jet error -1811.

Operation terminated with error -1811 (JET_errFileNotFound, File not found)

This error occurs when you run the command with the following parameter and you run out of disk space.

Eseutil /mh <database.edb>

Since Exchange database is not mounted, you will immediately know that the issue is critical since all the users will start complaining that they cannot send/receive their emails.

Ways to Fix the Error: Operation Terminated with Error -1811 (JET_errFileNotFound, File Not found)

Here are some ways to fix the issue at the earliest and restore the services:

• Perform a soft recovery using eseutil/r
• Perform a hard recovery using eseutil/p
• Restore from backup
• Use a third-party tool

Perform Soft Recovery

With EseUtil, you can perform a soft or hard recovery. The soft recovery would help you to fix small, corrupted items in the database. You should try it first to fix your database. You should never try to run a hard recovery first. This should always be used as the last resort.

To perform soft recovery, run the following command:

Eseutil /r /d “<path to your database file>”

An example would be:

Eseutil /r /d “M:ExchangeDatabasesDB01”

Depending on the size of the database, the process may take some time. Once done, run the EseUtil with the /mh parameter to check the status of the database. If it shows the status as Healthy Shutdown, you can mount Exchange database.

Perform Hard Recovery

If the soft recovery does not fix the error: Operation terminated with error -1811 (JET_errFileNotFound, File not found), you need to perform the hard recovery.

Caution: You should take a backup of the database before proceeding with hard recovery. You have to accept data loss as hard recovery will purge any data or information that is deemed corrupted. Also, after the hard recovery, your database will have a hard coded tag. If you request Microsoft to assist after you run it, you will not be supported as it breaches the SLA.

To perform the hard recovery, run the following command:

Eseutil /p “<path to your database file in full>”

An example would be:

Eseutil /p /d “M:ExchangeDatabasesDB01db01.edb”

After this, you can mount the database. However, it is not 100% sure that this would fix the problem.

Restore From Backup

You can also try to restore Exchange database from a previous healthy backup. However, you will end up losing all the data post the backup.

Use a Third-Party Tool

As an alternative, you can use Stellar Repair for Exchange. The application can open corrupted databases of any Exchange Server version. You can recover all the mailboxes and public folders and save them in PST and other formats. You can also export items and mailboxes granularly to a live Exchange Server database or an Office 365. Stellar Repair for Exchange will drastically reduce the recovery time of your services and reduce the data loss.

Resolve Exchange Jet Error 1811 With Different Scenarios

Jet Engine errors are quite hard to resolve and can easily harm your Exchange database file. Majority of time these errors get easily resolved, but when it comes to Exchange Jet error 1811 one must require profound information to fix it.

Microsoft Exchange is one of the most popular utilized emailing platform, however like other applications, Microsoft Exchange is also vulnerable to number of errors. Resolving them is a tedious task especially when it comes with real blunder issues like Exchange Jet errors .

Hence, in this article, we are going to understand one such blunder is Jet error 1811, what are the possible reasons behind it and how can it be settled in an effective way. But first let us understand when this Exchange Error 1811 comes.

Pro Tip: If in case, you are getting an error due to corruption issue found in Exchange database files like Priv.edb or Pub.edb, then you can try SysTools Exchange EDB Recovery Tool for repairing its database files. You can quickly recover & repair Exchange mailbox and fix your corrupted Exchange Server database files by using this software which supports to recover and repair EDB file Exchange 2016, 2013 & all its below versions.

After the successful recovery of the Exchange database file and mailboxes, you can export the recovered Exchange mailboxes into Live Exchange Server, O365 and different file formats in a simplified way.

How Exchange Jet Error 1811 Encounter?

The error is one of the most common error faced by the users. It comes when the administrators or the users execute eseutil.ese from cmd where machine is connected to the Exchange Server. Due to this error, users become inaccessible to their mailboxes, hence, not be able to perform other activities.
Error generated by Exchange is as follows:

“Access to the source database. ‘…mdbdatapriv2.edb’ failed with jet error 1811”

It could be the possibility that the error code contain different path in your system. There could be various reasons why this Exchange error 1811 occur, running Eseutil tool, user is in no mount state while trying to fix database corruption are some of the reasons why this error occurs.

Know the Cause Exchange Jet Error 1811

There could be number of reasons of getting this error. Some of them are as below:

• Unclean Shutdown of Exchange Server
• Inappropriate installation of an application
• Malware Intrusion
• Deleted Log file
• Power Outrage
• Missing Exchange Log file
• Mismatch between Exchange Log file signature Log generation number
• Mismatch Log file with its original signature

Fix Exchange Jet Error 1811 with Different Scenarios

Let us discuss various scenarios of getting this error in Exchange with its solution :

1. It could be the possibility that your Exchange log files get accidentally deleted or get misplaced, for that you need to use “Exchange Information Restore” so that you can recover the file from the production log files.

2. Another case could be if there is no missing file. For that case you need to check whether the files are stored under the Anti-Virus Program.

3. Sometimes Exchange Jet Error 1811 occurs while opening the log file. It generates an Event ID of 455 stating ‘currently log file is missing’. Reason being an issue in configuration between the Exchange Server and the currently running program. Or an Anti-Virus Quarantine option is enabled but the antivirus is not configuring accordingly.For that case, Perform the following steps:

• Stop all services of Exchange Server & Configure your Anti-virus program
• Now save your current log files to a temporary folder
• Delete all *log files located in MDBDATA
• Check the folder, only e00.chk, res1.log & res2.log files must be present there.
• If not, transfer all the extra files present there to a temporary folder.

4. Sometimes user get Error -1811 = 4294966274 = 0xfffff8ed = Jet_errFileNotFound. This occur when file is not found at the location. Reason being the missing database file or you have located your log files and Exchange database on network storage. You can resolve it by checking the file in which you are facing error, check its integrity and ensure it must have proper access permissions.

5. The Exchange error 1811 also occurs when you try to do an offline defrag of the mailbox using command eseutil. In this case, make sure you have entered correct folder path and enclose your folder path in double quotation marks.

Also Read: Fix Exchange Jet Error 1018

Conclusion:

For all those users who are looking for a solution to fix Exchange Jet Error 1811 are welcomed here. The blog discusses various possible scenarios of getting Exchange Error 1811 and the solution associated with it. If, somehow your exchange server database files got corrupted due to any of the reason, the blog covers an instant solution for repairing those files.

When administrators execute eseutil.ese utility from the command line where the machine is connected to the Exchange server, they

encounter Code error and Exchange Jet Error 1811 is one most common error faced by the user still, but due to error user not able to run other command and can’t access their mailboxes not able perform other activities. Since error display the description and a reason of its occurrence, and the id of malfunctioned system or program but it become not easy to naive user easily, For that, in below section, manually method are described properly fix the Jet Error 1811 for Exchange Server 2013, 2010, 2007 and 2003 versions.

The numeric part in name comprises of the data, which can be decrypted by the malfunctioned device or program manufacturer. It might be possible that the error statement with this code appears in the different path in the system, which means that it is going to be more complicated for pointing out the error and hence, the solution to troubleshoot it.

Conditions – Eseutil Exchange Jet Error 1811 Occur  Server

After searching on the Web get various Situation when user faced a Pop appears with message Error “Access to the source database. ‘…mdbdatapriv2.edb’ failed with jet error 1811” in Exchange 2003, 2007,2010, 2013 Server.

• When a user tries to Defrag the mailboxes of Exchange.
• Sometimes user gets error After Running the Extensible Storage Engine Utility (Eseutil) in Exchange 2007 Server.
• Even after Running eseutil /d on Store.
• While fixing Data Corruption in Exchange 2013, 2010 and 2007 version and user not able to mount the database

Read Also: Resolve Error JET_errRecordNotFound

Common Cause of Exchage Jet Error 1811  in Server

This error mostly arises due to the mismatch between the Exchange Log file signature and log generation number file. Sometimes due to various issues or malfunction in the system activities or programs leads to this error occurrence. Basic reasons behind this involve:

• Improper or interrupted Un-installation or installation of an application
• High consequences of the virus or Malware attacks
• The sudden shutdown of the machine due to Power failure
• Accidental Deletion of essential system files or registry

Generally, Log file in Server Known as E00.log file and if this file has not the common signature, then even the database of Exchange Server is consistent, still user not able to mount the database.

Solution to Fix Exchange 2010/ 2013 /2016 Eseutil Jet Error 1811

It is a hit and trial measure to get rid of this issue manually. Users can try all the methods one by one to resolve this Exchange server error 1811:

• A user to need to verify that whether any Anti-Virus program is able to read Exchange Service Files. If any Exchange log files are missing or deleted then try to recover that file from the production log file for that user need to use “Exchange Information Store”.
• If there is no file is missing then the database will otherwise user need to check whether the file stored in Folder of Anti-Virus Program File.

Solution When Log File is Deleted

• If Exchange log file is deleted then the user to first create a backup of the database and store them into a Backup folder. If any log file creates with name “EOO.log File”, you need to also Copy this file to the backup folder. If you see E00.chk file then Copy this file.
• Now rename the file E00*.log file to E00.log and restore the Dismounted again and replay the log files which helps Mailbox to move on the Consistent state. If still the Database not to move to Consistent state then try to run repair commands.

In Technical terms  Error code, 1811 denotes that IS is unable to locate the file. This can either be PRIV.EDB or PUB.EDB, which means that error is caused due to log file missing. To fix this, restore the previously backed up Exchange data and then, restart IS. If the problem does not get resolved then, move to the next measure.

•  Now Look for ‘EDB*.LOG’ files in the MDBDATA directory and search for a non-broken sequential string of all the file names, numbered in hexadecimal. For example EDB0001a.LOG to EDB0003f.LOG and EDB.LOG. Check that there are no spaces present in their numbering scheme. If all of the files are presented as well as accounted then, there are chances that damaged EDB.CHK is present. Move this file to some another directory and restart IS.
• If the log files are absent then, the recovery procedure is going to be a little bit different. For example ‘edb0003f.log’ file is missing; in this case, you have to erase all the files that are numbered lower thank the 3f. Along with this, you also have to remove ‘EDB.CHK’ file and replay the log file again

Note: If the missing file is edb00030.log then, the files to be removed are edb00031.log to edb00030f.log along with edb.log and edb.chk Rename the edb0002e to EDB.LOG. You have to delete all the files residing after the one, which is missing.

Use Best Alternative Solution

If an error arises due to some corruption issue in Exchange Priv.edb or Pub.edb then a user can Go for Exchange EDB Repair Tool provided by SysTools i.e. specially designed to resolve Exchange mailbox corruption and recover/repair the Exchange database file. It provides dual scanning mode i.e. Quick and Advance scan option which easily recovers & repair pub1.edb as well as priv1.edb file from corruption.

Download Now Purchase Now

After the successful recovery of Exchange database mailboxes, users can use this advanced tool to extract mailbox from offline EDB file and export directly to Live Exchange 2016, 2013, 2010, 2007 2003 mailboxes, Office 365, and multiple file format in a hassle-freeway. Users can easily convert EDB to PDF, PST, EML, MBOX, MSG, HTML file.

Key Features Of  Professional Software

1. Support EDB and STM file
2. Preview MS Exchange mailbox items before conversion
3. Preserve maintain folder hierarchy & keep metadata intact
4. Export EDB to PST, EML, HTML, MBOX, PDF, MSG file format
5. Option to decrypt email from Exchange mailboxes in batch
6. Compatible with all Microsoft Outlook, Exchange Server, and Windows OS version

Bringing It All Together

This write-up provide complete solution and explanation of Exchange Jet Error 1811 in Exchange Server 2013, 2010, 2007 and 2003 application helps the naive user to understand this issue and they can fix themselves using the techniques provided here. If you are new to Microsoft Exchange environment and finding difficult to resolve the issue, then users can use the advanced software described in the above section that easily remove corruption from EDB file and expport the mailboxes directly to Live Exchange Server. Hope it will be helpful for the administrator in troubleshooting the problem.

После запуска расширенного обработчика хранилищ (Eseutil.exe) из
командной строки на компьютере с Microsoft
Exchange Server 2007 выводится сообщение об ошибке Jet
1811, даже если операция завершается успешно.

Например, если выполнить команду eseutil .exe /K E00 из
командной строки, будет выведено следующее сообщение об ошибке:

Причина

Такое сообщение об ошибке предусмотрено в
Exchange 2007. Его можно игнорировать.

While using ESEUTIL, users can sometimes face unexpected errors which can lead to complete mailbox inaccessibility. Resolving such errors is an uphill task especially since the information that appears along with the error message can be very cryptic. Stellar Phoenix Mailbox Exchange Recovery software acts as a one-stop solution for dealing with Exchange ESEUTIL errors and can play an instrumental role in bringing the Exchange server back online in such scenarios.

ESEUTIL is an easily accessible command-line utility for performing various complex tasks for the Exchange server. This inbuilt tool proves to be extremely helpful when it comes to fixing corrupted Exchange databases, defragmenting them, reducing their size, or checking their integrity. But sadly, ESEUTIL sometimes faces errors which cause it to terminate without completing its action which can cause damage to Exchange files and leave users in a soup with no access to their mailboxes and failure in executing other commands.

In such cases where ESEUTIL command fails to perform, reliable and competent software applications like Stellar Phoenix Mailbox Exchange Recovery come to the rescue and help users in overcoming their Exchange troubles. This post demonstrates this fact by describing a scenario where ESEUTIL fails with Jet error 1811 and Stellar Mailbox Recovery fixes the same quickly.

Problem Scenario – Exchange Jet Error 1811

When working with the Exchange server, initiating defragmentation procedures is a common thing. The defragmentation option makes used storage contiguous, eliminates unused storage, and reduces the database’s size by compacting it. The command used for this purpose is eseutil /d.

Usually, the above mentioned command executes flawlessly and delivers what it promises. However, in rare situations, it fails with the error “Access to the source database. ‘…mdbdatapriv2.edb’ failed with jet error 1811”. This error is typical in Exchange versions 2003, 2007, 2010, and 2013. Evidently, decrypting this error message can be very difficult especially for a user with limited Exchange error handling experience. Still, there are a few things that can be done to attempt resolving Jet Error 1811.

Exchange Jet Error 1811 – Causes & Common Solutions

A quick look across Exchange forums reveals that the primary causes for Jet Error 1811 are:

• A mismatch between Exchange log file signature and log generation number file
• System malfunctions like interrupted installation or un-installation of an application
• Virus / Malware infection to Exchange system files
• Accidental Deletion of essential system files or registry information
• Sudden shutdown of the machine due to power failure leading to corruption in the database
• EDB file corruption owing to sundry reasons

Since the reasons behind this error can expand over such vast proportions, decoding exactly what caused it in your case can become tough. Hence, try out the hit-and-trial solutions listed below one by one to attempt resolving it.

• Disable your anti-virus program and try mounting the Exchange database. If it works, add an exception in your anti-virus application for Exchange service files.
• Take a backup of all Exchange log files and then move the original log files to a different folder. Thereafter, rename the file E00*.log to E00.log and perform a full restore of the Exchange database by replaying log files.
• Restore Exchange database from a previous backed up. Thereafter, restart the Information Service
• Look for ‘EDB*.LOG’ files in the MDBDATA directory and search for a non-broken sequential string of all the file names, numbered in hexadecimal, for example, EDB0001a.LOG to EDB0003f.LOG and EDB.LOG. If all of the files are accounted for, there might be chances that your EDB.CHK file is damaged. Locate this file and move it to some another directory. Then restart the Information Service.
• If a particular log file is missing, all the log files that are numbered lower than the missing one will have to be deleted along with edb.log and edb.chk. After this, repair commands (eseutil /p) will need to be executed on the Exchange server. If they execute fine, next step will have to be recovery procedure using command eseutil /r.

There might be a high chance that even after you try out all the above fixes, Jet Error 1811 still exists. Such a condition is indicative of severe corruption in Exchange database files which can be fixed with the best Exchange server remedy, Stellar Phoenix Mailbox Exchange Recovery.

What to do if manual techniques fail?

If manual tricks don’t work the magic, place your trust in an application that is more accurate and proficient. Stellar Phoenix Mailbox Exchange Recovery will help you overcome Jet error 1811 and a majority of other Exchange Jet engine errors smoothly. Ranked as one of the most recommended software by MVPs, this product repairs corrupt Exchange Database (EDB) files and restores mailbox content which can be directly exported to Live Exchange or Office 365. You can also save individual email messages recovered from EDB files in a variety of formats like PST, MSG, EML, HTML, RTF, and PDF.

Through a simple 3-step procedure – select EDB file, scan-and-preview, and repair-and-recover – this software allows you to overcome the drawbacks of manual Exchange repair techniques and stay ahead of nasty issues. Equipped with a convenient GUI, this product saves your time and effort while helping you ensure that Exchange server stays problem-free. Read more about the product here: Stellar Phoenix Mailbox Exchange Recovery.

Wrapping it up

We hope that at this point you’re much more aware of Jet Error 1811, its prime causes, and ways to fix it at your end. As a general rule, keep your Exchange EDB files backed up and server software updated. Also, maintain an uninterrupted power supply to the Exchange server and add an exception for Exchange services in your anti-virus application and firewall. Lastly, keep Stellar Phoenix Mailbox Exchange Recovery handy since it is the best alternative to manual Exchange repair techniques and helps you bring Exchange back online regardless of how grave an error seems to be.

Microsoft Exchange platform is one of the popularly used email platforms. This platform is also like other platforms is unsafe from several errors. The good thing is these errors can be resolved easily. But few errors need extra efforts like to Fix Exchange Jet Error 1811 & 1032. This type of error can damage your whole EDB file if it is not fix quickly at a time.

In this Blog Post, I have shared the causes and the solution that helps you to Fix Microsoft Exchange Jet Engine Error. So let’s get start

Why Exchange Jet Error 1811 & 1032 Occurs?

This Microsoft jet database engine error can arise due to harm in Exchange Server Database or application level. Here is the list of Jet Engine errors when the Exchange Server is corrupt, due to an unexpected crash in hardware or Software.

So here is the list of Jet Engine errors that can be arisen due to an unknown reason:

• The Jet VBA is not able to initialize. Re-Install the application once again
• JET_errRecord not available error
• 100 JET_err Rfsfailure
• Not capable to start DAO/Jet db engine
• Microsoft Jet database stops performing the process because you and the third user are changing the same data simultaneously.

Reasons behind the Eseutil Jet Error 1811

• Malfunctioning of hardware like hard drive, sudden power crash, damage to EDB mailbox
• When there is corruption in critical objects like the Exchange database due to registry and software errors
• When there is a mismatch between the JET or DAO file
• Missing or deleted Exchange log files leads to Eseutil jet error. 
• When there is a false Exchange database recovery because third-party resources are incompatible with Exchange

Solutions to Fix Exchange Jet Error 1811 & 1032

Follow these methods to fix this ESEUTIL jet error 1811 error given below:-

Manual Method 1- Backing Up of Exchange Database

• Start the Windows Server Backup and select the local backup solution
• Select the backup once the option
• Then just tap on different options and click the next button
• You will see a select Backup configuration page
• Choose the custom option and click on the next to move further
• You can also select items for the backup page
• Press add items option and press OK to attach the needed volume
• With Advanced Settings Exclusions, you can exclude the file types
• Visit the VSS settings tab and choose VSS full backup tab and press OK
• Then you will see a window giving an option to select local drives or remote shared folders to save Exchange backup files to the destination
• Check the setting of backup in the confirmation tab, and click on the backup button
• Check the current backup process and then press the backup button
• You can view the backup progress using the backup progress tab. Check the backup files after the completion of the process.

Related Post:- How to Repair Priv1.edb Exchange 2003 Error

Manual Method 2- Using Various ESEUTIL Command

MS Exchange server has several commands that resolve the different types of corruption errors. All you need to do is to open the command prompt and select desired ESEUTIL command depending upon the requirements. Read out the given commands:

• ESEUTIL/c- To perform the hard recovery of the Exchange database
• ESEUTIL/m- You can use this command to take the exit from header information of the database
• ESEUTIL/D- Command facilitate the offline defragmentation of the Exchange database
• ESEUTIL/y- Used to assign the operation on large mailboxes of the database
• ESEUTIL/g- To check the integrity of the exchange database
• ESEUTIL/p- Basically, used to recover corrupt exchange database file.  After this, the user needs to perform an offline defragmentation of the database
• ESEUTIL/R- For recovery operations on the exchange database
• ESEUTIL/K- To do the analysis of checksum values

You can use all these commands to Fix Exchange Jet Error 1811 & 1032. But these manual methods do not guarantee to keep data integrity. And you can also lose the information stored on the server.

Manual Method 3- Using Eseutil Repair Tool For Repairing Exchange Database

You can use the inbuilt tool of the Exchange server named Eseutil for fixing the damaged Exchange database. If you don’t know about the Eseutil repair tool here is a small overview of it.

What is eseutil used for?

ESEUTIL is the tool that is available for all Exchange server administrators. It can be used for various purposes like checking database status, repairing or defragmenting corrupt databases, and managing the database size.

In this tool, you’ll get 2 different soft recovery and hard recovery features for repairing the Exchange database. 

Solution No.1- Soft Recovery for ESEUTIL Jet Error 1811

Every user should prefer to use soft recovery first in comparison to hard recovery. There is no risk on the soft recovery and by this, you’ll be able to fix corruption-creating issues in the Exchange database.

Follow the below steps for performing Soft Recovery:-

•  Here you need to open the ESEUTIL tool and enter this command Eseutil /r /d “<path to your database file>”
• Here is the example:- Eseutil /r /d “M:ExchangeDatabasesDB01”

By entering all the above commands wait for few minutes to let the process complete. After the completion check the health status of the database by entering EseUtil with the /mh parameter command. And if the status is in a healthy state you can try to mount the database.

Solution No.2- Hard Recovery in ESEUTIL Repair Tool

If unfortunately, the soft recovery failed to resolve Exchange jet error 1811 then you can look for the hard recovery.

Caution:- Before performing the hard recovery I’d like to aware you that this process can lead to data loss or corruption. So make sure to take a backup of all Exchange databases before proceeding with the below steps.

Here are the steps of Hard Recovery with ESEUTIL:-

• Go to your ESEUTIL tool and put this command

  Eseutil /p “<path to your database file in full>”

And you might see the windows given in the below screenshot after putting the command.

Remember there is no 100% guarantee to fix the issue. You can go with the automated tool mentioned in Method no.3.

Automated Method 3- Using SysInspire EDB to PST Converter Software

The software has the latest technology to eliminate any error related to the Exchange Server file. This EDB to PST Free software has many features listed below:-

• Quick Conversion of EDB file into working PST Outlook format
• The auto-detection feature means it can automatically locate the.EDB file location
• Multiple Conversion formats of EDB File such as EMLX, EML, MSG, HTML, and PST
• There is no limitation of the database for making EDB to PST Conversion
• Splitting feature to shorten the size of large PST file into various small-sized PST files
• Also maintains the data integrity during the conversion

Conclusion

You can use any manual and automated method but the manual methods come with many limitations. And to operate the manual method you need professional knowledge. So it is better to take the help of SysInspire EDB to PST Converter software that scans the EDB file and immediately Fix Exchange Jet Error 1811 & 1032.

Hi,

I am getting the following error when I try to kick off an offline defrag usuing eseutil

***************************************************************************************************
C:Program FilesExchsrvrbin>eseutil /d «C:Program FilesExchsrvrExchsrvrM
DATApriv1.edb» /t e:temp.edb

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Error: Access to source database ‘C:Program FilesExchsrvrExchsrvrMDBDATAp
v1.edb’ failed with Jet error -1811.

Operation terminated with error -1811 (JET_errFileNotFound, File not found) af
r 0.32 seconds.
****************************************************************************************************

the steps I have completed so far are:
1. Dismounted the Info Store
2. Connected an external hard drive to the server with enough space to run the defrag
3. I ran the defrag a couple of nights ago but had to stop the defrag as it took too long so I re-scheduled it for the weekend
4. It created two temp.edb and temp.stm files on the external hard drive — I deleted theses files today before I kicked of the defrag
5. When I kicked off the defrag I get the above error.
6. I have tried stopped all the exchange services and re-running the defrag but no joy

Any ideas?

Would this occur due to the fact I deleted the two temp.edb files from my initial running of the defrag where deleted?