User has reported that when trying to delete an obsolete RCM analysis in a Test environment, the deletion would hang and the smart-client would eventually crash.
Reviewing the error logs, the following error message is generated:
2019-07-05 20:17:02.6342Z Error BENTLEY\User.name Ivara.OTAssert [12] File: f:\src\hotfixes\7.11.0.205\apm\framework\oqpers\cax.cpp(8372) : Failed Assert: oQuantityX::set - CAX FailureCreationInfo::PFInterval is Read-Only because the FailureCreationInfo top container is read-only.The following states have been calculated on this datamember: PFInterval
IF Acknowledgement is NOT NULLAND Acknowledgement.Status Is ProcessedReadOnly BENTLEY Modelled State Group(OID = 1000047910) defined on the FailureCreationInfo class
RCM analysis should rarely be deleted in a Production environment. Typically they can be deleted if they are not fully implemented into the regular maintenance process with Indicators, Tasks, and Failure history. If there is indeed a failure history and that history is linked to a Failure Mode than this error and crash will occur.
In cases where the RCM is needed to be legitimately deleted, you need to go into each failure mode in the analysis and find out if there are Indicator readings and Failure records linked to the failure mode.
The best place to do this is using the Asset # on the Performance Management view. Once you find the Failure record and open it, you need to first unlink the Failure Mode, then go to the Source Tab and Mark the Reading as incorrect.
Next you can delete the Failure record.
Finally, you should now be able to delete the RCM2 analysis.