/build/static/layout/Breadcrumb_cap_w.png

Failure Exit Code 2: Snagit Uninstall

Simply can't figure this one out, please help if you can.

Purpose: Trying to uninstall SnagIt 7.x, uninstall SnagIt 8.x, install SnagIt 9.x
Using: SCCM 2007 with .CMD for uninstalls and .CMD for install of .msi with transform.
Package details: Three programs. 1st Install of SnagIt 9 with requirement to run another program first (Uninstall SnagIt 8 - Always run this program first); 2nd Uninstall of SnagIt 8 with requirement to run another program first (Uninstall SnagIt 7- Always run this program first); 3rd Uninstall of SnagIt 7

Problem: When advertisement is pushed to collection - SnagIt 7 is uninstalling fine, then SnagIt 8 uninstall fails with the following details:
  • Severity: Error - Message ID: 10006 - Description: The program for advertisement "XXX2005D" failed ("XXX0003B" - "Uninstall Old Program"). A failure exit code of 2 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 2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing.
This then stops the install queued for SnagIt 9. I have tried to figure out what the failure exit code of 2 is referring to but can't find any information from SnagIt documentation or online forums. The verbose log output for the SnagIt 8 uninstall is below. I don't know what the admin rights error is refering to as the SCCM account has full rights to the distribution source and over the computer. Plenty of space on the computer free (~25GB) and that install error doesn't make any sense. Please help.


DEBUG: Error 2769: Custom Action FixComponentConditions.DC957364_DE35_11D3_B46C_00600810A1CE did not close 1 MSIHANDLEs.
Internal Error 2769. FixComponentConditions.DC957364_DE35_11D3_B46C_00600810A1CE, 1
MSI (s) (1C:A8) [09:50:20:841]: Executing op: CustomActionSchedule(Action=TSC_RemoveAddin_PP,ActionType=1062,Source=On Error Resume Next
Property(S): ErrorDialog = ErrorDialog
Property(S): WiseInitAdminError = You must have administrator rights to run this installation. Please login as an administrator and re-run this installation.
Property(S): WiseInitSpaceError = Could not create temporary file, not enough free temporary disk space. Please free up disk space and rerun this installation.
Property(S): WiseInitExistError = %s Version %s is already installed. You must uninstall the existing version before installing %s Version %s. Do you want to uninstall the existing version of %s?


If you require the full log please let me know. Thanks.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 14 years ago
Red Belt
2
Exit code 2 is an old DOS error - File not found. All you need to find out now is which file! ProcMon will come in handy for that but you'll obviously need to use that locally, rather than via SCCM.

It's always handy to remember the common DOS errors: 2 - File not found, 3 - Path not found, 5 - Access denied and so on.
Posted by: Jsaylor 14 years ago
Second Degree Blue Belt
1
Are you checking whether the application is installed or not before attempting to run the uninstall? If you run a typical uninstall command line through SMS and rely on the exit code for your success/failure criteria, then any msiexec.exe /x command run on a product that doesn't exist will return an error, which in turn stops any further chained programs from running.

If you don't have any version checking before attempting to uninstall, you might think about looking into the uninstall keys located at HKLM\software\microsoft\windows\currentversion\uninstall .
Posted by: RKD 14 years ago
Yellow Belt
0
Thanks VBScab and Jsaylor.

Turns out the third line of my .CMD [rmdir /s /q "C:\Documents and Settings\All Users\Start Menu\Programs\SnagIt 8"] which I had put in as a mirror of what I had to do with the SnagIt 7 uninstall was running before/during the second line [MsiExec.exe /qn /x {DA0BF7AB-88EB-4675-8FA1-531EAD938821} /norestart /l C:\Snagit8Uninstall.log] which was removing files that the uninstall was looking to clean up and subsequently not finding. Thanks procmon and Mark's Blog on Sharing Violations.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