Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Issue: Unexpected results when HFix-5535 installed as an Additional Related Hotfix

Updated on October 2, 2015

Symptom

After installing a hotfix that includes HFix-5535 as an Additional Related Hotfix (dependent hotfix), you encounter unexpected results, including system failure, on the PRPC 6.2 SP2 system.

Explanation

HFix-5535 requires manual steps for successful installation, as described in Access Group settings for privilege control available in PRPC 6.1 SP2 (HFix-5536) and PRPC 6.2 SP2 (HFix-5535). When HFix-5535 is automatically installed as an Additional Related Hotfix (dependent hotfix) of a primary hotfix, the required manual steps for HFix-5535 can be inadvertently bypassed.

Unless you carefully examine the list of Additional Related Hotfixes for the primary hotfix that you are installing, you can overlook the presence of HFix-5535 as a dependent hotfix. Failure to notice HFix-5535 as an Additional Related Hotfix and subsequent failure to perform the required manual steps for its installation causes problems.

Solution

Always install HFix-5535 separately, as a primary hotfix, on any PRPC 6.2 SP2 systems that you have operating in any environment (Development, Test/QA, UAT, Staging to Production, Production).

HFix-5535 is available on My Support Portal, Hotfixes, Hotfix Self Service, but you must read the PDN Article cited to complete the required manual steps for installing this mandatory hotfix.

Required Reading

Access Group settings for privilege control available in PRPC 6.1 SP2 (HFix-5536) and PRPC 6.2 SP2 (HFix-5535)

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us