RE: SMS 2003 ITMU failure 11412 using February's wsusscn2.cab

There's a good thread here about people w/11412, and the various methods they
used to fix it: http://www.myitforum.com/forums/m_153907/tm.htm

To quickly summarize, make sure Automatic Updates service is able to be
started, verify you have the latest Windows Update Agent installed, BITS (at
least 2.0) can be started, and try the batch file on a client to re-register
dlls/restart services.
--
Standarize. Simplify. Automate.


"Fran Vázquez" wrote:

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 is
called. 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?



.

Relevant Pages

  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Client not yet reported
    ... Microsoft Online Newsgroup Support ... I understand that a client workstation is always in "not ... |> The root cause can be at either the server side or the client side. ... |> any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: Global Address Book Update
    ... >>> outlook 2003 on a Windows 2000 clients using RPC over HTTP. ... Bring up ESM, Recipients, Offline Address Lists. ... On the Outlook client ... >>> updates the Offline Address Book on the client every 24 hours. ...
    (microsoft.public.windows.server.sbs)
  • RE: Global Address Book Update
    ... I understand that you want to know how to force outlook client to update ... service ''Microsoft Exchange System Attendant'' and choose to Restart it. ... Additional information about outlook clients and GAL updates time frequency: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2K3 and 2003 term server problem since SP1 upgrade
    ... any of the client except the client inside the lan. ... we only know you can access the TS box from the LAN ... Please understand if you put the external NIC to router directly, ... I will be here waiting for your updates. ...
    (microsoft.public.windows.server.sbs)
Quantcast