Fixed in Version 5.x of LiteSpeed.
The current LiteSpeed Version is available for download at Quest.com (you’ll need to login in order to access the page). The msi files are specific to 32-bit, 64-bit and 64-bit Itanium, the correct version will be the same as the bit version of your SQL Server and processor version. The release notes are available at the same location
WORKAROUND:
Rerun the Log Shipping Wizard to set up a new plan. If any failures are encountered, the LSTrackingLog from the publisher will contain information for troubleshooting.
Additional Information:
1) SQL Server is started with a domain user account having local administrator privileges on the servers (OS Level) and sysadmin rights on both SQL Servers.
2) If the SQL Servers are in a workgroup, both SQL Servers should be started with Windows user account having same user id and password. Again, they have to have local system administrator privileges on the server(OS Level) and sysadmin right on both SQL Servers.
3) Both servers should be able to see each other. (ping from one server should be able to reach the other server and vice versa)
4) The name of the SQL Server using in connection string should be exactly the same as result returned from 'select @@servername' from Query Analyzer.
5) SQL Server Agent is running.
6) Same version of LiteSpeed Engine has to be Installed on both SQL Server. (use 'master.dbo.xp_sqllitespeed_version' in query analyzer to get the version)
7) Same version of LiteSpeedLocal Database is installed on both servers with same name. (run 'select * from LiteSpeedVersion' in your Local database)
8) There should be a share folder either on the publisher, subscriber or on the network that can be fully manipulated by both SQL Servers (UNC path will be used to access it)
9) The LiteSpeed LogShipping tables and procedures version may not match between publisher and subscriber. The Version may be determined by querying the LiteSpeedLocal LSOptions table (SELECT * from LSOptions). Upgrade both publisher and subscriber to the same version of LiteSpeed. If they are the same, then the configuration might be corrupt. At this point, run the Instance Configuration of LiteSpeed on the Publisher and Subscriber servers.
