G
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
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