New answers tagged

0

We resolved this issue by killing the locks in SDE_state_locks table. Restarting the sdeArc service on the server killed 7/10 of the locks. The remaining 3 had the SDE_state_locks.direct_connection set to Y, the other 7 were N. I don't know what that means. So then I dropped all the tempdb tables associated to these 3 remaining locks, restarted the sdeArc ...


0

I was facing same issue while working on the utility network database. It happens when two user modify the same feature attribute/geometry in two different ways. Try reconciling the version only after refreshing parent database .



Top 50 recent answers are included