@bettsgeospatial I can't see anything obvious that you are doing incorrectly. At first I thought 'Stop' might be a reserved word, but I can write to a Stop layer on our AGOL OK. Things you can try to narrow down where the problem originates:

• Try writing to only one layer at a time. Perhaps it's not the Stop layer specifically that is the issue, but your Portal connection or the feature service name instead.
• Try writing to a new layer instead of truncating. Or try truncating using the AGOL tools and reloading.
• Try selecting the feature service name from the Portal to ensure you've got the syntax FME needs.

Thanks Mark ...I really appreciate the quick response

I am having this same error. Can you share what syntax helped fix the issue? Thanks!

I think I have fixed this issue. I was trying to update a hosted table in my AGOL (from a table in my local Enterprise Geodatabase) and was getting the same error you were. I had published my hosted table using ArcGIS Pro before running the FME script. After publishing to AGOL the hosted table was there with a service definition file but there was no file geodatabase with it. It seems that you must have a file geodatabase to do this kind of update with FME. So what I did was... I deleted my hosted table and service definition layers from AGOL. Then I created a new workspace/FME file and setup the writer with a new table name that didn't exist in AGOL. When I ran the script in FME, it created a new hosted table with a corresponding file geodatabase with the same name. This worked like a charm! I'll be testing it tomorrow to see if it picks up the updates to the Enterprise Geodatabase overnight.

I had additional failure at writer .....after changing the names to match

EDIT: following this post, I eventually re-created my readers and writers, including new service names. And since then, they've been running without issues. I'm not sure where the issue was, if it was some configuration on the FME and/or AGOL side. Also, one feature had an attribute name with 47 characters: this doesn't seem to be a cause and was never reported in any logs as being a problem, but I reduced the name to less than 32 characters, just in case.

Hello

I've been struggling with the exact same problem for 4 months now and I haven't been able to find a solution, and I'm not quite sure I understand how you solved your case.

I have two data sets that I import in to AGOL:

• CSV file
  • Service name: NAME_RT
  • Single layer: NAME_RT (same name as service, coincidentally)
• Excel file with 3 sheets
  • Service name: NAME_Stats
  • Each sheet one layer: AB, CD and Stats
• All are configured for INSERT:Yes and Truncate First

Both writers work fine the first time (creating the service), but fail most of the times I re-run them. Yesterday both failed when I ran them a second time. Today the CSV one was successful but the Excel one still fails.

For the Excel one I'm getting the error you get:

• Could not find a Feature Service item matching the Feature Service directive 'MyAGOLName/NAME_Stats'. A new Feature Service will be created
• and further ahead:
• ArcGIS Online Feature Service Writer: Uploading File Geodatabase dataset as an Item named 'NAME_Stats'
• ArcGIS Online Feature Service Writer: Publishing Feature Service using Item named 'NAME_Stats', Target SR is WKID 102100
• ArcGIS Online Feature Service Writer: Deleting Item 'NAME_Stats'
• ArcGIS Online Feature Service Writer: Encountered an unexpected error. The error code from the server was 'none' and the message was: 'Service name 'NAME_Stats' already exists for 'randomletters''. Details: ''

I tried renaming the new service in FME to be all uppercase, but it still throws the error (so I guess it's not case-sensitive).

Notice that the services are created by FME, so I don't see how it can be a naming problem.

This is driving me nuts. Any help is appreciated.

Thanks!