I really appreciate your help, and I want to use your information to resolve our issue, but I can only do so much. I am trying to put together...

We found the following query which cleared the transactions and allowed us to shrink the log:

exec sp_repldone @xactid = NULL, @xact_seqno = NULL, @numtrans = 0, @time = 0, @reset...

Is there any way I can find out when or who tried to use the replication??

Thanks for all the help with this! Unfortunately at this point, my hands are completely tied by IT!!! The log file is now up to 450GB.

Thanks again!!

I tried the option of switching the database to simple mode as recommended in the other post. However, that did not resolve the issue. I have never set up replication,...

I did get enough diskspace to run the stored procedure, but it did not clear the entry for log_reuse_wait_desc in sys.databases

I am trying to run sp_removedbreplication, but the log is currently full and I am out of disk space.. I am hoping I can get out IT to give me...

According to everyone I have asked, the answer is no! We have not used replication......

Thank you very much! I believe this Solution will get me the results I am look for!!

Our server finally choked itself to death and shut down. I am now trying to figure out what caused the processes to fire. Now the real fun begins!!

That is what I am trying to figure out. I ran the sp_cycle_errorlog and here is the result:

Msg 17049, Level 16, State 1, Procedure sp_cycle_errorlog, Line 9

Unable to cycle error...