Program exit code 259 in SCCM Cllient
Hi,
I am getting Error "Program exit code 259" in Execmgr.log while installing symantec backup tool on sccm client.

Execmgr.log:

Execution Request for package C010194B program Symantec Backup Exec System Recovery v8.5.3.314-0 state change from Running to NotifyExecutionexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Checking content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.System for useexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.Systemexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Executing program as a scriptexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\loader.EXE" /s CM_DSLID=002FDAexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Command line = "C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\loader.EXE" /s CM_DSLID=002FDA, Working Directory = C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\execmgr8/26/2009 1:09:52 AM448 (0x01C0)
Created Process for the passed command lineexecmgr8/26/2009 1:09:52 AM448 (0x01C0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "N0120AAD";
ClientID = "GUID:C7E780C0-72FE-4876-B3B3-ACC7E7AB5D71";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\C010194B.1.System\\loader.EXE\" /s CM_DSLID=002FDA";
DateTime = "20090826050952.320000+000";
MachineName = "WFSLUSLVA8DYW";
PackageName = "C010194B";
ProcessID = 3876;
ProgramName = "Symantec Backup Exec System Recovery v8.5.3.314-0";
SiteCode = "N02";
ThreadID = 448;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\C010194B.1.System\\";
};
execmgr8/26/2009 1:09:52 AM448 (0x01C0)
Raised Program Started Event for Ad:N0120AAD, Package:C010194B, Program: Symantec Backup Exec System Recovery v8.5.3.314-0execmgr8/26/2009 1:09:52 AM448 (0x01C0)
Execution Manager timer has been fired.execmgr8/26/2009 1:12:03 AM2228 (0x08B4)
Program exit code 259execmgr8/26/2009 2:09:52 AM5392 (0x1510)
September 5th, 2009 3:44am

We saw this while trying (and failing) to get an AutoCAD 2009 installation with SCCM R2 working. We opened a case with MS Premier and were told that "259 is not a "normal" exit code and was being produced (in AutoCAD's install) by a initial install process that spawned off other processes". It seems that there was code that started other things installing (which actually finished correctly), but, when the initial code exited, it gave off the 259 and SCCM took that as a failure and ceased to do anything further.

