This article has been archived. It is offered "as is" and will no longer be updated.
When you restart your server after you install Microsoft Windows 2000 Service Pack 4 (SP4), the Microsoft Exchange Server Key Management Service (KMS) service does not start.
Additionally, the following event is logged in the Application log of the Windows Event Viewer:
Event Type: Error Event Source: MSExchangeKMS Event Category: None Event ID: 5085 Date: Date Time: Time User: N/A Computer: ComputerName Description: KMS can not mount the key database. Either the database is missing or it is corrupted. The service started, but Admin/User can not do any operation except restoring the database from a backup set. After restoring, please stop and restart the service.
Note In this event message, "can not" is a misspelling for the word "cannot."
This problem occurs if you install Windows 2000 SP4 on a computer that is running Microsoft Windows 2000 Service Pack 3 (SP3) and that is also running Microsoft Exchange 2000 Server Service Pack 3 (SP3).
To work around this problem, run the eseutil.exe /d command against the KMS database to defragment it. To do this, follow these steps:
Note By default, Eseutil.exe is stored in the Program Files\Exchsrvr\Bin folder. However, you can also locate this utility on the Exchange 2000 Server CD in the Support\I386 folder.
Perform a complete backup of your Exchange 2000 databases.
Start a command prompt, and then change to the Program Files\Exchsrvr\Bin folder on the hard disk where Exchange 2000 is installed.
Run the following command, where c:\program files\exchsrvr\kmsdata\kmsmdb.edb is the path of your KMS database:
Note While the /d switch is used with the eseutil command to defragment a database, the actual work that the Eseutil utility does is to create a new database to store the defragmented information in, and then to replace the existing database with this new copy. This is helpful when the existing database structure might be corrupted.
When the database is successfully defragmented, restart the Microsoft Exchange Key Management Service.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
317014 XADM: Exchange 2000 Server Eseutil Command Line Switches
192185 XADM: How to Defragment with the Eseutil Utility (Eseutil.exe)
km certificate corrupt corrupted mount failed fail crash