Log Shipping fails after DB Reindex.

Can anyone help.
I have set up log shipping between two SQL 2000 servers, with no issues. A
job runs on the Primary server to reindex the databases. At this point Log
Shipping Fails, the error massage says that the servers are out of sync.
The log file shows the error
The log in this backup set begins at LSN 202000000017000001, which is too
late to apply to the database. An earlier log backup that includes LSN
20200000
0016800001 can be restored.
Is there a way to reindex the database that does not affect log shipping?
Many thanks in advance
Andy McDonald
MCSA
"Andy McDonald" <Andy McDonald@.discussions.microsoft.com> wrote in message
news:7ED44ADD-C2FF-4E2F-B371-CC3180FC8B8A@.microsoft.com...
> Can anyone help.
> I have set up log shipping between two SQL 2000 servers, with no issues. A
> job runs on the Primary server to reindex the databases. At this point Log
> Shipping Fails, the error massage says that the servers are out of sync.
> The log file shows the error
> The log in this backup set begins at LSN 202000000017000001, which is too
> late to apply to the database. An earlier log backup that includes LSN
> 20200000
> 0016800001 can be restored.
> Is there a way to reindex the database that does not affect log shipping?
It sounds more like somehow you're losing a log backup somewhere along the
line.
reindexing doesn't (or at least shouldn't) affect log-shipping (having just
done this lately).

> Many thanks in advance
> Andy McDonald
> MCSA
|||Greg
The data base is a large one, (about 25 GB) dont know if this helps. but we
only receive the error when re-indexing takes place.
Andy McDonald
MCSA
"Greg D. Moore (Strider)" wrote:

> "Andy McDonald" <Andy McDonald@.discussions.microsoft.com> wrote in message
> news:7ED44ADD-C2FF-4E2F-B371-CC3180FC8B8A@.microsoft.com...
> It sounds more like somehow you're losing a log backup somewhere along the
> line.
> reindexing doesn't (or at least shouldn't) affect log-shipping (having just
> done this lately).
>
>
>
|||Are you 100% certain that you don't set the database to simple recovery mode during reindex?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andy McDonald" <AndyMcDonald@.discussions.microsoft.com> wrote in message
news:695642A8-9954-472D-9C90-ECC295BAB791@.microsoft.com...[vbcol=seagreen]
> Greg
> The data base is a large one, (about 25 GB) dont know if this helps. but we
> only receive the error when re-indexing takes place.
> Andy McDonald
> MCSA
> "Greg D. Moore (Strider)" wrote:
|||Hello
Yes I am sure.
"Tibor Karaszi" wrote:

> Are you 100% certain that you don't set the database to simple recovery mode during reindex?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Andy McDonald" <AndyMcDonald@.discussions.microsoft.com> wrote in message
> news:695642A8-9954-472D-9C90-ECC295BAB791@.microsoft.com...
>
>
|||"Andy McDonald" <AndyMcDonald@.discussions.microsoft.com> wrote in message
news:695642A8-9954-472D-9C90-ECC295BAB791@.microsoft.com...
> Greg
> The data base is a large one, (about 25 GB) dont know if this helps. but
we
> only receive the error when re-indexing takes place.
Very weird. Really sounds like a log is benig lost somewhere along the
line.
Which I had a better answer.
[vbcol=seagreen]
> Andy McDonald
> MCSA
> "Greg D. Moore (Strider)" wrote:
message[vbcol=seagreen]
issues. A[vbcol=seagreen]
Log[vbcol=seagreen]
sync.[vbcol=seagreen]
too[vbcol=seagreen]
shipping?[vbcol=seagreen]
the[vbcol=seagreen]
just[vbcol=seagreen]