IBM Support

PH21656: UPGRADING FROM 9.0.1.4 TO 9.0.1.8 LEAVES EXTRANEOUS DEVICE DRIVER ENTRY IN SERVICES REGISTRY, POTENTIALLY CAUSING A CRASH

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The MVFS architecture subtly changed in IBM Rational ClearCase
    9.0.1.7, where there were 3 components of the MVFS (the
    Credential Manager, the main MVFS driver, and the "storage
    minifilter" driver), only the former 2 are part of the current
    Windows MVFS.
    
    When upgrading from IBM Rational ClearCase 9.0.1.4 to 9.0.1.8,
    an "extra" device driver entry for "MVFS Storage Filter" is left
    in the HKLM\System\CurrentControlSet\Services registry key.
    
    On a Windows 2016 or later host, if there is also an issue
    renaming or deleting the previous MVFS drivers, this extraneous
    driver may load, leading to system instability due to conflicts
    with the newer driver.
    

Local fix

  • Boot to safe node and remove the "MVFS Storage Filter" key from
    the HKLM\System\CurrentControlSet\Services and
    HKLM\System\ControlSet{nn}\services keys.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of ClearCase on Microsoft Windows, when upgrading from *
    * a previous version to version 9.0.1.8.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When upgrading the version of ClearCase on a Windows system, *
    * a reboot is required to complete the upgrade installation.   *
    * After that reboot, the system may crash shortly after        *
    * restarting.   It may enter a loop of crashing and            *
    * restarting, in which case it must be booted in safe mode to  *
    * allow manual manipulation of files in order to work around   *
    * the problem.                                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The crash is caused by incomplete cleanup of a previous version
    which is being replaced during the upgrade. This is fixed in
    version 9.0.1.9.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH21656

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-31

  • Closed date

    2020-03-30

  • Last modified date

    2020-03-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARCASE WIN

  • Fixed component ID

    5724G2900

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"901","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
31 January 2020