If you encounter problems with log shipping, one solution is to take a fresh backup of the source database and restore it to the secondary server ('reseeding'). This can be done without starting the log shipping process from scratch.

1. Disable the log shipping jobs on the primary and standby servers in SQL Server Management Studio.
2. Remove all transaction log backup files from the network share location.
3. Take a full backup of the source database, and restore it to the destination database either WITH NORECOVERY or WITH STANDBY. This can be done using the SQL Backup Restore wizard. For more information, see Restoring backups.

Reseeding is now complete and the log shipping jobs on both servers can be re-enabled.