Hello,
As per the Compliance rules, we are supposed to Patch the Domain Controllers running Windows Server 2003 SP2 every 3 months. We recently deployed the patch and I noiced "Failed to install Updates" in the Reports. Upon further investigation, I noticed the below error message in UpdatesDeployment.log:
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_3e952bc5-aad2-4117-ab65-a42f96298868) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_5fc9d5fb-b777-48e9-ab63-5fd773863e96) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_839e8f9f-188f-48b6-b43a-a4c3cb58c679) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_932ecd0d-729f-46b7-9e18-4e021d3988f6) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_a7fdb01a-4517-4906-91df-52916085d7e7) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_f15b1f6f-7db6-4efa-b6f7-0c7e54e1a939) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
Update (Site_F3F7B4B4-52F2-4D21-999E-829DA6019800/SUM_f21b0303-4d18-4a9b-9bda-8a796062189b) Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80040668 UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 536 (0x0218)
The Security Updates are for .Net Framework 2.0
Upon further troubleshooting, I was directed to http://technet.microsoft.com/en-us/library/bb735894.aspx which says this is an expected behaviour and should be resolved during next Deployment evaluation cycle. Hence, I manually initiate "Software Updates Deployment Evaluation Cycle", but the error still remains.
I noticed that in WUAHandler.log:
1. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2604092) (3e952bc5-aad2-4117-ab65-a42f96298868, 105) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
2. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2742596) (5fc9d5fb-b777-48e9-ab63-5fd773863e96, 201) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
3. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2804577) (839e8f9f-188f-48b6-b43a-a4c3cb58c679, 201) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
4. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2729450) (932ecd0d-729f-46b7-9e18-4e021d3988f6, 201) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
5. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2844285) (a7fdb01a-4517-4906-91df-52916085d7e7, 202) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
6. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2833940) (f15b1f6f-7db6-4efa-b6f7-0c7e54e1a939, 202) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
7. Update (Missing): Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2789643) (f21b0303-4d18-4a9b-9bda-8a796062189b, 201) WUAHandler 7/23/2013 9:06:13 AM 4460 (0x116C)
Async installation of updates started. WUAHandler 7/23/2013 9:06:15 AM 4460 (0x116C)
Update 1 (3e952bc5-aad2-4117-ab65-a42f96298868) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:06:40 AM 4156 (0x103C)
Update 2 (5fc9d5fb-b777-48e9-ab63-5fd773863e96) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:07:00 AM 1520 (0x05F0)
Update 3 (839e8f9f-188f-48b6-b43a-a4c3cb58c679) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:07:20 AM 5296 (0x14B0)
Update 4 (932ecd0d-729f-46b7-9e18-4e021d3988f6) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:07:40 AM 2620 (0x0A3C)
Update 5 (a7fdb01a-4517-4906-91df-52916085d7e7) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:08:00 AM 4432 (0x1150)
Update 6 (f15b1f6f-7db6-4efa-b6f7-0c7e54e1a939) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:08:19 AM 6096 (0x17D0)
Update 7 (f21b0303-4d18-4a9b-9bda-8a796062189b) finished installing (0x00000000), Reboot Required? No WUAHandler 7/23/2013 9:08:39 AM 4276 (0x10B4)
BUT, in UpdatesDeployment.log: IT SAYS, ciStateError.
Raising event:
[SMS_CodePage(850), SMS_LocaleID(2057)]
instance of SMS_SUMAgentAssignmentError_UpdatesFailures
{
AssignmentId = "{94385427-B490-48BE-9350-95A7E0159A35}";
ClientID = "GUID:A4BC54A0-9E5D-4428-8250-DB33CDF68DFA";
DateTime = "20130723080843.688000+000";
insAssignmentId = "{94385427-B490-48BE-9350-95A7E0159A35}";
MachineName = "ServerName";
ProcessID = 4040;
SiteCode = "000";
ThreadID = 5644;
Win32ErrorCode = 2147747432;
};
UpdatesDeploymentAgent 7/23/2013 9:08:43 AM 5644 (0x160C)