SUS update problem with W2K clients 1

[torin8]

Seem to be having a problem with a few of my client PC's in that the users complain that every morning they come in and log in as normal but then the computer immiediately says that an update has been applied and needs to reboot without giving the user the option to stop it. The user after the machine reboots can then log on normally.

Event log entries for a couple of common items in the workstation are below:

Anyone any ideas?

Application logs
Event Type: Error
Event Source: Application Management
Event Category: None
Event ID: 102
Date: 21/10/2004
Time: 07:35:54
User: NT AUTHORITY\SYSTEM
Description:

The install of application Microsoft Windows Update Auto Update from policy Default Domain Policy failed. The error was : Fatal error during installation.

Event Type: Error
Event Source: Application Management
Event Category: None
Event ID: 108
Date: 20/10/2004
Time: 07:51:43
User: NT AUTHORITY\SYSTEM


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 : Fatal error during installation.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 20/10/2004
Time: 07:51:43
User: NT AUTHORITY\SYSTEM

Description:
The Group Policy client-side extension Application Management was passed flags (1) and returned a failure status code of (1603).


***************************************************************************************************************
Security Logs

Event Type: Information
Event Source: Automatic Updates
Event Category: (2)
Event ID: 21
Date: 02/12/2004
Time: 08:35:36
User: N/A

Description:
The description for Event ID ( 21 ) in Source ( Automatic Updates ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: - Security Update, February 13, 2002 (MSXML 4.0).

Also for event ID 18 and 19 with same message

 

[Stiddy]

The user after the machine reboots can then log on normally." That is how SUS is suppose to work if the user logging on is not inh the local administative group on that box. If he/she were an admin, then they would be able to choose if the reboot should take place or not.

Although I believe the machine should have rebooted overnight when the update was applied. As far as some of the events you posted I will try to help you look into them more.

 

[MisterNiceGuy]

Updating MSXML on the affected computers to the latest service pack should solve this problem for you.

http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en

 

[torin8]

Thanks for the advice - I've had a bit of a further look at the even logs and yes it does seem to be something to do with the XML Parser. This update seems to be failing on these machines (through SUS) and it reschedules itself for the next night - where is fails again (see even log entry below). Anyone any ideas how to get this update to work?

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 03/12/2004
Time: 08:35:36
User: N/A

Description:
Product: Microsoft XML Parser and SDK -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2103. The arguments are: 26, ,

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

[MisterNiceGuy]

Updating MSXML on the affected computer to the latest service pack should take care of this for you.