SUMMARY: Problem installing ECO T64KIT1001167-V51BB27-ES-20070321

Thanks to: Olle Eriksson, Dustin Marquess, Bill Glessner, HP Support

Conclusion is that the inventory within the patch is incorrect, and needs to be modified to change the dependency list.

HP have provided me with an updated patch which corrects the problem, and applies cleanly on PK4-PK5 upgraded systems.

Full summary details here:

-----Original Message-----
From: tru64-unix-managers-owner@xxxxxxxx
[mailto:tru64-unix-managers-owner@xxxxxxxx]On Behalf Of Iain Barker
Sent: Monday, 07 May, 2007 16:03
To: tru64-unix-managers@xxxxxxxx
Subject: Problem installing ECO T64KIT1001167-V51BB27-ES-20070321

I am seeing the same problem as reported in this email, but I didn't see any solution posted to the list yet.

Has anyone found a solution, or a way to work around the path application failure?

I've opened a case with HP (3218624946), their engineers are look into the issue.

-----Original Message-----
From: tru64-unix-managers-owner@xxxxxxxx
[mailto:tru64-unix-managers-owner@xxxxxxxx]On Behalf Of
Sent: Thursday, 05 April, 2007 11:05
To: tru64-unix-managers@xxxxxxxx
Subject: Follow-up on Question on problem installing ECO


It seems that the question/issue regarding installation of the ERP/ECO
T64KIT1001167-V51BB27-ES-20070321 is: should an ERP/ECO for the Tru64unix
version 5.1B BL27 operating environment to be applied over aggregate patch kit
6 have conflicts or intersections with a patch from a previous aggregate patch
- in this case aggregate patch kit 5?
If so, then are there instructions in the installation documentation for
aggregate patch kit 6 to remove all BL26 ERP/ECO kits including aggregate
patch kit 5?

Bill Glessner - System programmer
Central Washington University

During the installation of the T64KIT1001167-V51BB27-ES-20070321 ECO, I have
encountered a problem. Specifically, in the "Checking patch prerequisites and
patch file applicability..." phase the dupatch script produces a number of
"Problem installing:" messages for the C2001.00 OpenSSL 9.8d patch where
conflicts between parts of the C2001.00 patch and a SP05 patch 26114.00 are
called out. The system in question has been in operation for several years
and during its lifetime the SP05 and SP06 Tru64unix have been installed over
the initial Tru64unix version 5.1B distribution. The exact sequence has been
Tru64unix version 5.1B -> Aggregate patch kit 5 (BL26) -> BL26 ERPs which
applied to the system's hw/sw configuration -> Removal of the BL26 ERPs prior
to installation of Aggregate patch kit 6 -> Aggregate patch kit 6 (BL27) ->
BL27 daylight savings time ECO C2017.00. What is the recommended procedure
for resolving the "Problem installing:" messages for the ERPkit C2001.00?

Relevant Pages

  • 9_Recommended error codes (specifically return code 5)
    ... * "return code 2" indicates patches are already installed. ... * "return code 25" means a patches requires another patch that is not yet installed. ... With or without using the save option, the patch installation process ... Installing 114008-01... ...
  • Re: Which security patch NOT to install
    ... This revised patch corrects an installation issue that some customers ... has caused some customers difficulty installing the patch. ... Unless she has the previous patch for those languages installed why ... (Command Software A/V) ...
  • Dependency problems with Tru64 patches
    ... Once again I am trying to install a security patch and it is failing to ... An online manual defines a customer specific patch as: ... Problem installing: ...
  • Re: MS02-018 Breaking ASP ODBC
    ... > after installing the latest security hotfixes as of April ... >>1) IIS 5 web server can't be contacted. ... >>before the patch and that fixed that problem. ... >>load some VB components that fail to connect to my Oracle ...
  • Re: Bit of a rocky start
    ... retrieving character lists which Blizzard says should be resolved by 4:30. ... Patch required, gulp. ... Blizzard updater appears, 1% installing "locale-wnUS.MPQ' ... Okay, so, framerate seems to be slightly up, or maybe my imagination. ...