Search
Report Types:
Products
Updates
Logs
Bugs
Files
Encounters:
Only Reports that have Encounters
Encounters must contain resolution
Home
Products
Updates
Logs
Bugs
Files
Sign In
Create an Account
Action Links
Create a Product Report
Create a Update/Patch Report
Create a Log/Event Report
Create a Bug Report
Create a File Report
Recent Search Results
No Search results are currently available to display.
Your last search results will be displayed here for the duration of your browser session.
Latest Reports
LINUX Slackware 13
HP Designjet 9000sf
Dell Adamo XPS
HP Photosmart 335
HP LaserJet 4250tn
HP Designjet Z3100
HP PA-RISC rp8420
HP Designjet 30
Dell Optiplex GX280
TAKE 2 INTERACTIVE GRAND THEFT AUTO: VICE CITY STORIES PLAYSTATION PORTABLE
...
136
137
138
139
140
...
Log Report
Print
Edit This Record
Create New
Revision
1
Template
Windows Event Log
Log Name
System
Type
Error
Source
Service Control Manager Eventlog Provider
Event ID
7024
Average Threat Rating
Average Threat Rating Help
X
Loading...
Encounters
More Info
Related Content
Alert Me
Discuss
Add Your Encounter
Hide Encounters without Resolutions
joverland
Posts: 41
4/26/2011
Revision
3
Threat Rating:
Contains Resolution:
The Active Directory Certificate Service could not verify the CRL and would not start. We were ablet to get the service started by following Method 2 of this KB:
http://support.microsoft.com/kb/825061
Method 2: Modify the LogLevel Registry Value
If this CA is an offline CA and has no access to the network to obtain the CRL, set the LogLevel registry value to 2. This registry change permits the CA to start by ignoring the revocation offline error. To set the LogLevel registry value, follow these steps:
Click Start, click Run, type cmd in the Open box, and then click OK.
Type the following command, and then press ENTER:
certutil.exe -setreg CA\LogLevel 2
The following results are returned:
<myCA>\LogLevel:
Old Value:
LogLevel REG_DWORD = 3 (3)
New Value:
LogLevel REG_ DWORD = 2 (2)
Restart the Certificate Services service. To do so, type the following commands (press ENTER after each command):
net stop certsvc
net start certsvc
After starting the service we could see that the Root CA CRLs had expired. We have them on a 180 day interval and had not updated them.
Peer Reviews (0)
Peer Review Help
X
Loading...
No reviews have been post for this Encounter
Post a Peer Review:
Copyright (c) 2011
About Us
Contact Us
Privacy
Disclaimer
FAQs