Hi Bill- sorry to hear you are still having issues with this compress / locks. The filling of the transaction log could well be due to existing / orphaned locks still existing. Did you ensure the following tables were completely empty in SQL before attempting the compress?
sde.SDE_object_locks
sde.SDE_layer_locks
sde.SDE_table_locks
sde.SDE_state_locks
sde.SDE_project_information
Additionally, I'd recommend truncating or deleting a large amount of the current transaction log to free up space in SQL. Further- ensure the 'Recovery Model' of the geodatabase is set to 'Simple' before running compress. You can change it back to 'FULL' after the compress if you want, or just leave it set to simple and change it to FULL when you want to take a manual or scheduled full backup of the database.
Please feel free to give the above suggestions a try and hopefully, this gets your GDB back up, running, and accessible / compressed.