Anyone had Error 160277: The row contains a bad value while running load data using workspace?

BrettRosso

Hi all,

Has anyone encountered Error 160277: “The row contains a bad value” when running the Load Data Using Workspace geoprocessing tool?

It appears that a value is being written to a string field that exceeds the field’s defined length. However, the error message doesn’t indicate which specific field is causing the issue.

To troubleshoot, I updated all string fields in the target asset package to a length greater than 2000 characters, but I’m still encountering the same error. I also updated the individual excel files being referenced in the data reference.xls spreadsheet

Does anyone have suggestions on next steps or additional things to check? I do have an Esri tech support ticket open, but wanted to ask the group as well.

Thanks in advance,
Brett

screenshot2.png

screenshot.png

image 2.png

image 1.png

TinaBrewington_0-1743198975579.png

RhettZufelt_0-1743198617445.png

BrettRosso

Good morning,

While preparing the data and spreadsheets to send to tech support, I realized that the Load Data to Workspace tool had actually uploaded about one-third of the features to the asset package—something I hadn’t noticed before making the original post.

Prior to that, I had already adjusted all string lengths to around 1,000 characters. However, I believe the subsequent errors occurred because either:

1. Existing features were being re-appended to the asset package, or
2. The tool wasn’t recognizing the updated string lengths.

After clearing all data from the layers, I decided to run the tool one more time—and it worked! (With minor warnings, which were expected.)

I truly appreciate all the replies and suggestions @RobertKrisher  @gis_KIWI4 . On to the next step!