Log Shipping Problem

Hello,
I thought log shipping was supposed to be so strait forward and easy! Does n
ot appear to be a reliable fail-over or "warm standby" solution.
After setting up log shipping I have four databases that continue to try an
load the first_file_000000000000.trn log, that is created when the plan is f
irst initialized. It happens even though the backup/copy/loads are functioni
ng successfully and accordi
ng to the plan schedule, and this initial file doesn't even exist in the des
ignated share because it's been deleted according to the log retention sched
ule. What else should I have expected form Bill and the bunch....Anyway, h
ere is the error: It's like
..tell me something I don't know, like why is this happening!
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft]&#
91;ODBC SQL Server Driver][SQL Server]The log in this backup set begins
at LSN 33000000022600001, which is too late to apply to the database. An ear
lier log backup that includes LSN 330000000
11800001 can be restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is te
rminating abnormally.
Any help anyone can give would be greatly appreciated. Thank you much!
Ren Flotlooks to me like you may be trying to apply a log that is somehow leaving
gaps in the transaction chain.
are you sure that you did not miss a logfile somewhere ?
Non-Logged operations can break your log chain....
Greg Jackson
PDX, Oregon