Firstly, you can set the DB back to simple recovery mode. You can shrink the logs insimple, you just can't back them up.
The open tran info shows that the DB thinks it's published.
(Oldest distributed LSN : (32471:27046:1)
Oldest non-distributed LSN : (32471:29355:1))
That refers to the log entries that have not been passed on to the distributor. Was it restored from a backup of a published DB? Sometimes the published status partially stays with a restored database. Enough to stuff the logs up anyway.
Go to query analyser and run the following (only if you are very sure this DB is not supposed to be published!!!!!!!)
exec sp_repldone NULL -- mark all log entries as distributed
checkpoint -- auto-truncate the log if in simple recovery
Now run DBCC SQLPERF (logspace) and see if the usage has dropped.
The permainent fix is to set up a publication on that DB (it doesn't matter of what) then drop the publication. That should clear out the reminents of replication. A check of DBCC OPENTRAN after that should have no references to replicated LSNs
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass