Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Altiris Exit codes - 1605 and 1642

Created: 28 Mar 2013 | 7 comments

Hi there,

 

I often encountered these Altriis Exit codes but not quite sure what are the causes? Please help if you crossed these.

 

1605 This action is only valid for products that are currently installed.

 

1642 The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

 

Thank you,

Charlie. 

Operating Systems:

Comments 7 CommentsJump to latest comment

andykn101's picture

These are not Altiris error messages but Windows Installer (msiexec) error messges:

http://msdn.microsoft.com/en-gb/library/windows/desktop/aa372835(v=vs.85).aspx

It looks like you are trying to install a Windows Installer Patch package (msp) when the original product that the patch is supposed to update isn't installed.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Joshua Rasmussen's picture

Hello Charlie,

     The Exit Codes: 1605 & 1642 are generally related to the update not being applicable, and a problem may exist in regards to how the IsApplicable Rule is targeting via Patch Management.

     You may search the individual update KB on the Knowledge Management site to see if that update is already being reviewed for a possible rules issue. Input the KB number and in the 2nd search field; input the Product: Patch Management Solution for Windows. Or let me know the update name and I will see what I can find.

     Otherwise, you will want to contact support and have them gather the necessary data for troubleshooting rules as detailed on KM: HOWTO60789. The Patch Development Team can then review how the IsApplicable rule is targeting and modify as needed.

Thank you,

Joshua

Charlie D Tran's picture

Thanks very much, Joshua. I would think to open a case to tech support for a review on IsApplicable rules.

Thanks again so much, Joshua

Charlie.

Joshua Rasmussen's picture

Sounds good.

If you'd like; drop the precise update names (example: windowsxp-kb123456-enu.exe) here and I will be happy to research to see if we have any known issues.

Thank you,

Joshua

Charlie D Tran's picture

Sure, please help, Joshua.

 

NDP20SP2-KB2789643-x86.exe
NDP40-KB2789642-x86.exe

 

Thanks very much,

Charlie.

 

 

Joshua Rasmussen's picture

Thank you for the info Charlie, for usually I am able to find something if a rules issue is present; however, I have found no evidence that there are any open known issues regarding the rules for this bulletin.

Further research for NDP20SP2-KB2789643-x86.exe & NDP40-KB2789642-x86.exe; found both are bundled in MS13-015. This bulletin was released on 2/12/13 with no revisions, nor was it superseded, since then. Often this will cause a mock-rules issue if the PMImport is not configured to clean up Revised or Superseded updates.

Moving forward: please proceed with opening a separate case for each update to be reviewed by the Patch Management Support Team for a possible change in the IsApplicable Rule data.

Thank you again,

Joshua