Certificate Authority service fails to start due to corrupt log fi
- From: Chris Martin <ChrisMartin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Apr 2008 19:00:00 -0700
We have a two layer CA system, a root CA and a group of subordinate CAs the
answer for various types of certificates.
The root CA service currently fails to start saying there is a corrupt log
file. I have run esentutl on the database (minor inconsistencies fixed) and
the log file (doesn't recover the log file, saying that it's corrupt:
"C:\WINDOWS\system32\CertLog>esentutl /r edb
Microsoft(R) Windows(R) Database Utilities
Version 5.2
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: edb
Log files: <current directory>
System files: <current directory>
Performing soft recovery...
Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is
corrupt
) after 0.219 seconds."
This server hasn't issued a new cert in months, is there a way to delete or
clean the log file? If I just move or rename the log file the CA service
can't start because it's missing. Is there a way to get around this?
Regards,
Chris Martin
SysAdmin
Medfin
.
- Follow-Ups:
- Prev by Date: icacls or subinacl
- Next by Date: Re: icacls or subinacl
- Previous by thread: icacls or subinacl
- Next by thread: Re: Certificate Authority service fails to start due to corrupt log fi
- Index(es):
Relevant Pages
|
|