I'm facing the same problem here.
Error: Underlying DBMS error [[Microsoft][SQL Server Native Client 11.0][SQL Server]There are no rows in the current fetch buffer
Using arcgis 10.2.2 and working with offline data. When I try to edit features using ArcMap(same dataset as I use in offline mode), works for a while, then appear the error reported above.
Quite similar with Sumant Mallavaram problem.
Seth / Sumant / Antonio,
We are getting the same error when editing in ArcMap or ArcGIS Online to a SQL server database. Did you find any long term resolution besides restarting the SQL server?
ESRI support pointed us to this knowledge base http://support.esri.com/en/knowledgebase/techarticles/detail/43036, but enabled CLR is likely not an option because we are using a shared database instance.
I have encountered the same problem with an on-premesis 10.22 ArcGIS Server and a SQL-Server backed GDB. In my case the symptom was that the ApplyEdits REST API call failed.
The Error from ArcGIS Server is:
Unable to complete operation.
Unable to perform applyEdits operation.
And the detail in the logs is:
Error: Underlying DBMS error [[Microsoft][SQL Server Native Client 11.0][SQL Server]There are no rows in the current fetch buffer.]
I cannot yet explain how the server got into this state, but perhaps my resolution will help you. To resolve the issue we did the following:
ALTER DATABASE MyDatabase SET OFFLINE WITH ROLLBACK IMMEDIATE
ALTER DATABASE MyDatabase SET ONLINE
Once the services came back online the REST API was able to update features once again.
Thank you for your post Dave - I can verify having the same issue as the Original post and the same Error: Underlying DBMS error [[Microsoft][SQL Server Native Client 11.0][SQL Server]There are no rows in the current fetch buffer.]. Your solution fixed our problem. Now if we could only figure out why it happened in the first place?
Can any one else verify if Dave's solution worked for them as well?
I was also getting reports of the download stalling. Compressing the database with all connections closed, then taking it offline and back online again resolved it for me. Editing through ArcMap online was never affected, it was only the REST interface that was an issue.
The temporary fix of stopping all services and taking the SQL database offline and putting back online works but the big question is why do I have to do this every other week??
The archive enabled data which is being used offline seems to be source of the issue...
Error: Underlying DBMS error [[Microsoft][SQL Server Native Client 11.0][SQL Server]There are no rows in the current fetch buffer.] [GIS_EDIT.DBO.tmpRubbishRemoval].
This issue is caused by the database archive taking up too much room. We bumped the RAM on our database server and it fixed the issues. It is possible switching from a database with archiving to one with versioning may fix it as well.