It could be that you have network latency, so the time it takes to copy a tranlog file could exceed the interval that you have set for the copies. 

Try...

Probe uses sql-authenticated account.  I actually had to resync again yesterday, WITH a remove/recreate of log-shipping (side note: I changed dump directory names on the primary, and modfied the logshipping...

I have the same issue.  Databases are in sync primary -> log-shipped copy & there are no failures of copy/restore on the target.  If you look at properties, you can...

Did you check that the account used to start the SQL Server service is a local admin?

Yes, thanks for your note.  However, if you refer to my original posting, you will notice that I did execute sp_repldone with success.  The information & string was in BOL; but,...

FYI:  sp_detach_db followed by sp_attach_single_file_db (removing the .ldf in between) appears to be the only way to resolve this, following results of a google search. 

The bug is SQL2K, and supposedly...

Have you thought about simply disabling the log-shipping copy & restore jobs (at the primary and secondary sites, respectively) + the monitoring for those jobs, then bringing the databases online at...

Are you using the virtual server/instance name when accessing the cluster as opposed to the physical node?

Also, the ODBC DSN settings need to be identically created on each physical node of the cluster a,b.

Well, I have always believed that the best managers are hands-on, at the frontline, and not only assigning on-call, but participating as well.  The only way that one can know what...

Nice -- long -- email, but it struck me as more than a little self-serving, particuarly since you had one foot out the door already. 

If you were working in...

This is just an observation, but wouldn't you prefer to be awake and check that the installation was successful and the instances recovered correctly following the server reboot? 

Create table with index, then bcp (export/import); however, the bcp process will take *much* longer.

It is more efficient to create the tables afterwards.

Bulk-copy into new tables (no indexes), and then create the indexes following.

Try copying the files and restoring them at a 2 hr. interval (to correspond to the tranlog dump) so that the timestamps are maintained in sequence?  We have setup DR using log-shipping...

Save a copy of combolists_unique somewhere, drop it & then drop duplicate_in_combolists. 

Modify the stored proc to remove the referenced dependency (or fix up the table and recreate it), then...