Have you ever been in the unpleasant situation in which 'necessary Windows updates (such as an entire package of Service Pack) and your operating system, refuses to apply the new patches released?
Well, the mishap and I 'just happened today, when, seized by an attack of acute Stakhanovism, I decided to start a good week in anticipation of a good half-hour into the company and tried to access one of the Our server via remote desktops had the good fortune to receive a beautiful door in his face!
After a healthy reboot the machine, I finally managed to connect through Remote Desktop and, looking through the Windows event log to find some clue that would make me understand what had happened, I noticed some funny errors like:
Event Type: Error Event Source
: NtServicePackEvent
Category: NoneEvent
Well, the mishap and I 'just happened today, when, seized by an attack of acute Stakhanovism, I decided to start a good week in anticipation of a good half-hour into the company and tried to access one of the Our server via remote desktops had the good fortune to receive a beautiful door in his face!
After a healthy reboot the machine, I finally managed to connect through Remote Desktop and, looking through the Windows event log to find some clue that would make me understand what had happened, I noticed some funny errors like:
Event Type: Error Event Source
: NtServicePackEvent
Category: NoneEvent
ID: 4373
Date: 07/05/2007
Time: 10:29:58
User: N / A
Computer: XXXXXXXX
Description: Windows Server 2003 KB833407 installation failed.The parameter is incorrect.
Date: 07/05/2007
Time: 10:29:58
User: N / A
Computer: XXXXXXXX
Description: Windows Server 2003 KB833407 installation failed.The parameter is incorrect.
Microsoft public a complete description of the above problem at http://support.microsoft.com/kb/822798 proposing several possible solutions.
Among the various options I decided to follow that which proposed to rename the file in the file Edb.log edb.tst, and everything has resumed normal operation, so that, even before the updates failed to apply the SP 2 are been installed without any problems.
The following steps followed for the resolution of the problem.
1. Command Prompt windows, type net stop cryptsvc
2. Remove all tmp *. cat files from cacrtelle:
2. Remove all tmp *. cat files from cacrtelle:
- % systemroot% \\ system32 \\ CatRoot \\ {127D0A1D-4EF2-11D1-8608-00C04FC295EE}
- % systemroot% \\ system32 \\ CatRoot \\ {F750E6C3-38EE-11D1-85E5-00C04FC295EE }
3. from the command prompt type:
- net stop cryptsvc
- ren% systemroot% \\ System32 \\ Catroot2 \\ Edb.log edb.tst
- start cryptsv
- exit
0 comments:
Post a Comment