Msi Error Code 259
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a program exit code 259 sccm 2012 question Quick access Forums home Browse forums execution is complete for program the exit code is 259 users FAQ Search related threads Remove From My Forums Answered
Exit Code Failure
by: Program exit code 259 in SCCM Cllient System Center Configuration Manager > Configuration Manager 2007
Sccm Exit Codes
General Question 0 Sign in to vote 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 the thread has exited with code 259 (0x103) System Recovery v8.5.3.314-0 state change from Running to NotifyExecution execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)Checking content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.System for use execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)Successfully selected content location C:\WINDOWS\system32\CCM\Cache\C010194B.1.System execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)Executing program as a script execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\C010194B.1.System\loader.EXE" /s CM_DSLID=002FDA execmgr 8/26/2009 1:09:52 AM 448 (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\ execmgr 8/26/2009 1:09:52 AM 448 (0x01C0)Created Process for the passed command line execmgr 8/26/2009 1:09:52 AM 448 (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\\
Favorite Rating: Error 259 deploying Install MSI
Thread Exit Code 259
actionThis document (7002874) is provided subject to the disclaimer return code at the end of this document. Environment Novell ZENworks 10 Configuration Management with Support getexitcodeprocess Pack 1 - 10.1 Situation Install MSI action generates error 259:Error installing Pro11.MSI. MsiExec returned error code: 259.WindowsActions.MSI_ERR_UNKNOWNThere was an error that occurred https://social.technet.microsoft.com/Forums/systemcenter/en-US/fbccc114-3605-4363-b983-b2f7b02fe266/program-exit-code-259-in-sccm-cllient?forum=configmgrgeneral during an action for bundle bundleName. Would you like to automatically verify this bundle and attempt the action again? Resolution This is fixed in version 10.2 - see TID 7003225 "ZENworks 10 Configuration Management with SP2 (10.2)" which can be found at https://www.novell.com/support Additional Information This happens http://www.novell.com/support/kb/doc.php?id=7002874 especially for MSI installs that take over a minute to complete as they have a large number of associated files, or are run from Network share etc. The 259 means that the install process is still running, and ZEN bundle manager should not generate an erroras nofailure has occurred. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7002874Creation Date:31-MAR-09Modified Date:30-APR-12NovellZENworks Configuration Management Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
Français Deutsch 日本語 Español Help Video Screencast Help Windows System Error Codes (exit codes) Description Created: 28 Jan 2009 • Updated: 20 Dec 2010 | 9 comments Language TranslationsMachine TranslationsDeutsch http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description Français Español 简体中文 日本語 Sidd +19 19 Votes Login to vote Tweet Application installation (legacy setup applications or Windows installer applications) sometimes fails without any error message. These tasks will http://sdwright.blogspot.com/2012/05/sccm-package-returning-error-259-how-to.html return exit/error codes when log file is generated. The following script will help in getting the Exit/Error code of Application installation else on can get it from log file. Dim exit code oShell, MyApp, i Set oShell = CreateObject("WScript.Shell") MyApp = """C:\MyApplication\Setup.exe"" /Q" i = 0 i = oShell.Run(MyApp, 1 ,True) WScript.Echo "Exit Code is: " & (i) Set oShell = Nothing Note: Use Silent switches according to the application. The table below describes system Exit/Error codes when a task is executed. The description of codes may help in identifying and troublshooting the exit code 259 issues. Code Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 There are no more files. 19 The media is write protected. 20 The system cannot find the device specified. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command b
returning error 259 in the CAS logs on clients. After investigations it was found that setup.exe was executing then spawning other processes while the setup thread was killed. Hence the agent was misreporting the install even though it was eventually successful. This is a small script I wrote to be executed via the program in the package for installs such as this. You must change the: -strLogLoc (To the actual msi installer log to be monitored) -cMD (To the actual installer command line) -The if InStr check for the text in the log that is displayed with the main thread exit code(should be right at the end of the log) in this instance for AutoDesk I have used "]: MainEngineThread is returning" when it parses this line and grabs the "last" character of the line(the error code in this instance) Don't attempt to modify the script other than this if you are not sure what you are doing, however feel free to ask a question and I shall reply when I have time. Hope this helps people google tells me alot of people have not been able to resolve this. Sean On Error Resume Next Set objFSO = CreateObject("Scripting.FileSystemObject") Set objShell = WScript.CreateObject("WScript.Shell") strCmd = objShell.ExpandEnvironmentStrings("%comspec%") strScriptPath = objFSO.GetParentFolderName(wscript.ScriptFullName) strLogLoc = "c:\Windows\Temp\Autodesk Revit Architecture 2012 Install (en-us).log" 'wscript.echo strScriptPath If not right(strScriptPath,1) = "\" Then strScriptPath = strScriptPath & "\" End If 'wscript.echo strScriptPath cMD = strCmd & " /c " & strScriptPath & "\Image\Setup.exe /qb /I Image\AutoDeskRevit_20.12_86a.ini" 'wscript.echo strCmd 'wscript.echo cMD 'Return = objShell.Run(cMD,0,False) 'Loop to wait for the log to be created to we check to see when it is finished installing bLogExist = 1 While bLogExist = 1 If objFSO.FileExists(strLogLoc) Then wscript.echo "log exists" bLogExist = 0 Else wscript.echo "Waiting for log" ' do nothing just leave bool to 1 End if wscript.sleep 30000 'check every 30 seconds for the log file then once found continue Wend 'now check the loop in a loop to check when the MainEngine Thread is finished then return error code bLogCheck = 1 strMainEngineThreadCode = "" strErrorCode = 999 While