Re: Problems installing XP SP2!

From: David Randall [MS] (davidra_at_microsoft.com)
Date: 09/02/04

Next message: ipsec23: "Re: Office XP Installation Problem!"
Previous message: jc: "Removed Clients Still Appear as Client Installed"
In reply to: ipsec23: "Re: Problems installing XP SP2!"
Next in thread: ipsec23: "Re: Problems installing XP SP2!"
Reply: ipsec23: "Re: Problems installing XP SP2!"
Messages sorted by: [ date ] [ thread ]

Date: Thu, 2 Sep 2004 09:02:21 -0700

The error listed: 2147942402 is a "file not found" error. Please check your
package source directory and make sure the that XPSPS2sms.exe file exists in
that location.

I downloaded SP2 from
http://www.microsoft.com/downloads/details.aspx?FamilyId=049C9DBE-3B8E-4F30-8245-9E368D3CDB5A&displaylang=en

and then extracted the dowloaded file WindowsXP-KB835935-SP2-ENU.exe using
the command:
WindowsXP-KB835935-SP2-ENU.exe /x

After the files are extracted, you should have an "update" folder and in
that, a file called "update.exe" That is the file that you need to specify
in your SMS Program command line property.

I also went back and looked at your original error message, it was error
code: 2147942593, which translated to "... is not a valid Win32
application." Which makes me wonder about the bundle for XPSP2 that you
have downloaded.

I will investigate the .SMS file properties with one of our App Compat
people here, and see if we need to get a documentation change made,
otherwise, please verify that you have the update.exe file, and use that in
your command line, just as I had posted earlier.

Let me know how it goes. We'll get it working!

