Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 482 Source: NTDS ISAM
|Source: NTDS ISAM|
<process> (<PID>) An attempt to write to the file "<file>" at offset <value> (<hex value>) for <value> (<hex value>) bytes failed with system error <error code> (<hex error code>): "<error message>". The write operation will fail with error <error code> (<hex error code>). If this error persists then the file may be damaged and may need to be restored from a previous backup.
|English: Request a translation of the event description in plain English.|
Aaron C. de Bruyn
If you do as Microsoft says and split your AD database/logs on different drives during dcpromo you may run into this some day. If you run chkdsk /f on your system partition, it will tell you that you need to reboot to perform the check. If you run it on your non-system partition (but a partition with your AD data) chkdsk will helpfully unmount the drive causing AD to become corrupted.
Rebooting may solve your problem. Otherwise, you may have to restore from a backup.
|Private comment: Subscribers only. See example of private comment|
|Links: EventID 482 from source ESE98|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated