Answers

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.

********************** 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.

All replies

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).

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.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

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.

********************** 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.

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.

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...((

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.