laptop and a wrench

Bug

Cannot close state when a stored procedure having the close edit version syntax is called from a trigger.

Last Published: August 25, 2014 ArcSDE/Enterprise Geodatabase
Bug ID Number NIM058818
SubmittedJuly 7, 2010
Last ModifiedApril 2, 2025
Applies toArcSDE/Enterprise Geodatabase
Version found9.3.1
Operating SystemWindows OS
Operating System Version2003
StatusKnown Limit

Additional Information

Multiversioned view edits called via a trigger can fail due to transaction scope issues. See the workaround for more info on changes in next release.

Workaround

This is a known limit. The SQL Server trigger is expecting to close with a transaction count of 1. The Edit_version stored procedure expects a transaction count of 0 to close a state at 9.3.1, or returns the transaction count to 0 (10.0 SP4 fix). Either case is causing the trigger to abort.At 9.3.1 & earlier there is no workaround.For edits exclusively to the default version, upgrade to 10.0 SP4 or later. Edits to default no longer use the edit_version stored procedure. See the 10.1 documentation for more information.For edits to child versions at 10.0 SP4 or later you can test adding a 'BEGIN TRAN' statement to the assessment_xy_to_assessment_mobile trigger immediately after the exec sde.insert_assessment_mv stored procedure call. This will increment the transaction count to 1. This should satisfy the trigger requirement without impacting the stored procedure. The transaction count is returned to 0 when the trigger completes.

Steps to Reproduce

Bug ID: NIM058818

Software:

  • ArcSDE/Enterprise Geodatabase

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options