-- 
-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"ipsec23" <ipsec23@discussions.microsoft.com> wrote in message 
news:5B1D3636-D0A9-46AB-8FE2-8550BCF98D47@microsoft.com...
> Hi David,
> Thankyou for the response.I tried the two commnad line options but both of
> them seem to give an error for some kinda reason.Here's the snippet of the
> execmgr.log.
> Execmgr.log
> =======
> Executing program as a script
> Invalid executable file update/XPSP2sms.exe
> Raising event:
> [SMS_CodePage(437), SMS_LocaleID(1033)]
> instance of SoftDistProgramBadEnvironmentEvent
> {
> AdvertisementId = "CIT2001A";
> ClientID = "GUID:F8E07B22-FBDC-46FA-A3C0-C594E0D3FDA4";
> CommandLine = "update/XPSP2sms.exe /q /f /forcerestart";
> DateTime = "20040902042524.579000+000";
> DriveLetter = "";
> MachineName = "TWO";
> PackageName = "CIT00009";
> ProcessID = 1604;
> ProgramName = "Automated upgrade from XP or XPSP1";
> SiteCode = "CIT";
> ThreadID = 3588;
> Win32ErrorCode = 2147942402;
> WorkingDirectory = "";
> };
> Raised Program Bad Environment Event for Ad:CIT2001A, Package:CIT00009,
> Program: Automated upgrade from XP or XPSP1
> EnterRsRuningState failed to run script update/XPSP2sms.exe /q /f
> /forcerestart 0x80009106
> OnOptionalExecutionRequest failed at EvaluateRequestForExecution
> OnOptionalExecutionRequests failed for program Automated upgrade from XP 
> or
> XPSP1
> Policy is updated for Program: Automated upgrade from XP or XPSP1, 
> Package:
> CIT00009, Advert: CIT2001A
> ......
> Executing program as a script
> Invalid executable file update/update.exe
> Raising event:
> [SMS_CodePage(437), SMS_LocaleID(1033)]
> instance of SoftDistProgramBadEnvironmentEvent
> {
> AdvertisementId = "CIT2001A";
> ClientID = "GUID:F8E07B22-FBDC-46FA-A3C0-C594E0D3FDA4";
> CommandLine = "update/update.exe /q /f /forcerestart";
> DateTime = "20040902043018.201000+000";
> DriveLetter = "";
> MachineName = "TWO";
> PackageName = "CIT00009";
> ProcessID = 1604;
> ProgramName = "Automated upgrade from XP or XPSP1";
> SiteCode = "CIT";
> ThreadID = 1624;
> Win32ErrorCode = 2147942402;
> WorkingDirectory = "";
> };
> Raised Program Bad Environment Event for Ad:CIT2001A, Package:CIT00009,
> Program: Automated upgrade from XP or XPSP1
> EnterRsRuningState failed to run script update/update.exe /q /f
> /forcerestart 0x80009106
> OnOptionalExecutionRequest failed at EvaluateRequestForExecution
> OnOptionalExecutionRequests failed for program Automated upgrade from XP 
> or
> XPSP1
>
> Many Thanks!!
>
> "David Randall [MS]" wrote:
>
>> Sounds like you have the update folder and all of the expanded files for
>> SP2.
>>
>> I had used the command:
>>
>> update/update.exe /q /f /forcerestart
>>
>> I also made sure this was an installation that runs with administrative
>> permission.
>>
>> If your quoted command line below is what's exactly in the program
>> properties, then you need to change it to:
>>
>> update/XPSP2sms.exe /q /f /forcerestart
>>
>> Dave
>>
>> Full command line parameters for SP2 at:
>> http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/sp2entdp.mspx
>>
>>
>> -- 
>> -- 
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>> "ipsec23" <ipsec23@discussions.microsoft.com> wrote in message
>> news:B11E139F-9AD9-426D-8049-0A31A72466A6@microsoft.com...
>> > Hi David,
>> > Thanks for the response. I download the service pack that consited of 
>> > an
>> > i386 folder, .sms file etc..and created a "package from definition" 
>> > using
>> > the
>> > .sms file.Once the package was created it generated 2 files "manual
>> > upgrade"
>> > and "Autoamtic upgrade" . Then created an advertisement to advertise 
>> > the
>> > prg.
>> > In the first 2 attempts the logs referred to a invalid syntax which was
>> > soemthing like "update/XPSP2sms.exe/q/f/forcerestart" .
>> > So are u suggesting that the cmd line be altered to be something like 
>> > this
>> > :
>> > "update.exe -x/XPSP2sms.exe/q/f/forcerestart"
>> > Thanks!
>> > "David Randall [MS]" wrote:
>> >
>> >> I'm not sure why you'd be getting error 193 from your program 
>> >> execution.
>> >>
>> >> How was your XPSP2sms.exe program made?
>> >>
>> >> Have you tried expanding out XP SP2 (using -x parameter) and running
>> >> update.exe with parameters to make it silent and unattended?
>> >>
>> >> -- 
>> >> -- 
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> "ipsec23" <ipsec23@discussions.microsoft.com> wrote in message
>> >> news:5E0E727B-9E4B-4ED1-94EC-0EDC06540DC4@microsoft.com...
>> >> > Hi,
>> >> > We are testing XP SP2 on a test client via SMS.I had posted earlier 
>> >> > on
>> >> > the
>> >> > same issue and i was suggested to check if the command line syntax 
>> >> > was
>> >> > right.
>> >> > I went ahead to make mofiifcations but i havent had any luck 
>> >> > yet.Logs
>> >> > show
>> >> > some sought of a fatal error!!!
>> >> > Below is the snippet of the execmgr.log.can someone kindly let me 
>> >> > know
>> >> > as
>> >> > to
>> >> > what the problem is.
>> >> > Mnay Thanks!
>> >> >
>> >> > Execmgr.log
>> >> > ========
>> >> > Mandatory execution requested for program Automated upgrade from XP 
>> >> > or
>> >> > XPSP1
>> >> > and advertisement CIT20013
>> >> > Creating mandatory request for advert CIT20013, program Automated
>> >> > upgrade
>> >> > from XP or XPSP1, package CIT00009
>> >> > Policy is updated for Program: Automated upgrade from XP or XPSP1,
>> >> > Package:
>> >> > CIT00009, Advert: CIT20013
>> >> > Requesting content from CAS for package CIT00009 version 1
>> >> > Raising event:
>> >> > [SMS_CodePage(437), SMS_LocaleID(1033)]
>> >> > instance of SoftDistWaitingContentEvent
>> >> > {
>> >> > AdvertisementId = "CIT20013";
>> >> > ClientID = "GUID:EBBDB8C9-49C2-448C-8CC0-CAC0C22D2D3F";
>> >> > DateTime = "20040830155510.878000+000";
>> >> > MachineName = "SATURN";
>> >> > PackageName = "CIT00009";
>> >> > PackageVersion = "1";
>> >> > ProcessID = 1540;
>> >> > ProgramName = "Automated upgrade from XP or XPSP1";
>> >> > SiteCode = "CIT";
>> >> > ThreadID = 464;
>> >> > };
>> >> > Successfully raised SoftDistWaitingContentEvent event for program
>> >> > Automated
>> >> > upgrade from XP or XPSP1
>> >> > Execution Request for program Automated upgrade from XP or XPSP1 
>> >> > state
>> >> > change from NotExist to WaitingContent
>> >> > Content is available for program Automated upgrade from XP or XPSP1.
>> >> > Notify user mandatory program Automated upgrade from XP or XPSP1 is
>> >> > about
>> >> > to
>> >> > run
>> >> > Execution Request for program Automated upgrade from XP or XPSP1 
>> >> > state
>> >> > change from WaitingContent to NotifyExecution
>> >> > Executing program XPSP2sms.exe /u /f  in Admin context
>> >> > Execution Request for program Automated upgrade from XP or XPSP1 
>> >> > state
>> >> > change from Running to Running
>> >> > Checking content location \\NUTMEG\SMSPKGD$\CIT00009\ for use
>> >> > Successfully selected content location \\NUTMEG\SMSPKGD$\CIT00009
>> >> > Executing program as a script
>> >> > Successfully prepared command line
>> >> > "\\NUTMEG\SMSPKGD$\CIT00009\XPSP2sms.exe"
>> >> > /u /f
>> >> > Command line = "\\NUTMEG\SMSPKGD$\CIT00009\XPSP2sms.exe" /u /f, 
>> >> > Working
>> >> > Directory = \\NUTMEG\SMSPKGD$\CIT00009\
>> >> > CreateProcess or CreateProcessAsUser failed to execute command line
>> >> > with
>> >> > non-recoverable error 193
>> >> > Raising event:
>> >> > [SMS_CodePage(437), SMS_LocaleID(1033)]
>> >> > instance of SoftDistProgramUnableToExecuteEvent
>> >> > {
>> >> > AdvertisementId = "CIT20013";
>> >> > ClientID = "GUID:EBBDB8C9-49C2-448C-8CC0-CAC0C22D2D3F";
>> >> > CommandLine = "\"\\\\NUTMEG\\SMSPKGD$\\CIT00009\\XPSP2sms.exe\" /u 
>> >> > /f";
>> >> > DateTime = "20040830155543.906000+000";
>> >> > MachineName = "PLUS";
>> >> > PackageName = "CIT00009";
>> >> > ProcessID = 1540;
>> >> > ProgramName = "Automated upgrade from XP or XPSP1";
>> >> > SiteCode = "CIT";
>> >> > ThreadID = 1728;
>> >> > Win32ErrorCode = 2147942593;
>> >> > WorkingDirectory = "\\\\NUTMEG\\SMSPKGD$\\CIT00009\\";
>> >> > };
>> >> > Raised Program Unable to Execute Event for Ad:CIT20013,
>> >> > Package:CIT00009,
>> >> > Program: Automated upgrade from XP or XPSP1
>> >> > EnterRsRuningState failed to run script XPSP2sms.exe /u /f 
>> >> > 0x80009101
>> >> > Fatal error 0x80009101 enountered for program Automated upgrade from 
>> >> > XP
>> >> > or
>> >> > XPSP1. This program will not retry.
>> >> > Execution Manager timer has been fired.
>> >>
>> >>
>> >>
>>
>>
>>

