Re: The failure discription was "11204"

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ivan P (IvanP_at_discussions.microsoft.com)
Date: 07/09/04 

Date: Fri, 9 Jul 2004 03:18:01 -0700

I have created a new scan tool package to use with servers, but I maintain the old scan tool package for client computers. I have seen the Patchinstall.log, several times. First of all, the scan tool did not run on computers. I have run the tool manually, and I have no errors now. The scan tool works well if you take a view to PatchInstall.log but when I am going to see if the installation of the update has been correct in the client computers, I see the updates nowhere nor I can localize the .log of every one of the updates that Patchinstall.log say that are installed. And "the failure discription was "11204"" continue. What else can I do?

"Adam Welker [MSFT]" wrote:

> Have you created a new scan tool package recently or changed the name?
> 11204 is actually a status message number for a status message generated by
> the patch installation agent on the client. You could view the
> patchinstall.log file from one of the clients to see exactly what the error
> is.
>
> --
> Adam Welker
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ivan P" <Ivan P@discussions.microsoft.com> wrote in message
> news:7CFD2AD2-FBC1-4BD2-BA90-E6BB494DF8DA@microsoft.com...
> > I have been distributing software updates since I installed sms 2003
> without problems. It have worked fine until last week. All the client
> computers have the following event, every time the package is advertised,
> now it is every hour:
> > The program for advertisement "CEN2000F" failed ("CEN0000C" - "MBSA -
> Client Patches").The failure discription was "11204". User context: NT
> AUTHORITY\SYSTEM
> > Possible cause: The program generates 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 assure that the updates that I want to distribute, I have distributed
> them previously, so format and parameters are OK. I have created another
> package of software updates and I have got the same problem.
> Patchinstall.log tells me what patches are authorized, aplicable and
> installed and ScanWrapper.log tells that a complete scan has been produced
> every hour because I modified the settings. None of the applicable updates
> are installed on the clients.
> >
> > Could anyone help me? I am worried about this.
> >
> > Thanks in advance,
> > Ivan
> >
> >
>
>
>

Relevant Pages

  • Re: Client push question - the plot thickens
    ... for clients within the site boundaries of a secondary site are disseminated ... If Client Push is enabled at that site then the ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... patches got installed. ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
  • Re: Office Installation Not Syncing to AIP
    ... to remove the clientside patches to fix the mixed state.. ... We want to replace all files since we are reaching to a brand new AIP. ... To answer your question about whether or not you can tell how the client ... If the installation is in a "mixed state" the symptom that you usually see ...
    (microsoft.public.officeupdate)
  • Re: Client push question - the plot thickens
    ... SMS 2003 and Advanced Client push installation behavior. ... secondary site unless the secondary site has both initiated discovery of the ...
    (microsoft.public.sms.admin)