Log Shipping Error

Log Shipping is not replication in the immediate sense, but it is as close as I could find in this set of forums. If there is a better place for this question, please direct me to it.

I am trying to set up Log shipping on two new servers, one is primary and the other is backup. I have made sure that the SQL Startup Login is the same name and password on both servers, and that it has all administrative permissions. When I try to set up Log Shipping, after I click the 'Finish' button, I get the following error:

Error 50007: xp_repl_encrypt: Error executing srv_paramsetoutput

I have done a search for this on support.microsoft.com, and on all of Microsoft. I have found nothing on these attempts. I have even Googled it, and have found very limited entries about making sure that the passwords are the same on both machines, etc. I have followed that advice, to no avail.

The two new machines in question are running Windows Adv Server 2000, and are part of a work group, not a domain. They can see each other, and can read / write to each others shared areas (I have verified that the areas for the Log Shipping are shared).

If anyone can shed some light on this, I would be very grateful.

Thanks in advance,

RollinHi Rollin,

Are you using Logshipping in SQl 2005 ?

Thanks
Yunwen|||No, Since SQL 2005 is not even fully out of the box. We will be with SQL 2000 fro some time to come. Since I made the last post, however, we have upgraded the new servers in question to Win Adv Server 2003, instead of 2000, and the Log Shipping error went away. It seems there must have been some windows related problem.

Thanks for your interest.

Rollin|||Thanks Rollin for updating us with this info. Please let us know if there is any further issues with LS in Sql 2005.

Yunwen|||

I am having the same error when I set up log shipping in SQL 2000. Can you share with me the solution?

Thanks,

Jim

|||This problem occurs probably because you are using a password too long for the user
log_shipping_monitor_probe to validate against the monitor server.

In order do despite the problem try to use a single char in the log_shipping_monitor_probe password's. If the problem is resolved you have to find a password with a length up to 8 chars.

I think this is a bug in the log-shipping fo SQL Server 2000 but MS guys can tell us more...