transactional replication log reader error

Hello, I am new to replication, and I just set up a transactional replication. When I look in the replication manager, there is a red x on the log reader agent. The error says that "An access violation occurred". I can't seem to figure out why this is. My subscription isn't updating, because of this. I have one idea of why it might not be working, and that is that I truncate the transaction log file everynight. Is this possible, and what would the workaround be. The transaction log grows so big that I need to do this, but I also need to be able to do replication. Please let me know what you think. Thanks a lot,
Ben

Hi Ben,

truncating the log shouldn't impact replication, since the log has a replication marker and will not allow the log to shrink beyond that marker anyway (the marker being the last transaction to have been replicated)

I guess the easiest is to not truncate the log for a couple of nights and check if the error continues.

If you really don't want the log to grow, then set the database recovery option to "simple". This should leave the log at the maximum size required for your largest transaction. If this is still too big, then you may need to work out which transaction is causing this, and seeing if it can be broken up into smaller transactions/batches

Cheers
Twan

I went into the log reader error history, and it looks like it is bailing out on the second step, which is to start the log reader agent. Any thoughts would be greatly appreciated. Thanks,
Ben

no, that was for another version of SQL, and I'm not using any filter. I am having trouble with the log reader agent. Thanks for your help though.

I've tried that also, and it doesn't seem to work either. I use SQL authentication with a user account that I set up myself.

where do I check these?

I believe so. I have checked the account that I am using, and I have every possible privilege set up for it. Tonight I will try installing the service packs, and reinstalling the subscription.

Thanks for the help everyone. I finally just removed the publication, put on the service packs, and reinstalled the publication, and everything worked.