Windows 2003 Server wont boot anymore - c000021a
Posted: Tue Feb 28, 2006 12:56 pm
[Problem]
After installing a security patch, the following error popped up:
[Solution]
NONE YET - at least not a real one. Read the Comments.
[Comments]
Okay. Now, this is crap. Hell. What we tried so far:
* Repair function of windows => does not work.
* replacing possibly broken dll's with dll's known to work (and of the right version => does not work
* Repair tools offered from Microsoft to fix this error (replaces this and that .exe + some dll's) => does not work
* Retrieve a complete list of dll's and exe's that could be involved in this error (to exactly replace whats broken) => failed
* Searching for hours in Microsoft knowledgebase articles and a thousand other websites => always the same triggers for this error, but not in our case. Failed.
Finally, there was no real option left (and no time left to play around more with this crap error) except for reinstalling. I installed the OS in the same directory (used old partitioning and left the C: drive in-tact, hence no format), and it worked again.
However, i do not consider _that_ a real solution - even tho iam known to even be happy with half-baked work-arounds as a final solution
After installing a security patch, the following error popped up:
The System won't boot anymore, in no boot mode (secured, last known working, ...).Stop c000021a {Fatal System Error}
The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.
[Solution]
NONE YET - at least not a real one. Read the Comments.
[Comments]
Okay. Now, this is crap. Hell. What we tried so far:
* Repair function of windows => does not work.
* replacing possibly broken dll's with dll's known to work (and of the right version => does not work
* Repair tools offered from Microsoft to fix this error (replaces this and that .exe + some dll's) => does not work
* Retrieve a complete list of dll's and exe's that could be involved in this error (to exactly replace whats broken) => failed
* Searching for hours in Microsoft knowledgebase articles and a thousand other websites => always the same triggers for this error, but not in our case. Failed.
Finally, there was no real option left (and no time left to play around more with this crap error) except for reinstalling. I installed the OS in the same directory (used old partitioning and left the C: drive in-tact, hence no format), and it worked again.
However, i do not consider _that_ a real solution - even tho iam known to even be happy with half-baked work-arounds as a final solution