I am baffled by the unsuccessful attempts to shrink a transaction log from 100G to 10G on a SQL Server 2005 instance. I have shrunken numerous other log/data files successfully in the past. I can't see what is different about this log. Here's is the command I've used,
DBCC SHRINKFILE (<LogName>, 10240) WITH NO_INFOMSGS
Also, I have done a backup of the log prior to this. The shrinkfile operation did not error out. In fact, it came back almost instanteously but nothing had happened, the log is still ~100G in size.