Re: Adv Client - Causing MSI Installation Issues

This is the same problem we are experiencing, except we have about 5000
machines to go through and we have had to slow down the role out immensely
because the number of calls generated each day when we do another group of
machines.

Please if anyone else has any input we would greatly appreciate it.

"Ahmad El Ghazouly" wrote:

> guys , please can any one help
> you are my last chance.
>
> "Ahmad El Ghazouly" <aelghaz@xxxxxxxxxx> wrote in message
> news:ermkdqfkFHA.3580@xxxxxxxxxxxxxxxxxxxxxxx
> > Here is an illustration on the problem that appeared after the client
> > installation.
> >
> > a.. we have 291 machines discovered, 234 clients installed
> > b.. 247 machines are windows 2000 professional with service pack 3, 223
> > clients installed.
> > c.. SMS client was pushed on the machines using client push installation
> > method. Software and Hardware cycle are collected indifferent time. (I.e
> > Software inventory in Sunday @ 3:00 p.m., Hardware inventory in Monday @
> > 3:00 p.m.
> > d.. Hardware Inventory, Software Inventory, Remote Tools, Advertised
> > programs, Software Metering agents are all installed and enabled.
> > e.. After the client installation no problem appeared.
> > f.. After the software inventory was run on schedule, 5 machines claim to
> > have problems.
> > g.. Two different problem aroused, first was user profile corruption, and
> > that was solved by deleting the user profile and rebuild it again.
> > h.. The other one was having problems with office applications word,
> > excel, outlook,...etc. ( we have office 2000 premium) are not running ,
> > and the antivirus (Symantec AV corporate edition) displays an MSI
> > Installer message waiting for the installation path. Reinstallation the
> > same package failed, and the only solution was to install office 2003 or
> > office 2000 professional.
> > i.. As a result I stopped the Software Inventory agent. by unchecking it
> > for client agents
> > j.. After the hardware inventory was run on schedule, more than 50
> > machines have the same problem. And also the solution was either to
> > install office 2000 professional or office 2003.
> > k.. Here are some of the event messages that was appeared on some clients
> > machines
> > Event Type: Warning
> >
> > Event Source: MsiInstaller
> >
> > Event Category: None
> >
> > Event ID: 1004
> >
> > Date: 7/25/2005
> >
> > Time: 1:14:24 PM
> >
> > User: N/A
> >
> > Computer: XXXX
> >
> > Description:
> >
> > Detection of product '{00010409-78E1-11D2-B60F-006097C998E7}', feature
> > 'OfficeUserData', component '{C9AF9050-C8BE-11D1-9C67-0000F81F1B38}'
> > failed. The resource
> > 'HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Common\UserData' does not
> > exist.
> >
> >
> >
> >
> >
> > Event Type: Warning
> >
> > Event Source: MsiInstaller
> >
> > Event Category: None
> >
> > Event ID: 1001
> >
> > Date: 7/25/2005
> >
> > Time: 1:11:29 PM
> >
> > User: N/A
> >
> > Computer: XXXX
> >
> > Description:
> >
> > Detection of product '{0EFC6259-3AD8-4CD2-BC57-D4937AF5CC0E}', feature
> > 'SAVBaseFiles' failed during request for component
> > '{96634D44-24A0-402B-8231-B3B0DEB8DA50}'
> >
> >
> >
> > Event Type: Warning
> >
> > Event Source: EventSystem
> >
> > Event Category: Firing Agent
> >
> > Event ID: 4100
> >
> > Date: 7/20/2005
> >
> > Time: 8:15:46 AM
> >
> > User: N/A
> >
> > Computer: XXXX
> >
> > Description:
> >
> > The COM+ Event System failed to create an instance of the subscriber
> > {6295DF2D-35EE-11D1-8707-00C04FD93327}. CoCreateInstanceEx returned
> > HRESULT 8000401A.
> >
> >
> >
> > Event Type: Error
> >
> > Event Source: Application Management
> >
> > Event Category: None
> >
> > Event ID: 108
> >
> > Date: 7/19/2005
> >
> > Time: 4:47:03 PM
> >
> > User: NT AUTHORITY\SYSTEM
> >
> > Computer: XXXX
> >
> > Description:
> >
> > Failed to apply changes to software installation settings. Software
> > changes could not be applied. A previous log entry with details should
> > exist. The error was The installation source for this product is not
> > available. Verify that the source exists and that you can access it. .
> >
> >
> >
> > Event Type: Error
> >
> > Event Source: Application Management
> >
> > Event Category: None
> >
> > Event ID: 102
> >
> > Date: 7/19/2005
> >
> > Time: 4:47:03 PM
> >
> > User: NT AUTHORITY\SYSTEM
> >
> > Computer: XXXX
> >
> > Description:
> >
> > The install of application Microsoft Windows Update Auto Update from
> > policy Adding Windows Update client failed. The error was The
> > installation source for this product is not available. Verify that the
> > source exists and that you can access it. .
> >
> >
> >
> > Event Type: Information
> >
> > Event Source: WMDM PMSP Service
> >
> > Event Category: None
> >
> > Event ID: 105
> >
> > Date: 7/19/2005
> >
> > Time: 4:46:50 PM
> >
> > User: N/A
> >
> > Computer: XXXX
> >
> > Description:
> >
> > The service was started.
> >
> >
> >
> > Event Type: Information
> >
> > Event Source: Application Management
> >
> > Event Category: None
> >
> > Event ID: 301
> >
> > Date: 7/19/2005
> >
> > Time: 4:46:48 PM
> >
> > User: NT AUTHORITY\SYSTEM
> >
> > Computer: XXXX
> >
> > Description:
> >
> > The assignment of application Microsoft Windows Update Auto Update from
> > policy Adding Windows Update client succeeded.
> >
> >
> >
> > Event Type: Warning
> >
> > Event Source: MsiInstaller
> >
> > Event Category: None
> >
> > Event ID: 1001
> >
> > Date: 7/25/2005
> >
> > Time: 11:46:49 AM
> >
> > User: PGESCO\shali
> >
> > Computer: XXXX
> >
> > Description:
> >
> > Detection of product '{00000409-78E1-11D2-B60F-006097C998E7}', feature
> > 'OUTLOOKFiles' failed during request for component
> > '{CC29EA4B-7BC2-11D1-A921-00A0C91E2AA2}'
> >
> >
> > "Ahmad El Ghazouly" <aelghaz@xxxxxxxxxx> wrote in message
> > news:uGfc3uekFHA.1968@xxxxxxxxxxxxxxxxxxxxxxx
> >> Guys
> >> I am having the same problem, this is a disaster for me
> >> can anybody help plz
> >>
> >> "RickR" <RickR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:2367A6E0-2F1A-491E-B29D-9DAE6FCABE35@xxxxxxxxxxxxxxxx
> >>> Currious is anyone else has seen this problem or has any thoughts:
> >>> We are upgrading to 2003, installing the Adv Client on Windows 2000 SP3
> >>> machines. On about 25% of the machines any application installed via
> >>> MSI
> >>> with self healing gets corrupt and requires a reinstallation. With
> >>> Office
> >>> 2003 we have to use article KB295823. and the Installer Cleanup Utility
> >>> to
> >>> before we can do a reinstall. We have had the problem with Visual
> >>> Studio and
> >>> a few other products. Any assistance anyone can provide would be great.
> >>> Thanks - Rick
> >>
> >>
> >
> >
>
>
>
.

Relevant Pages

  • Re: SMS 2k3 Advanced Client not installing...
    ... Can you run a command session as local sytem and try to do a net stop on the ... > may try on one client to remove BITS then re-install the advanced client. ... >>> Have you configured your Push Installation account? ... I can't tell you SP level on>> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)
  • Re: Adv Client - Causing MSI Installation Issues
    ... Here is an illustration on the problem that appeared after the client ... SMS client was pushed on the machines using client push installation ... After the software inventory was run on schedule, 5 machines claim to ... Event Source: MsiInstaller ...
    (microsoft.public.sms.setup)
  • Re: XP clients do not appear in Collections
    ... So your XP machines are or are not being discovered? ... installation methods have NOT been enabled. ... Very soon after enabling the discovery methods, ... >>> have any site listed or indicate the client has installed. ...
    (microsoft.public.sms.admin)
  • Re: SMS 2k3 Advanced Client not installing...
    ... may try on one client to remove BITS then re-install the advanced client. ... It appears that either the BITS installation is failing or>> you are getting permission denied. ... I can't tell you SP level on> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)
  • Re: SMS Virtual Mouse Problem
    ... Desktop Client on the machines but what we could not understand is that why ... About the Problem of the lose of drivers after the installation of SMS. ...
    (microsoft.public.sms.admin)
Loading