Solution - Designer Express - Error When Deleting Design Express Versions in Orphan Versions Cleanup Tool

Version 2

    Behavior

     

    When the Orphan Versions Cleanup Tool is run in ArcCatalog, ESRI versions for Designer Express designs marked to have their ESRI version deleted are not completely deleted. The following error is shown in the Orphan Versions Cleanup Tool dialog:

     

    Attempting to delete Designer Express version: ADAMS.WR825_DN861

    Version could not be found or has already been deleted.

    This could indicate that a version is marked as private and needs to be deleted manually or this tool needs to be run as the owner of that version.

     

    These errors are also written to the Miner event log:

     

    2016-04-01 08:52:53,208 [1] ERROR  [(null)] - mmPxBaseUI.dll::PxApplication.:
    mmPxBaseUI.dll::PxApplication.::DeleteExpressVersionRecords
    Invalid procedure call or argument
    Error at line: 3623 - Build: 10.21.1854
    {log4net:HostName=WIN7DT56, log4net:UserName=ADAMS, LoggingAssemblyFileVersion=10.21.20.1854, log4net:Identity=}

     

    2016-04-01 08:52:53,208 [1] ERROR  [(null)] - PxSDEVersion:::
    PxSDEVersion::CheckValid(Let IMMPxSDEVersion_Status)
    Attempted operation on an invalid version object
    {log4net:HostName=WIN7DT56, log4net:UserName=ADAMS, LoggingAssemblyFileVersion=10.21.20.1854, log4net:Identity=}

     

    2016-04-01 08:52:53,208 [1] ERROR  [(null)] - PxSDEVersion:::
    PxSDEVersion::IMMPxSDEVersion_Hydrate
    Version is not valid
    {log4net:HostName=WIN7DT56, log4net:UserName=ADAMS, LoggingAssemblyFileVersion=10.21.20.1854, log4net:Identity=}

     

    Cause

     

    This is caused by bug CLS-60119. Due to this bug, the Orphan Versions Cleanup Tool is attempting to delete an ESRI version for a Designer Express design that has already been deleted. When the errors occur, the deletion of ESRI versions stops, and the remaining versions set for deletion do not get deleted.

     

    Solution

     

    Bug CLS-60119 has been fixed in the latest patch for ArcFM 10.2.1. This bug fix will also be included in ArcFM 10.2.1c and ArcFM 10.2.1b SP2, upon their respective releases.