Failed to Compress the database - ERROR 999999

[wilcow]

ArcGIS Desktop version 10.6

SQL Server 2014

attempting to compress the DB and I get the following:

ERROR 999999: Error executing function.
Underlying DBMS error [dbo.DEFAULT]
Failed to execute (Compress).

I deleted all versions and killed all connections, but the error persists.

SDE_compress_log shows FAILURE -51 in compress_status and end_state_count is sky high.

I assume the state count is what's causing the problem, but I'm at a loss as to how to fix it. 

I know there's a ton of posts about Failure to Compress, but most of them have explicit errors to work from.

I've used Analyze Datasets, and Diagnose Version tables ("0 multiversioned tables had orphaned, duplicate, missing or redundant rows")

Any advice on troubleshooting would be appreciated. 

[DrVSSKiran]

Hi,

Check on below link. 

https://gis.stackexchange.com/questions/377883/executeerror-error-999999-error-executing-function-fa...

[wilcow]

Thanks but that seems to refer to a Create FGDB script in Python.

I don't see how it would help in this situation.

Am I missing something?

[DrVSSKiran]

Have you tried this work arround.

Try once these settings before you compress the DB.

1. On the machine where SQL Server  is installed, navigate to Start > Programs > Microsoft SQL Server > SQL Server Management Studio.
2. Highlight and right-click the instance and click Properties.
3. In the Server Properties window:
   A. Select 'Permissions'.
   B. Highlight the 'sde' user. Verify the user has 'View Server State' permission available.
   C. Click the check box under 'Grant' for the 'View Server State' permission

[wilcow]

checked and the SDE user did not have View Server State granted. 

so i granted the View Server State permission but still get the same error.

[George_Thompson]

It may be best to work with technical support on this issue.

[wilcow]

Yeah I guess so.

When I run the Compress GP Tool in Pro that's what it tells me as well.

[WilliamRice]

Also check the Windows Sever Event logs.  If the compress failure is due to a SQL Server database table or index issue then the compress failure will often register a useful error message in the event logs.

[wilcow · Accepted solution]

fixed this with the help of tech support - the anonymous error referred to some orphaned locks in a couple of tables. we found them by searching SDE_state_locks and SDE_table_locks tables and deleting any locks that weren't present in SDE_process_information table