Symantec Access Management

Expand all | Collapse all

UpgradeReadinessCheck.cmd Parallel Upgrade Incompatibilities

Jump to Best Answer
  • 1.  UpgradeReadinessCheck.cmd Parallel Upgrade Incompatibilities

    Posted 02-05-2018 01:43 PM

    We performed a Parallel Upgrade for 12.7 SP01 , Existing environment is on CA SSO 12.52 SP01 CR08.

    After Running UpgradeReadinessCheck.cmd we are seeing below.

     

    F:\CA\siteminder\bin>UpgradeReadinessCheck.cmd -u  <User> -p <Password>
    INFO: Starting UpgradeReadinessCheck .....
    INFO: Connection to Policy Store established successfully.
    INFO: Fetching Policy Data.....
    INFO: Fetching Policy Data complete.
    INFO: Logging custom 32-bit binaries, unsupported auth-schemes information.
    INFO: 32-bit custom binaries or unsupported binaries or unsupported auth-schemes found.
    INFO: Output of 32-bit custom binaries and unsupported auth-schemes that are configured is logged to the below file:
    F:\CA\siteminder/log/UpgradeReadinessCheck_01_08_2018_03_21_58.txt

    F:\CA\siteminder\bin>

     

    Output of  F:\CA\siteminder/log/UpgradeReadinessCheck_01_08_2018_03_21_58.txt

    Custom binaries configured but not available in lib or bin:
    ===========================================================
    Binary Name: npssessionlinkner
    Object Name: SessionLinker
    Object Type: ActiveResponse
    Object Path: Domain[Domain Name1]/ActiveResponse[SessionLinker]
    Binary Path: Couldn't find this binary in lib or bin
    Description: Couldn't determine the bitness

    Binary Name: npssessionlinkner
    Object Name: SessionLinker
    Object Type: ActiveResponse
    Object Path: Domain[Domain Name2]/ActiveResponse[SessionLinker]
    Binary Path: Couldn't find this binary in lib or bin
    Description: Couldn't determine the bitness

     

    CA SSO 12.7 SP01 has inbuilt (Part of CA SSO 12.7 SP01 build it will install). with Name showing as: F:\CA\siteminder\bin\NPSSessionLinker.dll but we are seeing npssessionlinkner not found under bin.

    Is there any configuration(adding to Path) required to perform to fix these errors?

    And why only two domains are showing?

    There other domains which uses sessionlinker.

    Currently our environment is a mixed environment (few are 12.52 SP01 CR08 & few are 112.7 SP01 )

     

    Do we need to install  "ca-erp-sessionlinker-12.52-win64" to fix this issue?

     

    Does "UpgradeReadinessCheck" Utility only work for In Place Upgrade ( Upgrading 12.52 SP02 64 -bit to 12.7 SP01) Only?



  • 2.  Re: UpgradeReadinessCheck.cmd Parallel Upgrade Incompatibilities
    Best Answer

    Posted 02-05-2018 01:44 PM

    Update from CA SSO Support:

     

    The documentation only address's the use of of the upgrade readiness tool as part of the "In place upgrade" process.

    It's used to identify any 32 bit custom code that needs to be recompiled to 64 bit.

     

    https://docops.ca.com/ca-single-sign-on/12-7/en/upgrading/in-place-upgrade/upgrade-policy-server Step 5

     

    Note: The installer runs the Upgrade Readiness utility to identify potential issues with custom components. If no issues are found, the utility runs silently. If issues are found, the installer displays the Important: Upgrade Readiness Check screen, which lists the components that you should remove or upgrade (to a 64-bit version) after the upgrade completes. For more information about the Upgrade Readiness Check Utility and to learn how to run it after the upgrade, see Manually Check for Issues with Custom Binaries and Authentication Schemes. Given that this information is expected to resolve this issue, I'll close out this case at this time.