How do you find a transaction given the LSN

Hi.. 

I'm pretty sure I have the problem where an undistributed transactions is causing my t-log to grow to infinity.  Well, maybe not quite.. 54 G t-log for < 2 G data.  We are backing up the t-log.  We're running 2008R2 10.50.4000

My log_wait_reuse_desc = REPLICATION.

My output for dbcc opentran is:

Replicated Transaction Information:
        Oldest distributed LSN     : (0:0:0)
        Oldest non-distributed LSN : (14628:9126:1)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Is there a way to find the transaction and cancel it.. ok  cancelling is probably asking too much, but is there a way to see the SQL behind the transaction?  Actually, it could be a quite old transaction.

My first guess was sys.dm_tran_database_transactions, but there is nothing there.

Here's the article I've been working off of:

http://blogs.msdn.com/b/sqlserverfaq/archive/2009/06/01/size-of-the-transaction-log-increasing-and-cannot-be-truncated-or-shrinked-due-to-snapshot-replication.aspx

It sounds like my only option is to run sp_repldone.  I see this recommended a lot, but as I understand there are caveats? Also, I see comments that suggest this may be a bug, but I think those threads are mostly related to 2005.

Thank you for your time.

Ria Caussyn

Ria Caussyn