Solved! Go to Solution.
I don't think it matters who creates the Feature Layer but it needs to be versioned and the ArcGISSOC user needs to granted editing privileges (view and edit) (all done in Catalog).
Jay...mark yes if that answered your question
Is your server and SDE on separate machines?
Occasionally, the situation may arise that your data is on a machine with no components of ArcGIS Server installed and you are following the recommended practice of using local accounts for the SOC account. You will need to use the operating system tools to create a local SOC account on the machine containing your data. Create a local account on the machine hosting your data and assign it the same name and password as the SOC account on all the other machines in your deployment. The GIS server will then be able to recognize that it has permissions to access your data.
http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#/Common_proble...
Jay
This is our exact environment:
1. The data in SDE must be versioned. Owner of the data does not matter, as long as an editor (DB user) has edit privileges.
2. The ArcGISSOC user is not a database user, only OS. It does not need to be on the database server
3. Create your mxd and switch the version to the edit version (this will change at 10.1, were you will likely publish the msd at the parent SDE version and specify in the application which child private version you will use). Right now you have to hardcode the edit version in the mxd/msd.
4. Publish the MSD to server, enabling feature services.
5. The directory the MSD resides in is the one that <active directory>/ArcGISSOC user needs access to.
I started with a new feature dataset and a new feature class, with a edit version (this part I missed earlier). Everything seems to work fine now.
Thanks
@Jean-FrançoisDucré-Robitaille @JeffPace Hi!
I have a similar problem. I can't editing data in my ArcGIS Portal or in Experience Builder (including Developer Edition). This data we get from Oracle database. Do you have any idea for solve this issue?
Thanks a lot for any advice!
Your options are
1. Version the data, publish the data as a headless versioned editor, using group permissions in portal to manage access
2. Version the data, publish the data as parent public version owner (sde) . NOT RECOMMENDED
3. Publish the data as the data owner and do non-versioned editing