Log Shipping problem

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.

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrb
That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:

>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>
|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrbThat config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:

>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb

Log shipping from SQL2000EE SP3 to SP4

Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrbThis is a multi-part message in MIME format.
--090403030908040509010200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug surprises).
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
zrajbun@.hotmail.com wrote:
>Hi,
>Source ==> SQL Server 2000 EE SP3
>Target ==> SQL Server 2000 EE SP4
>Does automated log shipping work for this configuration? Or log
>shipping requires same service pack levels?
>Thanks,
>zrb
>
>
--090403030908040509010200
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>That config should work (although it is preferable to have the same
service pack level on both servers so that if you have to point your
client code at the secondary server there are no post-SP3 bug
surprises).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:zrajbun@.hotmail.com">zrajbun@.hotmail.com</a> wrote:
<blockquote
cite="mid1124169030.671658.100080@.g49g2000cwa.googlegroups.com"
type="cite">
<pre wrap="">Hi,
Source ==> SQL Server 2000 EE SP3
Target ==> SQL Server 2000 EE SP4
Does automated log shipping work for this configuration? Or log
shipping requires same service pack levels?
Thanks,
zrb
</pre>
</blockquote>
</body>
</html>
--090403030908040509010200--|||Thank you Mike. I think I'll go with the same service pack levels,
keeping SP3.
b4n
zrb

Log Shipping Error on SQL 2000 SP4

I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.

Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.

I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!

Please HELP!any hints ? :(|||Just a wild guess... Are you logshipping to the same instance or between to SQL instances? If the latter is the case, have you ran the MS solution on both instances? (just to be sure)