I have several SQL Server 2000 SP4 instances on Windows 2003 Advanced Server and Datacenter Edition shipping logs to a SQL Server 2000 SP4 instance on Windows 2003 Advanced Server. All of the log shipping pairs work fine except in the case of one instance. When I set up a log shipping pair from it, the maintenance plan, jobs and entries in the system tables are created successfuly, the initial database (which is small in my example) is backed up as part of the log shipping setup, copied to the secondary server and restored. But when the "copy" job executes in the secondary server, it doesn't copy the transaction log backups from the backup server. Other log shipping pairs established from other primaries to this secondary server work fine, so I know it is not a communications problem between this particular primary and the secondary server. The "copy" job indicates that it succeeds, but it doesn't do anything. I use LiteSpeed 2005 both on the primaries and on the secondary server. In the secondary server I have LiteSpeed's NCS (Native Command Substitution) installed, since the Log Shipping maintenance plans cannot be converted to LiteSpeed. Again, this works fine for all other instances. The configuration settings of the problematic primary are analogous to the configuration settings of the other instances. Log shipping used to work from the problematic primary to other secondary server, but not now. I suspect that this has something to do with inconsistencies in some system tables in the primary server. Has anyone a hint to offer?
If you are using the third party tool, have you contacted the vendor in first place.
If it is a SQL Server log shipping, then I would suggest to check SQL error log and event logs on both the servers to ensure there is no issue with SQL components, also you might take help of network admin to see why this is happenning with a network trace etc.
