Here is the numbers:

The database is taking 26851.05 for its log. This is 26 GB.

So, there is no maintenance on that one. It just keeps increasing. So, we might have reached a limit here or something that SQL Server cannot execute this operation without applying a lock. So, we would have to look at how to lower that log file and keep it to a maximum. How are you doing it on your end?