Re: Adv Client - Causing MSI Installation Issues
- From: "Paul Thomsen [MSFT]" <pthomsen@xxxxxxxxxxxxx>
- Date: Wed, 3 Aug 2005 20:50:49 -0700
It's a long post, so it's hard to be sure, but it looks like a
traditional Windows Installer source path issue. That means the apps can't
be repaired and sometimes can't even be upgraded due to lack of the original
source bits. Maybe the user installed from a CD-ROM, which of course is
likely no longer in the drive.
SMS does provide a good solution to this. Set up an SMS package for the
original version and set the details in the package's Windows Installer tab.
SMS will take care of the rest.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ahmad El Ghazouly" <aelghaz@xxxxxxxxxx> wrote in message
news:uM$1PaPlFHA.3692@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: domain1/user1
>
> Computer: XXXX
>
> Description:
>
> Detection of product '{00000409-78E1-11D2-B60F-006097C998E7}', feature
> 'OUTLOOKFiles' failed during request for component
> '{CC29EA4B-7BC2-11D1-A921-00A0C91E2AA2}'
>
.
- Prev by Date: RE: SMS Desktop OS upgrade?
- Next by Date: Re: Object ids
- Previous by thread: RE: SMS Desktop OS upgrade?
- Next by thread: Re: Object ids
- Index(es):
Relevant Pages
|
