Please consider reviewing the following topic:
- There are some specific requirements for feature service.
Yes I am well aware about those requirements - I also followed the step by step "bird watch" tutorial which still created the same error message. Can you indicate in which cases this exception is thrown?
Unfortunately ESRI is very quiet on this. I will be at the UC next week hopefully I get a bit more information there
Has anybody found a solution to this?
I've been banging my head for 2 days over this, and still cannot work through it?
Solution found while working with ESRI tech support:
Turned out to be a combination of privileges and a possible corrupted properties on a specific layer.
I have seen this problem several times. The solution I figured out is outlined below:
1) Share the folder where the .mxd document is stored and give ArcGISSOC account privileges to read it in Windows Explorer.
2) Copy the .sde connection file which will be used to connect to an ArcSDE geodatabase to this shared folder.
3) Use this .sde connection file when adding feature classes and other data into an ArcMap map document and not the one which is created under the Database Connections folder in ArcCatalog. This is because the .sde connection files created here are stored in the Windows user account folder, i.e., C:\Users\%username%\AppData\Roaming\ESRI\Desktop10.0\ArcCatalog in Win7 or C:\Documents and Settings\%username%\Application Data\ESRI\Desktop10.0\ArcCatalog in WinXP and it seems as ArcGISSOC cannot get access to this .sde connection file.
4) If all of these did not help, you can try grant privileges to the ArcGISSOC account for the feature class in the ArcSDE geodatabase - right-click the feature class and choose Privileges. Then grant the Edit privilege to the ArcGISSOC account.
Good luck all and please keep posting if you have found another workarounds or solutions.
My service was created but 'No Layer or Table was initialized.' I took the last advice from Alexey Tereshenkov above:
For 10.1, in catalog,
1. Right-clicked on my enterprise geodatabase holding my feature class
2. Choose Administration > Permissions;
3. Picked the Server\arcgis account and gave it 'Read Only' permissions;
4. Started the service with success.
Thanks @Alexey Tereshenkov