Solution - Designer Express - "One or more failed to commission, see event log"

Version 1

    Behavior

    When trying to commission some features, you get the errors "One or more failed to commission, see event log".  The event log has 3 events that look something like

    2013-03-27 14:26:08,539 [1] ERROR Miner.Desktop.DesignerExpress.FeatureConverter [(null)] - Field is not editable.

    System.Runtime.InteropServices.COMException (0x80040658): Field is not editable.

    at ESRI.ArcGIS.Geodatabase.IFeatureBuffer.set_Value(Int32 Index, Object Value)

    at Miner.Desktop.DesignerExpress.FeatureCopier.CopyFields(IFeature fromFeature, IFeatureBuffer toFeatureBuffer, IFeatureClass toFeatureClass, IGeometry fromShape)

    at Miner.Desktop.DesignerExpress.FeatureCopier.CopyFeature(IFeature originalFeature, IFeatureClass toFeatureClass, IGeometry shape)

    at Miner.Desktop.DesignerExpress.FeatureConverter.ConvertFeature(IFeature designerFeature, Boolean copy, IGeometry shape)

    at Miner.Desktop.DesignerExpress.FeatureConverter.ConvertSortedFeatures(List`1 featureList)

    {log4net:HostName=2K3-32-LRGHD, LoggingAssemblyFileVersion=10.10.0.276}

     

    2013-03-27 14:26:08,539 [1] ERROR Miner.Desktop.DesignerExpress.FeatureConverter [(null)] - Could not convert DESIGNERAnchorGuy with OID 29327 to Feature Class Anchor Guy

    {log4net:HostName=2K3-32-LRGHD, LoggingAssemblyFileVersion=10.10.0.276}

     

    2013-03-27 14:26:08,508 [1] ERROR [(null)] - "Unable to get subtype code"

    HRESULT: -2147220465

    File: "d:\root\source\com\components\mmgeoobjects\IFeatureEditImpl.h"

    Line: 347

    {log4net:HostName=2K3-32-LRGHD, LoggingAssemblyFileVersion=10.10.0.276}


    Cause

    This has been known to be caused by fields on the target "real" feature (NOT the Designer Express feature) being set to read-only.  ESRI's "Editor Tracking" tends to set fields to be "read only", so right now Editor Tracking is not compatible with Designer Express.


    Solution

    In ArcCatalog, you can right-click on the feature class, hit Properties, then on the "Editor Tracking" tab you will want to uncheck the "Enable editor tracking".

     

    Once you have done that, now your layers will default back to "No" for "Read-Only" if you add them to a blank map. HOWEVER, somehow your stored displays have been saved with this "Read-only" flag set. Since this is saved within the map document on the layer itself, you will have to manually go in to your stored display and remove the "Read-only" flag from those 4 fields on your "Real" features.

     

    Alternatively, once you've disabled the "Editor Tracking", you can remove the existing layer from your stored display, re-add the feature to the map, and save the stored display. You will have to re-configure your symbology, though.