Solution - Conduit Manager - The duct configuration dialog fails to open if data exists in the field

Version 1

    Behavior

    When trying to get the Duct Configuration dialog to open, nothing happens and the following is logged to the event viewer:

    2015-03-16 10:45:09,875 [Main Thread] ERROR  [(null)] - mmUlsFrameworkUI:

    frmULSEdit.frm.LoadDuctColumns:

    -2147219880 : Field is not editable.

    Error at line: 4719 - Build: 10.21.1102

    {log4net:HostName=PC14215, LoggingAssemblyFileVersion=10.21.10.1102}

     

    2015-03-16 10:45:09,876 [Main Thread] ERROR  [(null)] - mmUlsFrameworkUI:

    frmULSEdit.frm.Form_Load:

    -2147219880 : frmULSEdit.frm.LoadDuctColumns:

    -2147219880 : Field is not editable.

    Error at line: 4719 - Build: 10.21.1102

    Error at line: 2192 - Build: 10.21.1102

    {log4net:HostName=PC14215, LoggingAssemblyFileVersion=10.21.10.1102}

     

    2015-03-16 10:45:09,884 [Main Thread] ERROR  [(null)] - Miner & Miner ListItem TreeView Control:

    MMListTree.CreateInternalTree:

    Automation error

    Error at line: 2192 - Build: 10.21.1102

    {log4net:HostName=PC14215, LoggingAssemblyFileVersion=10.21.10.1102}

     

    2015-03-16 10:45:09,885 [Main Thread] ERROR  [(null)] - Miner & Miner ListItem TreeView Control:

    MMListTree.UserControl_Show:

    MMListTree.CreateInternalTree:

    Automation error

    Error at line: 2192 - Build: 10.21.1102

    Error at line: 2576 - Build: 10.21.1102

    {log4net:HostName=PC14215, LoggingAssemblyFileVersion=10.21.10.1102}

     

    When this is observed, usually new conduit systems are able to be edited without issue.  Only existing conduit system features with a duct configuration set will fail to open.

     

    Problem

    This has been known to happen if the fields on the DuctDefinition table are somehow set to read-only.  While the DuctDefinition table does not actually store any records, it is used to model the fields that are available in the duct configuration dialog. 


    One reason that the fields might be set to read-only is if ESRI Editor Tracking has been enabled on the table. Sometimes organizations set "Editor Tracking" to be enabled across the entire database.  Since the DuctDefinition table does not store any actual data, you do not need Editor Tracking to be enabled on this table. 


    Solution

    Disable editor tracking:

    1) In ArcCatalog, right-click the DuctDefinition table and choose Properties

    2) Go to the "Editor Tracking" tab.

    3) Uncheck the "Use editor tracking" checkbox.


    If the fields are read-only for some other reason, you need to ensure that the fields are not read only.