Urgent issue with XP SP2 RTM

[Guest]

Hi all

We have been testing XP SP2 RTM today - courtesy of our MSDN subscribtion -
and we have an urgent problem that we dont have a good answer to.

Upon applying SP2, the Windows Installer refuses to install anything from
the network. Local installation may not be a problem (I say may because we
manually fixed the issue before we tried a local install).

Checking the temporary log file reveals the following error
"Internal Error 2755. 30, \\server\share\Gpmc\gpmc.msi"

Checking the event logs reveals a number of things:
- Application log ---
Warning, Failed to connect to server. Error: 0x80070005

- System log ---
The requested lookup key was not found in any active activation context.
Source: SCM
Event ID: 7023

- Security log ---
Failure audit
Category: Object Access
Event ID: 560
User: Network Service
From the Description:
Object Name: MSIServer
Client User Name: NETWORK SERVICE
Accesses: Query service configuration information
Query status of service
Enumerate dependencies of service
Query information from service

With respect to the user interface, the initial MSI initialisation screen
takes in excess of forty seconds to appear. Once it does, it takes a little
longer to fail with the following error:

"The Windows Installer Service could not be accessed. This can occur if you
are running in Safe Mode, or if the Windows Installer is not correctly
installed. Contact your support personnel for assistance."


These are the details of the problem. The fix seems to be to run "msiexec
/unreg" followed by "msiexec /regserver".

The problem with this fix is it's manual, and the reason that this is a
problem is that it will be deployed through Software Update Services - which
is inherently automated.

So the position we find ourselves in is that a possibly broken Service Pack
is going to be automatically be deployed to nearly 1800+ XP clients (subject
to the SUS approval process).

At the moment, I'm in the position of having to write a group policy-hosted
computer startup script to perform these commands, but then I have to write
extra material to wrap around it so that it only runs once etc etc. This
seems too complicated an issue for something that should just work out of the
box.

Can anyone shed some light on whether they've had this problem, and if so
what the fix was - assuming it's different to ours?

Currently, this is a deployment blocker for us, as a great deal of our
software relies on the Windows Installer, and as our builds are automated
through RIS this impact is nothing short of catastrophic.

Regards
Lain Robertson
Siemens Australia

 

[Test Man]

Didn't you test this with the Release Candidate 1 and 2 which was released
months ago? Did you get the same result?

 

[Norm]

I am having the exact same problem with clean installs from
slipstreamed SP2 CD.

Also have found that I can no longer run any WSH/VBScripts, this is
not a problem on XP where it has been updated with SP2, only on clean
builds.

Anyone have any ideas?

 

[Torgeir Bakken \(MVP\)]

I am having the exact same problem with clean installs from
slipstreamed SP2 CD.

Also have found that I can no longer run any WSH/VBScripts, this is
not a problem on XP where it has been updated with SP2, only on clean
builds.

Anyone have any ideas?

Hi

If you download and install WSH 5.6 from the link below, does it
start to work again?

http://msdn.microsoft.com/downloads/list/webdev.asp

 

[Test Man]

You can temporarily stop SP2 from being deployed if it's a problem

http://www.microsoft.com/downloads/...ba-ea5d-4425-89c1-c1cb1ccd463c&DisplayLang=en

http://www.microsoft.com/downloads/...42-c6d7-4402-a5a9-9d52a9cd2500&DisplayLang=en

http://www.microsoft.com/downloads/...7b-f3d7-48d6-b86c-1256c0321727&DisplayLang=en

 

[Guest]

Thanks for that. As it will be deployed via SUS we already have control over
it's deployment. The real issue is that the service pack breaks something.

What I was hoping to verify was whether other people were having this
problem (which we can easily reproduce) and as such whether there was any
acknowledgement from Microsft that this was a known issue. As I said earlier,
this has been a known issue for many people starting with RC1.

Regards
Lain
Siemens Australia

 

[Norm]

I have tried reverting back to the same version of WSH as used on
other systems and this has no effect. It seems to be some kind of
security settings that are stopping the script from running.

When a Win XP SP1 machine is upgraded to SP2 it runs scripts fine,
however if you then apply a GPO created with SP2 to such a machine
scripting stops functioning. Even if no settings are configured in
the GPO.

Win XP SP2 machines built from scratch will not runs scripts.

I have already blocked SP2 from being installed onto our systems,
however as I would like to roll it out, this is a problem I need to
solve.

 

[Norm]

Hi,

If you are still having problems check to see if you have these two
settings enabled in Group Policy under Computer Configuration\Windows
Settings\Security Settings\Local Policies\User Rights Assignment:

"Impersonate a Client After Authentication"
"Create Global Objects"

The settings don't seem to show correct from a Windows XP client...
have a look via Group Policy on a Windows 2000 Server.

Refer: Overview of the "Impersonate a Client After Authentication" and
the "Create Global Objects" Security Settings (821546.KB.EN-US.2.2)

http://support.microsoft.com/default.aspx?kbid=821546

Changing both these settings to 'Not Defined' solved the issues on my
XP SP2 machines. Also try placing your XP SP2 PCs into a OU with
Block Inheritance set to see if it is a setting in Group Policy
causing your problems.

Regards,

Norman