Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

**HELP** Unable to get SP4 Package to work under SMS 2003

Status
Not open for further replies.
Apr 13, 2004
26
US
Getting dispirit and running out of time...

Target client PC has Windows 2000 Professional SP3 and SMS 2003 Advanced client installed. I have build a PACKAGE with corrisponding ADVERTISEMENT to install SP4 for Windows 2000 using the package definition file W2KSP4.SMS provided by Microsoft. Unable to get the package to run on the client PC. Keep getting a 1603 error message under Advertisement Status. Details for the status message:
===================START DETAIL ===========================
The program for advertisement "EMS2001C" failed ("EMS00012" - "Unattendent Update"). A failure exit code of 1603 was returned.
User context: NT AUTHORITY\SYSTEM

Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1603 is considered a failure.
Solution: For more information on the exit code, refer to the documentation for the program you are distributing.
=================END DETAIL=============================

Reviewing the EXECMGR.LOG on the client PC is not any more help:
===============START DETAIL================================
<![LOG[Execution Manager timer has been fired.]LOG]!><time="11:59:13.997+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1052" file="execreqmgr.cpp:4234">
<![LOG[Policy is updated for Program: Unattendent Update, Package: EMS00012, Advert: EMS2001C]LOG]!><time="11:59:50.629+240" date="04-28-2004" component="execmgr" context="" type="1" thread="708" file="execreqmgr.cpp:5022">
<![LOG[Mandatory execution requested for program Unattendent Update and advertisement EMS2001C]LOG]!><time="11:59:50.659+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="execreqmgr.cpp:2718">
<![LOG[Creating mandatory request for advert EMS2001C, program Unattendent Update, package EMS00012]LOG]!><time="11:59:50.659+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="execreqmgr.cpp:2811">
<![LOG[Requesting content from CAS for package EMS00012 version 1]LOG]!><time="11:59:50.729+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="contentaccesshelper.cpp:136">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
{
AdvertisementId = "EMS2001C";
ClientID = "GUID:2BFE58A7-A342-4392-B4E8-997862F7E046";
DateTime = "20040428155951.270000+000";
MachineName = "EMSPC329";
PackageName = "EMS00012";
PackageVersion = "1";
ProcessID = 748;
ProgramName = "Unattendent Update";
SiteCode = "EMS";
ThreadID = 1096;
};
]LOG]!><time="11:59:51.300+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="event.cpp:522">
<![LOG[Successfully raised SoftDistWaitingContentEvent event for program Unattendent Update]LOG]!><time="11:59:51.310+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="executionrequest.cpp:1791">
<![LOG[Execution Request for program Unattendent Update state change from NotExist to WaitingContent]LOG]!><time="11:59:51.310+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1096" file="executionrequest.cpp:367">
<![LOG[Content is available for program Unattendent Update.]LOG]!><time="11:59:51.450+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1052" file="executionrequest.cpp:3713">
<![LOG[Notify user mandatory program Unattendent Update is about to run]LOG]!><time="11:59:51.450+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1052" file="executionrequest.cpp:2141">
<![LOG[Execution Request for program Unattendent Update state change from WaitingContent to NotifyExecution]LOG]!><time="11:59:52.322+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1052" file="executionrequest.cpp:367">
<![LOG[Executing program \\emsprdsms1\smspkgc$\ems00012\update\update.exe -u -z in Admin context]LOG]!><time="12:00:03.898+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executionrequest.cpp:2296">
<![LOG[Execution Request for program Unattendent Update state change from Running to Running]LOG]!><time="12:00:03.898+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executionrequest.cpp:367">
<![LOG[Checking content location \\EMSPRDSMS1\SMSPKGC$\EMS00012\ for use]LOG]!><time="12:00:03.938+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:1194">
<![LOG[IsNetResourceAccessible failed with error code 0x00000005]LOG]!><time="12:00:03.958+240" date="04-28-2004" component="execmgr" context="" type="3" thread="1128" file="executioncontext.cpp:1564">
<![LOG[Rolling over to network access account to check content location]LOG]!><time="12:00:03.958+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:1218">
<![LOG[Successfully selected content location \\EMSPRDSMS1\SMSPKGC$\EMS00012]LOG]!><time="12:00:04.609+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:1262">
<![LOG[Checking UNC path \\emsprdsms1\smspkgc$\ems00012\update\ for access]LOG]!><time="12:00:04.619+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:1997">
<![LOG[Network UNC path \\emsprdsms1\smspkgc$\ems00012\update is accessible]LOG]!><time="12:00:04.629+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:2049">
<![LOG[Executing program as a script]LOG]!><time="12:00:04.629+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executionengine.cpp:79">
<![LOG[Successfully prepared command line "\\emsprdsms1\smspkgc$\ems00012\update\update.exe" -u -z]LOG]!><time="12:00:04.639+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="scriptexecution.cpp:330">
<![LOG[Command line = "\\emsprdsms1\smspkgc$\ems00012\update\update.exe" -u -z, Working Directory = \\EMSPRDSMS1\SMSPKGC$\EMS00012\]LOG]!><time="12:00:04.639+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="scriptexecution.cpp:178">
<![LOG[Created Process for the passed command line]LOG]!><time="12:00:05.120+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="scriptexecution.cpp:220">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "EMS2001C";
ClientID = "GUID:2BFE58A7-A342-4392-B4E8-997862F7E046";
CommandLine = "\"\\\\emsprdsms1\\smspkgc$\\ems00012\\update\\update.exe\" -u -z";
DateTime = "20040428160005.140000+000";
MachineName = "EMSPC329";
PackageName = "EMS00012";
ProcessID = 748;
ProgramName = "Unattendent Update";
SiteCode = "EMS";
ThreadID = 1128;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "\\\\EMSPRDSMS1\\SMSPKGC$\\EMS00012\\";
};
]LOG]!><time="12:00:05.150+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="event.cpp:522">
<![LOG[Raised Program Started Event for Ad:EMS2001C, Package:EMS00012, Program: Unattendent Update]LOG]!><time="12:00:05.170+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:301">
<![LOG[Program exit code 1603]LOG]!><time="12:00:05.541+240" date="04-28-2004" component="execmgr" context="" type="1" thread="272" file="scriptexecution.cpp:354">
<![LOG[Looking for MIF file to get program status]LOG]!><time="12:00:05.541+240" date="04-28-2004" component="execmgr" context="" type="1" thread="272" file="executionstatus.cpp:276">
<![LOG[Script for Package:EMS00012, Program: Unattendent Update failed with exit code 1603]LOG]!><time="12:00:05.541+240" date="04-28-2004" component="execmgr" context="" type="3" thread="272" file="executionstatus.cpp:243">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramErrorEvent
{
AdvertisementId = "EMS2001C";
ClientID = "GUID:2BFE58A7-A342-4392-B4E8-997862F7E046";
DateTime = "20040428160005.551000+000";
ExitCode = "1603";
MachineName = "EMSPC329";
PackageName = "EMS00012";
ProcessID = 748;
ProgramName = "Unattendent Update";
SiteCode = "EMS";
ThreadID = 272;
UserContext = "NT AUTHORITY\\SYSTEM";
};
]LOG]!><time="12:00:05.561+240" date="04-28-2004" component="execmgr" context="" type="1" thread="272" file="event.cpp:522">
<![LOG[Raised Program Error Event for Ad:EMS2001C, Package:EMS00012, Program: Unattendent Update]LOG]!><time="12:00:05.571+240" date="04-28-2004" component="execmgr" context="" type="1" thread="272" file="executioncontext.cpp:379">
<![LOG[Execution is complete for program Unattendent Update. The exit code is 1603, the execution status is FailureNonRetry]LOG]!><time="12:00:05.721+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1052" file="execreqmgr.cpp:3127">
====================END DETAIL ============================
 