We could do nothing on the SCCM side, sent the info back up to AutoDesk, who made some partial corrections in the 2010 versions (still don't install right, with SCCM).
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2009 1:23pm

Hi,

Thanks for your reply!!!!!!!!!

But this package has been successfully installed on more than 90% machines so then how can be problem with software package.

Thank You,
Mahinder Chandel

September 5th, 2009 2:36pm


Quote: "But this package has been successfully installed on more than 90% machines so then how can be problem with software package.
"

Because 259 is an exit code from the software package, not ConfigMgr.

All ConfigMgr is doing is kicking off the command-line that you give it in the program. After that, it's up to whatever is launched to do its work. Thus 259 is a code from your executable and really is up to the vendor of that program to tell you what it means.

Just because it works most of the time doesn't mean it will work all of the time. There is some difference in the systems where it is failing.

If 259 is a Win32 error code it means "No more data is available". JUst because a program returns an error code though doesn't mean it is a Win32 error code and so this could be a vendor specific code.

Check appdeploy.com for others who may have tried to install this app and any feedback. Enable verbose logging on the program -- not ConfigMgr as it's not ConfigMgr having the issue, it's the program -- and review the log.

One thing to always keep in mind also is that if you are running the program using admin credentials, it is actually running under the local system account. In the vast majority of cases, this has no negative effect; however, there are some poorly written installers out there that make some bad assumptions about the context of where it should run and this ends up causing weird, sometimes sporadic problems.
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2009 2:48pm

Yep, as Jason said, it's not SCCM (actually...Microsoft may want to consider making 259 an "acceptable" code,like 3010 "successful, but needs reboot", so 259 could be "spawned process--check for completion", or...put out a message to vendors on how PROPERLY to write code that spawns things) that's at fault.

Using a task sequence command line, you might could just add in 259 as a "success" code?

In AutoCAD 2009's case, the install WOULD finish, successfully, but, SCCM had already given up, and, reported it as an error.

Here's our incident info, and, you might want to forward to Symantec, as, ultimately...THEY have to fix it...

CASE_ID_NUM: SRZ081104000346

MESSAGE:

********************** The message for you follows ************************ Hello Bill,

After looking over the logs you send I can see the problem. SCCM is starting the setup.exe with the command line options you specified. However the program is exiting within 20 seconds with a code 259. SCCM is interpreting this as a failure. To get SCCM to recognize that the application is installed correctly it should exit with a code 0. This is further complicated by setup.exe spawning multiple other processes and exiting before the processes it spawned are finished. This makes it impossible for SCCM to correctly tell if the application was installed correctly or reboot the system when it is done because SCCM has no way to monitor those processes.

To correct this the setup.exe should stay loaded and monitor all of the other processes it spawned then if they complete successfully return a code 0. You may be able to workaround this issue by wrapping the setup in some kind of script that will monitor the setup processes and exit properly when they are completed. The help file you sent does have a sample script that may be able to do this.

Please let me know if you have any other questions.

<![LOG[Command line = "\\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\setup.exe" /i r1a2k9.ini, Working Directory = \\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\]LOG]!><time="12:20:09.861+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:284">

<![LOG[Created Process for the passed command line]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:407">

<![LOG[Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramStartedEvent

{

AdvertisementId = "ECH20090";

ClientID = "GUID:FFAF7676-D841-4623-A88C-1DB8DCD40AEC";

CommandLine = "\"\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\setup.exe\" /i r1a2k9.ini";

DateTime = "20081105192010.470000+000";

MachineName = "ECH-WS46150";

PackageName = "ECH00074";

ProcessID = 496;

ProgramName = "AutoCAD 2009 Silent Install";

SiteCode = "ECH";

ThreadID = 1908;

UserContext = "NT AUTHORITY\\SYSTEM";

WorkingDirectory = "\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\";

};

]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="event.cpp:525">

<![LOG[Raised Program Started Event for Ad:ECH20090, Package:ECH00074, Program: AutoCAD 2009 Silent Install]LOG]!><time="12:20:10.486+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="executioncontext.cpp:523">

<![LOG[Program exit code 259]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="scriptexecution.cpp:547">

<![LOG[Looking for MIF file to get program status]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:282">

<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:232">

September 5th, 2009 3:04pm

Yep, as Jason said, it's not SCCM (actually...Microsoft may want to consider making 259 an "acceptable" code,like 3010 "successful, but needs reboot", so 259 could be "spawned process--check for completion", or...put out a message to vendors on how PROPERLY to write code that spawns things) that's at fault.

Using a task sequence command line, you might could just add in 259 as a "success" code?

In AutoCAD 2009's case, the install WOULD finish, successfully, but, SCCM had already given up, and, reported it as an error.

Here's our incident info, and, you might want to forward to Symantec, as, ultimately...THEY have to fix it...

CASE_ID_NUM: SRZ081104000346

MESSAGE:

********************** The message for you follows ************************ Hello Bill,

After looking over the logs you send I can see the problem. SCCM is starting the setup.exe with the command line options you specified. However the program is exiting within 20 seconds with a code 259. SCCM is interpreting this as a failure. To get SCCM to recognize that the application is installed correctly it should exit with a code 0. This is further complicated by setup.exe spawning multiple other processes and exiting before the processes it spawned are finished. This makes it impossible for SCCM to correctly tell if the application was installed correctly or reboot the system when it is done because SCCM has no way to monitor those processes.

To correct this the setup.exe should stay loaded and monitor all of the other processes it spawned then if they complete successfully return a code 0. You may be able to workaround this issue by wrapping the setup in some kind of script that will monitor the setup processes and exit properly when they are completed. The help file you sent does have a sample script that may be able to do this.

Please let me know if you have any other questions.

<![LOG[Command line = "\\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\setup.exe" /i r1a2k9.ini, Working Directory = \\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\]LOG]!><time="12:20:09.861+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:284">

<![LOG[Created Process for the passed command line]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:407">

<![LOG[Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramStartedEvent

{

AdvertisementId = "ECH20090";

ClientID = "GUID:FFAF7676-D841-4623-A88C-1DB8DCD40AEC";

CommandLine = "\"\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\setup.exe\" /i r1a2k9.ini";

DateTime = "20081105192010.470000+000";

MachineName = "ECH-WS46150";

PackageName = "ECH00074";

ProcessID = 496;

ProgramName = "AutoCAD 2009 Silent Install";

SiteCode = "ECH";

ThreadID = 1908;

UserContext = "NT AUTHORITY\\SYSTEM";

WorkingDirectory = "\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\";

};

]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="event.cpp:525">

<![LOG[Raised Program Started Event for Ad:ECH20090, Package:ECH00074, Program: AutoCAD 2009 Silent Install]LOG]!><time="12:20:10.486+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="executioncontext.cpp:523">

<![LOG[Program exit code 259]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="scriptexecution.cpp:547">

<![LOG[Looking for MIF file to get program status]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:282">

<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:232">

Free Windows Admin Tool Kit Click here and download it now
September 5th, 2009 3:04pm

Yep, as Jason said, it's not SCCM (actually...Microsoft may want to consider making 259 an "acceptable" code,like 3010 "successful, but needs reboot", so 259 could be "spawned process--check for completion", or...put out a message to vendors on how PROPERLY to write code that spawns things) that's at fault.

Using a task sequence command line, you might could just add in 259 as a "success" code?

In AutoCAD 2009's case, the install WOULD finish, successfully, but, SCCM had already given up, and, reported it as an error.

Here's our incident info, and, you might want to forward to Symantec, as, ultimately...THEY have to fix it...

CASE_ID_NUM: SRZ081104000346

MESSAGE:

********************** The message for you follows ************************ Hello Bill,

After looking over the logs you send I can see the problem. SCCM is starting the setup.exe with the command line options you specified. However the program is exiting within 20 seconds with a code 259. SCCM is interpreting this as a failure. To get SCCM to recognize that the application is installed correctly it should exit with a code 0. This is further complicated by setup.exe spawning multiple other processes and exiting before the processes it spawned are finished. This makes it impossible for SCCM to correctly tell if the application was installed correctly or reboot the system when it is done because SCCM has no way to monitor those processes.

To correct this the setup.exe should stay loaded and monitor all of the other processes it spawned then if they complete successfully return a code 0. You may be able to workaround this issue by wrapping the setup in some kind of script that will monitor the setup processes and exit properly when they are completed. The help file you sent does have a sample script that may be able to do this.

Please let me know if you have any other questions.

<![LOG[Command line = "\\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\setup.exe" /i r1a2k9.ini, Working Directory = \\VHAECHSMS1.v19.med.va.gov\SMSPKGG$\ECH00074\]LOG]!><time="12:20:09.861+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:284">

<![LOG[Created Process for the passed command line]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="scriptexecution.cpp:407">

<![LOG[Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramStartedEvent

{

AdvertisementId = "ECH20090";

ClientID = "GUID:FFAF7676-D841-4623-A88C-1DB8DCD40AEC";

CommandLine = "\"\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\setup.exe\" /i r1a2k9.ini";

DateTime = "20081105192010.470000+000";

MachineName = "ECH-WS46150";

PackageName = "ECH00074";

ProcessID = 496;

ProgramName = "AutoCAD 2009 Silent Install";

SiteCode = "ECH";

ThreadID = 1908;

UserContext = "NT AUTHORITY\\SYSTEM";

WorkingDirectory = "\\\\VHAECHSMS1.v19.med.va.gov\\SMSPKGG$\\ECH00074\\";

};

]LOG]!><time="12:20:10.470+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="event.cpp:525">

<![LOG[Raised Program Started Event for Ad:ECH20090, Package:ECH00074, Program: AutoCAD 2009 Silent Install]LOG]!><time="12:20:10.486+420" date="11-05-2008" component="execmgr" context="" type="1" thread="1908" file="executioncontext.cpp:523">

<![LOG[Program exit code 259]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="scriptexecution.cpp:547">

<![LOG[Looking for MIF file to get program status]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:282">

<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time="12:20:40.532+420" date="11-05-2008" component="execmgr" context="" type="1" thread="2492" file="executionstatus.cpp:232">

September 5th, 2009 3:04pm

Hi.
i have some error -Error "Program exit code 259", when i try instalation Office 2007 enterprise. Help me, please...
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2009 4:14am

Is just quote Jason here: "... 259 is an exit code from the software package, not ConfigMgr."
So you should have a look at installation logfiles to see what went wrong.
October 14th, 2009 6:31am

<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="16:09:34.651+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1312">
<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="16:09:34.827+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1312">
<![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="16:09:34.842+000" date="10-13-2009" component="execmgr" context="" type="3" thread="3120" file="softdistpolicy.cpp:1413">
<![LOG[Software distribution agent was enabled]LOG]!><time="16:11:48.870+000" date="10-13-2009" component="execmgr" context="" type="1" thread="3804" file="execreqmgr.cpp:5969">
<![LOG[Policy arrived for parent package QQQ00009 program RAR]LOG]!><time="04:19:00.850+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="execreqmgr.cpp:6451">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramOfferReceivedEvent
{
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221900.962000+000";
    MachineName = "SCOM";
    ProcessID = 2824;
    SiteCode = "QQQ";
    ThreadID = 3668;
};
]LOG]!><time="04:19:00.976+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="event.cpp:525">
<![LOG[Policy arrived for parent package QQQ0000E program Setup]LOG]!><time="04:19:01.005+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="execreqmgr.cpp:6451">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramOfferReceivedEvent
{
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221901.016000+000";
    MachineName = "SCOM";
    ProcessID = 2824;
    SiteCode = "QQQ";
    ThreadID = 3668;
};
]LOG]!><time="04:19:01.017+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3668" file="event.cpp:525">
<![LOG[Requesting content from CAS for package QQQ00009 version 1]LOG]!><time="04:19:02.678+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="contentaccesshelper.cpp:138">
<![LOG[Successfully created a content request handle {E493064B-D93A-4FD2-83FF-886B4325A796} for the package QQQ00009 version 1]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="contentaccesshelper.cpp:216">
<![LOG[Program RAR change to state STATE_ADVANCED_DOWNLOAD content in progress]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1168" file="executionrequest.cpp:3670">
<![LOG[Execution Request for package QQQ00009 program RAR state change from NotExist to AdvancedDownload]LOG]!><time="04:19:03.315+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1168" file="executionrequest.cpp:488">
<![LOG[Mandatory execution requested for program RAR and advertisement QQQ20008]LOG]!><time="04:19:03.344+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert QQQ20008, program RAR, package QQQ00009]LOG]!><time="04:19:03.357+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="execreqmgr.cpp:3440">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistWaitingContentEvent
{
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221903.978000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    PackageVersion = "1";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 2964;
};
]LOG]!><time="04:19:03.983+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="event.cpp:525">
<![LOG[Successfully raised SoftDistWaitingContentEvent event for program RAR]LOG]!><time="04:19:03.985+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="executionrequest.cpp:2623">
<![LOG[Execution Request for package QQQ00009 program RAR state change from WaitingDependency to WaitingContent]LOG]!><time="04:19:03.985+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2964" file="executionrequest.cpp:488">
<![LOG[Requesting content from CAS for package QQQ0000E version 1]LOG]!><time="04:19:04.328+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="contentaccesshelper.cpp:138">
<![LOG[Successfully created a content request handle {1AEB98AA-58BE-428F-883A-936448A7AC88} for the package QQQ0000E version 1]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="contentaccesshelper.cpp:216">
<![LOG[Program Setup change to state STATE_ADVANCED_DOWNLOAD content in progress]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1280" file="executionrequest.cpp:3670">
<![LOG[Execution Request for package QQQ0000E program Setup state change from NotExist to AdvancedDownload]LOG]!><time="04:19:04.451+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="executionrequest.cpp:488">
<![LOG[Mandatory execution requested for program Setup and advertisement QQQ20011]LOG]!><time="04:19:04.483+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="execreqmgr.cpp:3317">
<![LOG[Creating mandatory request for advert QQQ20011, program Setup, package QQQ0000E]LOG]!><time="04:19:04.534+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="execreqmgr.cpp:3440">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistWaitingContentEvent
{
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013221904.861000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    PackageVersion = "1";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 3460;
};
]LOG]!><time="04:19:04.871+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="event.cpp:525">
<![LOG[Successfully raised SoftDistWaitingContentEvent event for program Setup]LOG]!><time="04:19:04.877+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:2623">
<![LOG[Execution Request for package QQQ0000E program Setup state change from WaitingDependency to WaitingContent]LOG]!><time="04:19:04.877+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:488">
<![LOG[Content is available for program RAR.]LOG]!><time="04:19:08.813+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:4915">
<![LOG[CExecutionRequest::Service Windows Manager has allowed us to run.]LOG]!><time="04:19:08.859+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:3071">
<![LOG[Execution Request for package QQQ00009 program RAR state change from WaitingContent to NotifyExecution]LOG]!><time="04:19:08.859+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:488">
<![LOG[Notify user mandatory program RAR is about to run]LOG]!><time="04:19:08.893+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3460" file="executionrequest.cpp:3112">
<![LOG[Content is available for program Setup.]LOG]!><time="04:22:59.476+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:4915">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramWaitingForAnotherProgram
{
    AdvertisementId = "QQQ20011";
    BlockingPackageID = "QQQ00009";
    BlockingProgramName = "RAR";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013222259.546000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 864;
};
]LOG]!><time="04:22:59.551+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="event.cpp:525">
<![LOG[Successfully raised SoftDistProgramWaitingForAnotherProgram event for program Setup.]LOG]!><time="04:22:59.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:2899">
<![LOG[Execution Request for package QQQ0000E program Setup state change from WaitingContent to Ready]LOG]!><time="04:22:59.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="864" file="executionrequest.cpp:488">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:24:08.940+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="execreqmgr.cpp:5188">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:24:08.993+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="execreqmgr.cpp:5188">
<![LOG[Executing program "wrar380ru.exe" /s in Admin context]LOG]!><time="04:24:09.038+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionrequest.cpp:3277">
<![LOG[Execution Request for package QQQ00009 program RAR state change from Running to NotifyExecution]LOG]!><time="04:24:09.085+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionrequest.cpp:488">
<![LOG[Checking content location C:\Windows\system32\CCM\Cache\QQQ00009.1.System for use]LOG]!><time="04:24:09.172+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:1635">
<![LOG[Successfully selected content location C:\Windows\system32\CCM\Cache\QQQ00009.1.System]LOG]!><time="04:24:09.173+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:1703">
<![LOG[GetFileVersionInfoSize failed for file C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe, error 1813]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="2" thread="1788" file="executioncontext.cpp:119">
<![LOG[Executing program as a script]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executionengine.cpp:103">
<![LOG[Successfully prepared command line "C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe" /s]LOG]!><time="04:24:09.205+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:523">
<![LOG[Command line = "C:\Windows\system32\CCM\Cache\QQQ00009.1.System\wrar380ru.exe" /s, Working Directory = C:\Windows\system32\CCM\Cache\QQQ00009.1.System\]LOG]!><time="04:24:09.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:284">
<![LOG[Created Process for the passed command line]LOG]!><time="04:24:09.300+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="scriptexecution.cpp:407">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramStartedEvent
{
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    CommandLine = "\"C:\\Windows\\system32\\CCM\\Cache\\QQQ00009.1.System\\wrar380ru.exe\" /s";
    DateTime = "20091013222409.308000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 1788;
    UserContext = "NT AUTHORITY\\SYSTEM";
    WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\QQQ00009.1.System\\";
};
]LOG]!><time="04:24:09.318+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="event.cpp:525">
<![LOG[Raised Program Started Event for Ad:QQQ20008, Package:QQQ00009, Program: RAR]LOG]!><time="04:24:09.321+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1788" file="executioncontext.cpp:523">
<![LOG[Program exit code 0]LOG]!><time="04:24:12.399+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="scriptexecution.cpp:547">
<![LOG[Looking for MIF file to get program status]LOG]!><time="04:24:12.399+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionstatus.cpp:282">
<![LOG[Script for  Package:QQQ00009, Program: RAR succeeded with exit code 0]LOG]!><time="04:24:12.401+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionstatus.cpp:259">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramCompletedSuccessfullyEvent
{
    AdvertisementId = "QQQ20008";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091013222412.410000+000";
    MachineName = "SCOM";
    PackageName = "QQQ00009";
    ProcessID = 2824;
    ProgramName = "RAR";
    SiteCode = "QQQ";
    ThreadID = 3564;
    UserContext = "NT AUTHORITY\\SYSTEM";
};
]LOG]!><time="04:24:12.415+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="event.cpp:525">
<![LOG[Raised Program Success Event for Ad:QQQ20008, Package:QQQ00009, Program: RAR]LOG]!><time="04:24:12.419+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executioncontext.cpp:551">
<![LOG[Execution is complete for program RAR. The exit code is 0, the execution status is Success]LOG]!><time="04:24:12.419+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="execreqmgr.cpp:3908">
<![LOG[CExecutionRequest::Service Windows Manager has allowed us to run.]LOG]!><time="04:24:12.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:3071">
<![LOG[Execution Request for package QQQ0000E program Setup state change from Ready to NotifyExecution]LOG]!><time="04:24:12.554+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:488">
<![LOG[Notify user mandatory program Setup is about to run]LOG]!><time="04:24:12.558+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3564" file="executionrequest.cpp:3112">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:26:19.903+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3820" file="execreqmgr.cpp:5188">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:29:12.150+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3840" file="execreqmgr.cpp:5188">
<![LOG[Executing program Setup.exe in Admin context]LOG]!><time="04:29:12.161+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionrequest.cpp:3277">
<![LOG[Execution Request for package QQQ0000E program Setup state change from Running to NotifyExecution]LOG]!><time="04:29:12.173+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionrequest.cpp:488">
<![LOG[Checking content location C:\Windows\system32\CCM\Cache\QQQ0000E.1.System for use]LOG]!><time="04:29:12.196+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:1635">
<![LOG[Successfully selected content location C:\Windows\system32\CCM\Cache\QQQ0000E.1.System]LOG]!><time="04:29:12.196+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:1703">
<![LOG[Executing program as a script]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executionengine.cpp:103">
<![LOG[Successfully prepared command line "C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\setup.exe"]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:523">
<![LOG[Command line = "C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\setup.exe", Working Directory = C:\Windows\system32\CCM\Cache\QQQ0000E.1.System\]LOG]!><time="04:29:12.200+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:284">
<![LOG[Created Process for the passed command line]LOG]!><time="04:29:12.395+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="scriptexecution.cpp:407">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramStartedEvent
{
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    CommandLine = "\"C:\\Windows\\system32\\CCM\\Cache\\QQQ0000E.1.System\\setup.exe\"";
    DateTime = "20091013222912.413000+000";
    MachineName = "SCOM";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 1320;
    UserContext = "NT AUTHORITY\\SYSTEM";
    WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\QQQ0000E.1.System\\";
};
]LOG]!><time="04:29:12.423+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="event.cpp:525">
<![LOG[Raised Program Started Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="04:29:12.426+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1320" file="executioncontext.cpp:523">
<![LOG[Execution Manager timer has been fired.]LOG]!><time="04:33:31.003+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1280" file="execreqmgr.cpp:5188">
<![LOG[Program exit code 259]LOG]!><time="06:29:13.174+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="scriptexecution.cpp:547">
<![LOG[Looking for MIF file to get program status]LOG]!><time="06:29:13.178+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executionstatus.cpp:282">
<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time="06:29:13.184+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executionstatus.cpp:232">
<![LOG[Raising event:
[SMS_CodePage(866), SMS_LocaleID(1049)]
instance of SoftDistProgramExceededTime
{
    AdvertisementId = "QQQ20011";
    ClientID = "GUID:97CDFA0B-BE94-4B45-949F-546BFB130163";
    DateTime = "20091014002913.196000+000";
    MachineName = "SCOM";
    MaximumTime = "120";
    PackageName = "QQQ0000E";
    ProcessID = 2824;
    ProgramName = "Setup";
    SiteCode = "QQQ";
    ThreadID = 2788;
};
]LOG]!><time="06:29:13.204+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="event.cpp:525">
<![LOG[Raised Program Exceeded Time Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executioncontext.cpp:945">
<![LOG[Execution is complete for program Setup. The exit code is 259, the execution status is Unknown Status]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="execreqmgr.cpp:3908">
<![LOG[A user has logged on.]LOG]!><time="10:24:37.257+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3644" file="execreqmgr.cpp:4522">
<![LOG[The logged on user is WER\admin]LOG]!><time="10:24:37.595+000" date="10-14-2009" component="execmgr" context="" type="1" thread="3644" file="execreqmgr.cpp:4540">
<![LOG[A user has logged on.]LOG]!><time="15:55:34.833+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1708" file="execreqmgr.cpp:4522">
<![LOG[The logged on user is WER\admin]LOG]!><time="15:55:35.776+000" date="10-14-2009" component="execmgr" context="" type="1" thread="1708" file="execreqmgr.cpp:4540">
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2009 10:02am

<![LOG[Raised Program Exceeded Time Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executioncontext.cpp:945">
<![LOG[Execution is complete for program Setup. The exit code is 259, the execution status is Unknown Status]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="execreqmgr.cpp:3908">

ConfigMgr kicked off the installation but it did not finished within the configured period of time. Maybe there's a window  invisible to the end user waiting for input or something like that.
You should also have a look at the logfile that office itself generates.
October 14th, 2009 10:59am

<![LOG[Raised Program Exceeded Time Event for Ad:QQQ20011, Package:QQQ0000E, Program: Setup]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="executioncontext.cpp:945">
<![LOG[Execution is complete for program Setup. The exit code is 259 , the execution status is Unknown Status]LOG]!><time="06:29:13.206+000" date="10-14-2009" component="execmgr" context="" type="1" thread="2788" file="execreqmgr.cpp:3908">

ConfigMgr kicked off the installation but it did not finished within the configured period of time. Maybe there's a window  invisible to the end user waiting for input or something like that.
You should also have a look at the logfile that office itself generates.

Hmmm...its very very interesting, at all computers (40) itisnt this problem...((
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2009 11:52am

Has anyone tried adding the /SMS switch to the command.  This is an installshield parameter that tells setup to not return any return codes until the main task has completed?

Vince

October 14th, 2013 3:41pm

I am also getting Error "Program exit code 259" in Execmgr.log while deploying AutoCAD 2014.  Has anyone solved this issue? 

Regards, Tony

Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2014 9:58am

I am also getting Error "Program exit code 259" in Execmgr.log while deploying AutoCAD 2014.  Has anyone solved this issue? 

Regards, Tony

Hi All,

Even we had the same problem, AutoCAD with error 259.

We did find a workaround for it, make the program "ATTENDED". Few hughe application require user interaction for their proper installation.

I am not sure how many of you agree with this, but this a worked for me on many a machines.

I did check on the Autodesk Forum, there is no specific resolution for the 259 error.

By ATTENDED program i mean, user just has to interact once in running the advertisement from RAP after which the installtion carries on, no further interaction is required.

Do let me know if this works for someone else as well :-)

June 9th, 2014 6:08am

I have seen this SCCM Program Exit Code 259 accompanied by an error status: 1624 in the MSI install log. MSI log states:

DEBUG: Error 2759:  Transform C:\WINDOWS\Installer\1bf5a8.mst version 500 incompatible with engine; Min: 30, Max: 405.
1: 2759 2: C:\WINDOWS\Installer\1bf5a8.mst 3: 500 4: 30 5: 405
MSI (s) (B8:DC) [12:24:31:474]: Note: 1: 1708
MSI (s) (B8:DC) [12:24:31:489]: Product: xxxxxxxxxx -- Installation failed.
MSI (s) (B8:DC) [12:24:31:489]: Windows Installer installed the product. Product Name: xxxxxxxxxx. Product Version: xxxx.xxxx.xxxx.xxxx. Product Language: 1033. Installation success or error status: 1624.
MSI (s) (B8:DC) [12:24:31:489]: Attempting to delete file C:\WINDOWS\Installer\1bf5a8.mst
MSI (s) (B8:DC) [12:24:31:489]: MainEngineThread is returning 1624
..
Error applying transforms.  Verify that the specified transform paths are valid.
C:\WINDOWS\system32\CCM\Cache\SC10089E.8.S-1-5-21-1921803841-720794136-410060929-132402\xxxxxxxxxx.mst
...
MSI (c) (60:BC) [12:24:31:521]: MainEngineThread is returning 1624

In my case it was a malformed Transform (MST). Install target was XP 32-bit.

Free Windows Admin Tool Kit Click here and download it now
August 7th, 2014 12:48am

For anyone else that comes across 259 deploying Autocad.

http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/CloudHelp/cloudhelp/2015/ENU/Autodesk-NetworkAdmin/files/GUID-F9A14A04-FCA6-4ED8-B2E2-A495E3166B62-htm.html

I had the exact same issue.

You need to use the script provided by the image creation tool and you need to keep the original folder structure with the suite being in a sub folder.

Below is a screen shot of the folder structure created when you create a deployment image through the vendors tool.

You then need to make this location the source folder of the application / package.

The command line to use to install the application will be:

.\Img\Setup.exe /W /Q /I .\Img\autocad2015.ini /language en-us

If you change the folder structure it breaks the deployment, 

The /W prevents the initial stub part of the installer from closing, it remains open until the suite is fully installed and so prevents the 259 from occurring.

I have deployed 3 versions of the suite this way both as a package and application and it works perfectly.


  • Edited by -Richk- Friday, December 12, 2014 2:33 PM
December 12th, 2014 2:32pm

For anyone else that comes across 259 deploying Autocad.

http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/CloudHelp/cloudhelp/2015/ENU/Autodesk-NetworkAdmin/files/GUID-F9A14A04-FCA6-4ED8-B2E2-A495E3166B62-htm.html

I had the exact same issue.

You need to use the script provided by the image creation tool and you need to keep the original folder structure with the suite being in a sub folder.

Below is a screen shot of the folder structure created when you create a deployment image through the vendors tool.

You then need to make this location the source folder of the application / package.

The command line to use to install the application will be:

.\Img\Setup.exe /W /Q /I .\Img\autocad2015.ini /language en-us

If you change the folder structure it breaks the deployment, 

The /W prevents the initial stub part of the installer from closing, it remains open until the suite is fully installed and so prevents the 259 from occurring.

I have deployed 3 versions of the suite this way both as a package and application and it works perfectly.


  • Edited by -Richk- Friday, December 12, 2014 2:33 PM
Free Windows Admin Tool Kit Click here and download it now
December 12th, 2014 2:32pm

For anyone else that comes across 259 deploying Autocad.

http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/CloudHelp/cloudhelp/2015/ENU/Autodesk-NetworkAdmin/files/GUID-F9A14A04-FCA6-4ED8-B2E2-A495E3166B62-htm.html

I had the exact same issue.

You need to use the script provided by the image creation tool and you need to keep the original folder structure with the suite being in a sub folder.

Below is a screen shot of the folder structure created when you create a deployment image through the vendors tool.

You then need to make this location the source folder of the application / package.

The command line to use to install the application will be:

.\Img\Setup.exe /W /Q /I .\Img\autocad2015.ini /language en-us

If you change the folder structure it breaks the deployment, 

The /W prevents the initial stub part of the installer from closing, it remains open until the suite is fully installed and so prevents the 259 from occurring.

I have deployed 3 versions of the suite this way both as a package and application and it works perfectly.


  • Edited by -Richk- Friday, December 12, 2014 2:33 PM
December 12th, 2014 2:32pm

Richk-

I am struggling with Autodesk Maya 2015 package, command works manually in pstools 

I have setup root folder as Maya2015 and sub folders are same as you mensioned

Img, SMS_SCCM scripts and Tools

Command I am running is Img\Setup.exe /w /q /I Maya2015.ini /language en-us

if Maya2015.ini file is in same folder as setup.exe do I still have to specify it again /Img/Maya2015.ini?

Do I need . before Img and .\Img before Maya2015.ini file. 

As per my understanding if setup.exe and .ini files are in same folder it should work.

Need help, please advise.

Thanks

Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2015 9:36pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics