Re: SQL Server 7.0 Publisher/Distributor to SQL Server 2000 Subscriber
Have you checked if your server(s) are properly declared in the MDAC?
Their alliases should be listed in the Client Network Utility found in the SQL program utilities in your start menu.
Dont use IP numbers if u can and try to keep names short and without underscores etc.
Originally posted by mice Not working
when i try sql server 2000 as pull subscriber, i cannot find the publisher in sql server 7
SQL Server 7.0 Publisher/Distributor to SQL Server 2000 Subscriber
We never use Pull subscription as a rule but normally spoken that shouldn't present a problem. What needs to be done is to check with the program "Client Network Utility" (in the tools of mssql7) on your Server which is configured as Distributor (and generally as your publisher) if the other machine is known under a "regular" name.
What i mean by "regular" is something like "REMPCSUBS1" for example.
In tne C.N.U. you open up the tab Alias and there you can configure a specific Alias for a pull subscriber in your case something like:
Server name: 220.127.116.11 (This is only an example)
Use dynamic port
Select TCP/IP protocol
Sometimes it helps to switch places between IPnumber and alias (e.g. servername REMPCSUB1, alias 18.104.22.168) I never figured out completely why that's the case, i suppose it's a typical "microsoft quirk".
Give the Distributor about 5 minutes "rest" and then try to configure the other machine as a Pull subscriber from the Distributor.
You HAVE to make sure you use the right username/password combinations for the distributor, the publisher and the subscriber.
As a test i suggest you use as much as possible the SAME name/password first, on all machines and processess, giving it as much rights as possible. Once you got everything working, "tune down" the rights given until it still works but is safe to use in a daily environment.
Don't forget that the replication agent needs to be started up under a Domain user name which has administrator rights !! on the distributor / publisher. This is important, for at certain steps , while configuring replication, you might have to "impersonate" this domain user.