May 18, 2009 at 5:23 pm
I have been trying to set up replication of a database from a SQL2000 box to a web based SQL2005 instance.
I have sucessfully created the publisher (2000), distributor (2000), created the snapshot, moved the snapshot file manually to the web box, and later configured both the SQL2000 Client Network Utility and the SAC on the 2005 box to allow 1433 connections and can see both server at either end.
Initially I wanted to use replication over HTTP, so installed a local copy of SQL2005 Express and made this a subscriber to the 2000, hoping that I would then be able to replicate to my web based SQL2005 Express edition too. This of course failed as Express dosen't support this replication type (I think - still a little confused about if this is possible). Instead I allowed 1433 and 1434 to be open on my firewall (which I may be now regretting) to connect the servers directly.
All seemed OK, but I still couldn't intialise the subsciption on the web based 2005 instance.
I left the project for a couple of days and then uploaded and installed SQL2005 Enterprise edition (to the web box), re did all the SAC settings etc then came to re-connect to the 2000 box and use the existing snapshot to initialise the subscription.
Now the Log Reader Agent on the SQL2000 box is complaining about xplog70.dll being missing (Error message: Cannot load the DLL xplog70.dll or one of the DLLs it references. Reason 126 )The specified module cannot be found)) and the xp_cmdshell stored procedure also seems to be missing and a vital component of replication.
Does this mean that the 2000 box has been compromised in some way? Can I recover the 2000 box ?
I am at my wits end and have been trying to get this functional for 3 weeks. I am now really concerned that the 200 server (which is managed by a 3rd party) is damaged.
Please help !
Any help / advice would be really appreciated
Alistair
May 19, 2009 at 6:27 am
Check this article:
http://support.microsoft.com/kb/891984
It's not directly related to replication it it should help you to fix the problems.
[font="Verdana"]Markus Bohse[/font]
May 20, 2009 at 4:11 pm
Thanks for the tip.
I have tried the
exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
command, but I end up with an error message:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_addextendedproc'.
I can only assume that a number of sp have been removed on the box. I do not have a backup of the master db, is there any way to reinstate all the standard sp's ???
May 20, 2009 at 5:18 pm
I have managed to re-attach a very (3 years) old copy of master and re-created sp_addextendedproc back in and have managed to get xp_cmdshell back but in the process have come across Backdoor-DUZ trojan on my system.
I am assuming that this hit me whilst port 1433 was open.
So I now have xplog70.dll and xp_cmdshell back but my replicaiton LOg Reader agent still says its missing the file even though it is present in the instance Binn folder.
Any ideas ?
I am stuck with this being a live production server.
Alistair
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply