Log Shipping restore failing

I have a log shipping configuration set up that has been working for several weeks now. Last night starting at about 12:30 am the restore job has started failing periodically. It has gotten worse as the day has gone on, and the job history shows the same
error message each time it fails.
Executed as user: PROMAXONLINE\svcsql. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Can anyone tell me what this means? I am aware of the problem of nameing a directory with a -S in the name, and this is not the case here.
TIA,
Ken
Right-click on the maintenance plan name (not the SQL Agent Job) and select
Maintenance Plan History... for a more detailed error message.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Ken Krause" <anonymous@.discussions.microsoft.com> wrote in message
news:E8A88DA1-CAAA-45DB-A063-A4D5315D20F0@.microsoft.com...
> I have a log shipping configuration set up that has been working for
several weeks now. Last night starting at about 12:30 am the restore job has
started failing periodically. It has gotten worse as the day has gone on,
and the job history shows the same error message each time it fails.
> Executed as user: PROMAXONLINE\svcsql. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed.
> Can anyone tell me what this means? I am aware of the problem of nameing
a directory with a -S in the name, and this is not the case here.
> TIA,
> Ken
|||I have since found out that running indexing operations on the database while the log shipping file is being created can cause this problem, and that's exactly what happened. My next question is how do I get past a corrupted transaction log file without s
crewing up the whole chain of transaction logs? The rest are stacking up behind it every 15 minutes because this one log file won't restore.
Thanks,
Ken
|||Since the log sequence is broken, you will likely have to re-initialize log
shipping with a full backup-restore.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Ken Krause" <anonymous@.discussions.microsoft.com> wrote in message
news:DC38D04C-0745-400C-8F83-290F3EF46369@.microsoft.com...
> I have since found out that running indexing operations on the database
while the log shipping file is being created can cause this problem, and
that's exactly what happened. My next question is how do I get past a
corrupted transaction log file without screwing up the whole chain of
transaction logs? The rest are stacking up behind it every 15 minutes
because this one log file won't restore.
> Thanks,
> Ken