Event ID's 1202/1085 and ESENTUTL

  • Thread starter Thread starter imscoop22
  • Start date Start date
Thanks Wes, it did lead me to one article that I hadn't seen. I'll
look into it.

In the meantime, using ESENTUTL /P seems like an easy fix. Do you know
of any issues with using it?
 
I have never used ESENTUTL. Except for ESENTUTL /? once.

What files are you using ESENTUTL /p with?

REPAIR:
DESCRIPTION: Repairs a corrupted or damaged database.
SYNTAX: ESENTUTL /p <database name> [options]
PARAMETERS: <database name> - filename of database to repair
OPTIONS: zero or more of the following switches, separated by a
space:
/s<file> - set streaming file name (default: NONE)
/t<db> - set temp. database name
(default: TEMPREPAIR*.EDB)
/f<name> - set prefix to use for name of report files
(default: <database>.integ.raw)
/8 - set 8k database page size (default:
auto-detect)
/o - suppress logo
NOTES: 1) Repair does not run database recovery. If a database
is in an inconsistent state it is strongly recommended
that recovery is run to ensure the database is
consistent before proceeding with repair.

Securing Data Troubleshooting
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_scetroubletn.mspx

Securing Data Troubleshooting
http://technet2.microsoft.com/WindowsServer/en/Library/ea0c43e8-b08a-4893-b060-7b80c533d1961033.mspx

Troubleshooting SCECLI 1202 Events
http://support.microsoft.com/kb/324383

Event ID 1000 and 1202 After Configuring Policies
http://support.microsoft.com/kb/260715

ESENT event IDs 1000, 1202, 412, and 454 are logged repeatedly in the
Application log
http://support.microsoft.com/kb/278316/

Event ID 1091 and Event ID 1085 Appear in the Application Event Log
http://support.microsoft.com/kb/823608

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Back
Top