Diagnose Version Tables and Repair Version Tables fail and return Error 999999 when the sde_tables_locks table has the tables_locks_fk foreign key constraint.

Workaround

Before running the Repair Version Tables geoprocessing tool, run the following SQL in SQL Server Management Studio on the enterprise geodatabase to drop the 'table_locks_fk' key constraint.

• ALTER TABLE [sde].[SDE_table_locks] DROP CONSTRAINT [table_locks_fk]
• GO

Once the key constraint is dropped, run the Repair Version Tables geoprocessing tool.

After the Repair Version Tables geoprocessing tool is run successfully, immediately recreate the 'table_locks_fk' foreign key constraint to avoid other issues such as orphaned connections & locks. Run the following SQL to recreate the 'table_locks_fk' foreign key constraint.

• ALTER TABLE [sde].[SDE_table_locks] WITH CHECK ADD CONSTRAINT [table_locks_fk] FOREIGN KEY([sde_id])
• REFERENCES [sde].[SDE_process_information] ([sde_id])
• ON DELETE CASCADE
• GO
• ALTER TABLE [sde].[SDE_table_locks] CHECK CONSTRAINT [table_locks_fk]
• GO

Steps to Reproduce