Error Code 308

[ScottSeay]

I run the Copy Features tool to get a new feature class that is added to my File Geodatabase.  This feature class is the result of a join with a Table also in the Geodatabase.  The new feature works in ArGIS Pro but not in the older ArcCatalog and ArcMap.  Then I try to export the resulting feature to another folder as a shape file and get two error codes:  308 and 210.  

I have used this same process for years in ArcCatalog and ArcMap through 10.8 with no errors ever.  I do this process to share the resulting feature class with colleagues.

I'm using ArcGIS Pro 3.3

Error below:

Feature Class To Shapefile
=====================
Parameters

Input Features 'Z:\Lone Star\ArcPro\Lone Star ArcPro.gdb\NAD27_TX_CENTRAL\TRACTS_CopyFeatures'
Output Folder Z:\Lone Star\Exported Shapes
Updated Output Folder Z:\Lone Star\Exported Shapes
=====================
Environments

Maintain fully qualified field names UNQUALIFIED
=====================
Messages

Start Time: Wednesday, September 18, 2024 2:54:35 PM
Failed to convert: Z:\Lone Star\ArcPro\Lone Star ArcPro.gdb\NAD27_TX_CENTRAL\TRACTS_CopyFeatures. ERROR 000210: Cannot create output Z:\Lone Star\Exported Shapes\TRACTS_CopyFeatures.shp
ERROR 000308: Invalid field type
Failed to execute (CopyFeatures).

Succeeded at Wednesday, September 18, 2024 2:54:39 PM (Elapsed Time: 3.28 seconds)

[Robert_LeClair]

A couple things to test/consider:

1.  You mentioned that the FC is a result of a join.  Did you export the joined FC to a brand new FC and then try to export that new FC to a shapefile/GDB FC?
2.  Are there any of the new 64-bit field types in your current FC?  See the following article how to downgrade 64-bit field types to 32-bit field types.

[ScottSeay]

Thanks so much for the reply.  The FC was created after the join by the Copy Features tool, and placed in the same GDB.  I checked the FC properties and the ObjectID is 32-bit.  

[Robert_LeClair]

Okay - thanks for the update.  Next thing to consider:  

You cannot use ArcMap to access datasets that participate in functionality that is specific to ArcGIS Pro. For example, you cannot access branch-versioned datasets, utility networks, or datasets with attribute rules from ArcMap.

Does this apply to the FC in question?  Also, are you able to share the dataset with me?  If so, my email address is rleclair at esri dot com - thx!

[ScottSeay]

I'm only using ArcGIS Pro GDBs for this issue.  I will send you an email with the zipped GDB.  Also, I tried to replicate the issue again, and this time I received Error Code 2809.  Weird.  

[Robert_LeClair]

@ScottSeay - thank you for the zipped data.  I was able to find the error.  In the provided data, you had a DATE ONLY field.  This is a new geodatabase field type introduced at ArcGIS Pro 3.2.0.  It will cause the error messages you're seeing as this new field type is not supported in a shapefile format.  My workflow was to create a new DATE field, use the Calculate Field GP tool to copy attributes from the DATE ONLY field to the newly created DATE field and delete the "old" DATE ONLY field.  Then the GP tools work as expected.

You can read more about it here - What's new from the geodatabase team in ArcGIS Pro 3.2 (esri.com)

[ScottSeay]

Thanks Robert.  This worked.  Since the tabular data was added from an excel spreadsheet, then imported as a GDB table, then lastly a FC was created using Copy Features, I have no control over the DATE ONLY field creation.  Is there a way to not make that the default field type?  Otherwise, I have many steps in ArGIS Pro that were not necessary in ArcMap.  

[Robert_LeClair]

Certainly Scott - more than happy to assist!  Since the DATE ONLY field appears to be coming from the MS Excel side of things, I wonder if you can let the editor of that worksheet to change the field type from a DATE ONLY format to a more traditional "long" date/time format that ArcGIS Pro would recognize without any issues?  Might work but would require testing.

Related, if you feel my response was the correct answer, you can click the "Accept as Solution" button on my response to close this thread.  Let me know if you have additional questions - more than happy to assist!

[IvanDImitrov]

hat about 

000308: Invalid field type ???
In 3.3.2 you can't export GDB class to a .SHP, due the Object ID field, BUT, you can't delete this field? 
What is going on, people? Why?

[Robert_LeClair]

You can export a geodatabase feature class to a shapefile using the Feature Class to Shapefile GP tool.  The ObjectID field in a geodatabase feature class is an Esri created and maintained field and it cannot be deleted as you described.  When the feature class is exported to a shapefile, a comparable field is created called FID.  Again this is an Esri created and maintained field that cannot be deleted.  

In some cases, you may have 64-bit field types in your geodatabase feature class.  These 64-bit field types are not supported in a 32-bit field type shapefile format.  You can read more about it here - Error: ArcGIS Pro: 002809 Field in is of an Unsupported Type for the Output Workspace