Found it!!

Microsoft issued (but has since removed from public view effective 7/17/2003) the following patch: Q325804

This hot-fix effects:
Windows 2000 Profession SP3 or before.
Windows XP Professional with no service pack.

You need to run the Q325804 patch to fix a problem with access rights for the logonuser properties. AFTER this patch is installed you can package and run via SMS 2003 - SP4 for Windows 2000 and SP1 for Windows XP.

The hot fix can be located on the SMS 2003 CD-ROM under the directory WINQFE.

NOTE: This "fix" is included as part of Windows 2000 SP4 and above; Windows XP SP1 and above. So if you have these service packs already installed on the client PC, then this problem will already be fixed.
 
Did this solve your problem? I am having the same issues with SP4. I installed the patch and I still get the same errors...

Thanks
Gavin...
 
Just to clarify...
You are having problems installing SP4 on Windows 2000 Professional on a PC with Advanced Client using a package created under SMS 2003.

First question...
Have you been able to create a package (other than using SP4) and install it on a PC with SMS 2003 Advanced Client?

Second question...
More details - define what you mean by "some issues" - error messages on client desktop, error messages in SMS log files on client PC, error messages on SMS 2003 server.

 
Yes I have been able to push out other apps, I get the same errors in SMS Status Messages that you did when pushing out SP4.

The program for advertisement "STG2004C" failed ("STG00016" - "Windows 2000 - Service Pack 4 / Silent"). A failure exit code of 1603 was returned.
User context: NT AUTHORITY\SYSTEM

Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1603 is considered a failure.
Solution: For more information on the exit code, refer to the documentation for the program you are distributing.

Thanks
Gavin...
 
Have you manually tested the command line in your Program? I created the Package and Program manually (did not use package from defition) with a command line of
i386\update\update.exe -u -o -q -z for a quite, unattended install with reboot.
Jeff
 
I recreated the package manually and still got the same error. Guess I will have to use AD and a GPO for this update.

Thanks
Gavin...
 
I too am getting very desperate here!!
I have to distribute Share Point Client to all pc's on our network. I have a success rate of 1 in 5. Why is this??

The exact same package can download to some but not the other. The error message is the same "non-zero exit code of 1603"
Any ideas pleeeaassee...
 
I have exactly the same error message on this, so I tried ommiting the switches from the command line (the -u -q). I wanted to do it silently and in the background, but clearly it just failed on me! Hurrah!

So i omitted them and it's now stuck in running state. The ExecMgr.log file has got to

<![LOG[Raised Program Started Event for Ad:EMS2001C, Package:EMS00012, Program: Unattendent Update]LOG]!><time="12:00:05.170+240" date="04-28-2004" component="execmgr" context="" type="1" thread="1128" file="executioncontext.cpp:301">

...but rather than fail a few milliseconds later with 1603 error, it's now stuck there. It's not doing anything and hopefully it will, but i've had this twice now, so it doesn't seem to be happy with the switches used or the way they are inputted.

I'm still watiing for this thing to kick into gear, but i thought i'd share my findings. :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top