Microsoft KB Archive/244525

= How to run Eseutil on a computer without Exchange Server =

Article ID: 244525

Article Last Modified on 10/31/2007

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2007 Standard Edition
 * Microsoft Exchange Server 2007 Enterprise Edition

-



This article was previously published under Q244525



SUMMARY
You might need to run Eseutil against a database on a computer that does not have Microsoft Exchange Server installed on it. This situation normally occurs when there is not enough free space on the Exchange Server computer to complete tasks such as an offline defragmentation of an Exchange Server database file. In these limited scenarios, the required Exchange binaries can be copied over to a non-Exchange Server computer temporarily. Or, the required Exchange binaries can be run from a network share. For a permanent solution, you must install Exchange in Administrator-only mode. When you install Exchange in Administrator-only mode, the appropriate binaries are copied to the destination computer.

For more information about space requirements when you use the Eseutil utility to defragment your database, click the following article numbers to view the articles in the Microsoft Knowledge Base:

183888 Free disk space requirements for Eseutil.exe

192185 How to defragment with the Eseutil utility (Eseutil.exe)

255035 How to recover hard disk space from Exchange Server databases



MORE INFORMATION
Important For the following procedure, Microsoft strongly recommends that you use the same versions of Extensible Storage Engine (ESE) files that are on the Exchange Server computer.

Exchange Server 5.5

 * 1) Create a new folder on the computer that does not have Exchange Server installed on that particular computer.
 * 2) Copy the Eseutil.exe utility, Ese.dll file and Exchmem.dll files from the Exchange Server computers  :\Winnt\System32 folder (where   is the drive that houses Microsoft Windows NT server files) to the new folder that you created.
 * 3) Open a command prompt and change directory to the new folder that contains the copied files
 * 4) Run eseutil from this folder against any databases copied over from the Exchange Server computer.

These files should be copied to a computer running Windows NT 4.0 Service Pack 3 or later. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

190996 Operation terminated with error -1911 using ESEUTIL /d

If the Exchange Server computer and the computer without Exchange Server are not running the same Windows NT version and service pack, you may see events in the application log that indicate that the database indexes are being re-created upon restarting the database service. This is normal and does not indicate an issue. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

215297 WinNT version change may cause Exchange DB indexes to be rebuilt

Exchange 2000 Server

 * 1) Create a new folder on the computer that does not have Exchange 2000 installed on that computer.
 * 2) Copy the Eseutil.exe, Ese.dll, Jcb.dll, Exosal.dll, and Exchmem.dll files from the Exchange 2000 server's  :\Exchsrvr\Bin folder to the new folder that you created.
 * 3) Open a command prompt, and change directory to the new folder that contains the Eseutil.exe and Ese.dll files.
 * 4) Run eseutil from this folder against any databases copied over from the Exchange 2000 computer.

Note If the language locale setting in Exchange Server does not match the language locale setting of the computer without Exchange server where you run Eseutil, you receive the following error message when you run Eseutil:

Error -1062 (JET_errInvalidLanguageId, Invalid or unknown language ID)

Exchange Server 2003

 * 1) Create a new folder on the computer that does not have Exchange Server 2003 installed.
 * 2) Copy the Eseutil.exe, Ese.dll, Jcb.dll, Exosal.dll, and Exchmem.dll files from the Exchange Server 2003 computer's  :\Exchsrvr\Bin folder to the new folder that you created.
 * 3) At a command prompt, change directory to the new folder.
 * 4) Run the eseutil command from this folder against any databases that were copied from the Exchange Server 2003 computer.

Note If the language locale setting in Exchange Server does not match the language locale setting of the computer without Exchange server where you run Eseutil, you receive the following error message when you run Eseutil:

Error -1062 (JET_errInvalidLanguageId, Invalid or unknown language ID)

Exchange Server 2007

 * 1) Create a new folder on the computer that does not have Exchange Server 2003 installed.
 * 2) Copy the Eseutil.exe, Ese.dll, Exosal.dll, and Exchmem.dll files from the Exchange Server 2007 computer's Drive:\Program Files\Microsoft\Exchange Server\Bin folder to the new folder that you created.
 * 3) At a command prompt, change the directory to the new folder.
 * 4) Run the eseutil command from this folder against any databases that were copied from the Exchange Server 2007 computer.

Additional query words: x2kinfoht machine integrity check different XADM

Keywords: kbhowto KB244525

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.