Hi,
How does the enterprise gdb register that a branch version no longer has a particular user's shared lock? The context is that the user (i.e. Poster) in charge of posting a branch version back to default is not allowed to reconcile due to the error that the version is still in use. Upon checking the geodatabase administration locks for the enterprise gdb, found out that the version to be posted is held by two users: the Poster and another user, Editor (the owner of the named branch version). However, the Editor mentioned that they have already 'checked out' of their version by changing their named branch back to DEFAULT, as well as removing the layer from their ArcGIS Pro.
What could be the cause that despite the Editor user disconnecting from their named branch, the enterprise gdb still thinks that the Editor user has a "shared lock" on their named branch, thus preventing the Poster from reconciling and posting the Editor's named branch version back to DEFAULT?
We are working on ArcGIS Enterprise 10.9.1, ArcGIS Pro 3.0.1, and using Microsoft SQL Server 2019 standard edition.
Thanks