Next message: ipsec23: "Re: Office XP Installation Problem!"
Previous message: jc: "Removed Clients Still Appear as Client Installed"
In reply to: ipsec23: "Re: Problems installing XP SP2!"
Next in thread: ipsec23: "Re: Problems installing XP SP2!"
Reply: ipsec23: "Re: Problems installing XP SP2!"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: tclapp wrap problem in HP unix system
... The only thing that comes to my mind is that the command "package ... while executing ... When I use Tclapp GUI interface, I never add interpreter, some of my ...
(comp.lang.tcl)
how to run android after installation ?
... after executing make i m getting some warnings from "fd.c " like ... then i executed "tcl" command to enter tcl shell from there i executed ... to chk whether package is loaded or not by giving the command ...
(comp.lang.tcl)
Results for DTEXEC command
... I am executing a SSIS package from Management Studio using the DTEXEC ... In SQLSERVER 2000, i am getting those results in Query Analyzer by ... executing the package using the command DTSRUN. ...
(microsoft.public.sqlserver.dts)
Re: Windows update error 0x80242008
... 2.219: Hotfix started with following command line: /si ... Unexpected Error While Executing Line 1 ( ... Test.IE7InstallBlock.Section) of PreRequisite ...
(microsoft.public.windowsupdate)
RE: Open Form Code
... I've generally found that if you issue a DoEvents command after opening the ... I set that form's VISIBLE property to FALSE. ... VISIBLE property to TRUE immediately prior to executing the code. ...
(microsoft.public.access.formscoding)