Why does Collector say Update failed?

[JoshWhite]

When I was testing Collector I made a test feature but got a message that the update failed-updates could not be sent and I can cancel or retry.  Cancel abandons the feature and retry returns the same result. 

[RussRoberts]

Are you using hosted or your on-premise server?

Are you able to collect in AGOL?

If you try in AGOL - collect a feature and refresh your browser page and see if the feature still exists or see if it made it back into your SDE. This will help us determine where the issue is.

Thanks

Russ

[JoshWhite]

I am using an on-premise server.

It doesn't appear I am able to add features in AGOL either.  It says click to add a point and then nothing happens.  I have several feature layers present in this particular map and none of them appear to work, actually one works for some reason but the rest don't.  I have done some schema changes, would that cause the issue?  If so, how can I fix this issue?

[RussRoberts]

I don't think that would cause the issue. If you can enable debug logging on your server or look at the network requests when you try to add you might be able to determine the issue.

Russ

[JoshWhite]

The log repeatedly says a database error has occurred after I attempt to add a feature, nothing more.  The source is featureservice.mapserver.  The service featureservice appears to be running.  Yes I know simple name but the idea was this was a test service.  Fiddler doesn't return anything on a click.  Also interesting is that I apparently can edit existing points in AGOL.  However, even edits will not post from Collector.  Again, I am able to edit one of my features without issue in Collector and in AGOL. 

[RussRoberts]

Did you have the debug logging enabled from the servername/arcgis/admin ?

Thanks

Russ

[JoshWhite]

Oh, I missed the Debug part.  I will try and get some of the info:

SEVERE

Aug 1, 2014, 3:58:54 PM

A database error occurred.

featureservice.MapServer

DEBUG

Aug 1, 2014, 3:58:54 PM

RequestId: 17068 8/1/2014 3:58:53 PM 52a0166d-90b4-49f6-908b-2a0ab7623324 Performed StopEditing (without save).

featureservice.MapServer

DEBUG

Aug 1, 2014, 3:58:54 PM

RequestId: 17068 8/1/2014 3:58:53 PM 52a0166d-90b4-49f6-908b-2a0ab7623324 Aborted the Edit operation.

featureservice.MapServer

DEBUG

Aug 1, 2014, 3:58:54 PM

RequestId: 17068 8/1/2014 3:58:53 PM 52a0166d-90b4-49f6-908b-2a0ab7623324 Error while Performing Edits for GraphicFeatureServer.ApplyEdits.

featureservice.MapServer

These are a few of the entries that resulted.  Error while Performing Edits for GraphicFeatureServer.ApplyEdits seems to be the culprit but I have no idea what this means.

[RussRoberts]

Thanks for the info Josh. One more thing if you could try and collect/edit those layers in ArcMap would be great if the edits can be saved after an edit session.

Thanks

Russ

[JoshWhite]

Yes I edit most of those layers on a regular basis in ArcMap

[SumantMallavaram]

I wanted to chime in with a similar problem using the same workflow but with an error that is a little more specific:

Error: Underlying DBMS error [[Microsoft][SQL Server Native Client 11.0][SQL Server]There are no rows in the current fetch buffer.] [GDBName.DBO.LayerName].

I first got this message in one geodatabase. I then moved it to a brand new GDB. It worked fine for two days and now the same error is coming back up again. This is my first app using the 10.2.2 offline mode and as such I don't have any comparison points with other apps.

Any ideas on whether this is related to my specific database/datasets or could this be a bug.

Thanks