SMS 2003 ITMU failure 11412 using February's wsusscn2.cab
- From: "Fran Vázquez" <fvazquez@xxxxxxxxxxxxxxxx>
- Date: Tue, 19 Feb 2008 09:51:34 +0100
Hello everyone,
I'm stuck trying to distribute February's patches using ITMU. I manually
downloaded and sync'ed wsusscn2.cab with no issues. The new patches appear
under "Software Updates", and there is nothing out of the ordinary reported
in WUSSyncXML.log. But the problem arises when clients try to execute the
up-to-date "Microsoft Updates Tool". Every single one of them fails with the
following error:
'The program for advertisement "LAB20023" failed ("LAB0001C" - "Microsoft
Updates Tool"). The failure description was "11412".
User context: NT AUTHORITY\SYSTEM
Possible cause: The program generated an installation status Management
Information Format (MIF) file with a status value of Failed.
Solution: For more information about the failure, refer to the documentation
for the program you are distributing.'
I've found a little bit more of information in the SmsWusHandler.log file:
'~~======== SmsWusHandler Started ======== $$<SmsWusHandler><Mon Feb 18
13:05:03.292 2008 Hora estándar romance><thread=5652 (0x1614)>
Scan process started with cmdline =
/Catalog:C:\WINDOWS\system32\VPCache\LAB0001C\wsusscn2.cab
/OutputXml:C:\WINDOWS\system32\VPCache\LAB0001C\Results.xml
$$<SmsWusHandler><Mon Feb 18 13:05:03.292 2008 Hora estándar
romance><thread=5652 (0x1614)>
WUS client version detected on the machine = 7.0.6000.381.
$$<SmsWusHandler><Mon Feb 18 13:05:03.307 2008 Hora estándar
romance><thread=5652 (0x1614)>
Running the SMS WUS Handler in scan mode $$<SmsWusHandler><Mon Feb 18
13:05:03.307 2008 Hora estándar romance><thread=5652 (0x1614)>
LocaleID=<1033> will be used to get localised properties.
$$<SmsWusHandler><Mon Feb 18 13:05:03.401 2008 Hora estándar
romance><thread=5652 (0x1614)>
Searching for software updates now. $$<SmsWusHandler><Mon Feb 18
13:05:03.401 2008 Hora estándar romance><thread=5652 (0x1614)>
Search filter - Type='Software' $$<SmsWusHandler><Mon Feb 18 13:05:03.401
2008 Hora estándar romance><thread=5652 (0x1614)>
Using C:\WINDOWS\system32\VPCache\LAB0001C\wsusscn2.cab as the
offline-catalog. $$<SmsWusHandler><Mon Feb 18 13:05:03.401 2008 Hora
estándar romance><thread=5652 (0x1614)>
Registering a new scan package service with the Windows Update Agent.
$$<SmsWusHandler><Mon Feb 18 13:05:03.417 2008 Hora estándar
romance><thread=5652 (0x1614)>
ERROR : AddScanPackageService() failed, win32 error code = 0
$$<SmsWusHandler><Mon Feb 18 13:05:03.620 2008 Hora estándar
romance><thread=5652 (0x1614)>
ERROR: Search() failed with hRes=0x800b0100 $$<SmsWusHandler><Mon Feb 18
13:05:03.635 2008 Hora estándar romance><thread=5652 (0x1614)>
0x800b0100 is the hresult value for the operation. Returning 256 as the exit
code. $$<SmsWusHandler><Mon Feb 18 13:05:03.651 2008 Hora estándar
romance><thread=5652 (0x1614)>
~~ ======= SmsWusHandler Terminating ======= '
From what I understand, the process stops when Windows Update Agent iscalled. The exit code returned, 256, should suffice. But I've been unable to
find any related information. I've seen a lot of trouble with ITMU and this
failure 11412, however. So I tried applying the usual, blind "fixes":
re-registering XML dll's, reinstalling Windows Update Agent, etc. To no
avail. What puzzles me is the consistency of the failure. I mean, any and
all clients fail just after downloading the new patch definition file.
Please, does someone have a clue?
.
- Follow-Ups:
- RE: SMS 2003 ITMU failure 11412 using February's wsusscn2.cab
- From: Sherry Kissinger [MVP-SMS]
- RE: SMS 2003 ITMU failure 11412 using February's wsusscn2.cab
- Prev by Date: RE: Problemas with SMS Administrator Behind firewall
- Next by Date: RE: Problemas with SMS Administrator Behind firewall
- Previous by thread: RE: Problemas with SMS Administrator Behind firewall
- Next by thread: RE: SMS 2003 ITMU failure 11412 using February's wsusscn2.cab
- Index(es):
Relevant Pages
|
