Article ID: 248406 - View products that this article applies to.
This article was previously published under Q248406
This article has been archived. It is offered "as is" and will no longer be updated.
The Esefile utility is a new utility that is included with Microsoft Exchange Server version 5.5 Service Pack 3 (SP3) and Microsoft Exchange 2000 Server. It is in the Support folder on the Exchange 5.5 SP3 CD and in the Support\Utils\I386 folder on the Exchange 2000 CD. There are separate versions for the Intel and Alpha platforms. You can use this utility on Microsoft Exchange Server 5.0 databases, on Exchange 5.5 databases, and on Exchange 2000 databases.
The command line for the Esefile utility is:
esefile [/c source destination] [/x file] [/s file] [/d file page number]
/c copies source to destination
/s Ese.dll format checksum
/x Edb.dll format checksum
/d dumps a page from a file
Note The Esefile utility is system insensitive.
There are two main uses for this utility: to copy files, and to test the checksums on an Exchange database.
Copy filesTo copy files by using the Esefile utility, type the following command:
esefile /c <source> <destination>Notes
The esefile /c command can copy a file of any size. (The utilities in Microsoft Windows Server NT such as Copy/Xcopy make changes to the files by caching the page pointer. The size of files that these utilities can copy depends on the available amount of contiguous non-paged pool memory in the system.)
Test the checksums on an Exchange databaseThis command verifies the page-level integrity of the database. It runs at a speed of approximately 1 gigabyte (GB) per minute. To test the checksums on an Exchange database, type one of the following commands, depending on your situation:
ChecksummingThe following example shows a database that has an incorrect checksum:
0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... 117250 pages seen 0 bad checksums 457 uninitialized pages 0 wrong page numbers esefile completes successfully after 28 seconds
ChecksummingIn this example, page -1 and page 0 did not pass the checksum, and when you try to start the information store, it does not start and logs the following error message in the application event log:
0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... ERROR: page -1 checksum failed ( 0x39215350 / 0x291fed56 ) ERROR: page 0 checksum failed ( 0xd7698bbc / 0x6a5d128b ) 117250 pages seen 2 bad checksums 457 uninitialized pages 0 wrong page numbers esefile fails after 28 seconds
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Event ID 5000 Source MSExchangeIS
Unable to initialize the Microsoft Exchange Information Store service.
Error Non-database file or corrupted database.
(https://support.microsoft.com/kb/151789/ )Error -1018 (JET_errReadVerifyFailure)