Can't believe it's 9 years later since this post and I'm also experience this incident.
I'm running:
Enterprise 10.9.1 on SQL 2019. Using Desktop ArcMap 10.8.2.
Anyone know why this could be happening with this latest version?
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.