SQL Server 无法订阅或远程订阅复制发布？
我有一个主 SQL Server，运行 SQLServer 2000，有两个（理论上）订阅服务器，每个服务器都运行 SQL Server 2005。
其中一个订阅正常，但另一个似乎总是订阅失败，两者都是在尝试设置订阅时发生的从发布者 (SQL2000) 到订阅者 (SQL2005)，以及尝试通过 Server Management Studio 2008 和 SQL Enterprise Manager 将其设置为从订阅者到发布者时
在这两种情况下，发布都是在发布者上创建的，但订阅者上并未创建相应的订阅。
然后，我收到一条错误消息，指出“进程无法连接到订阅服务器 [ServerName]”，并且没有更多活动迹象。登录、权限等都没有问题。 sa 的密码在两台机器上是相同的，在工作的 2005 机器上是不同的。
这是其他人遇到过的问题吗？
编辑：我现在尝试在每台服务器上添加 dbSubscriber 和 dbPublisher 访问帐户，以便它们不会使用“sa”相互登录，但这似乎没有任何区别。
EDIT2：添加推送订阅不会在订阅服务器上创建本地订阅。这是正常现象，还是一切都已经到了崩溃的地步？
I have a main SQL Server, running SQLServer 2000, with two (in theory) subscribing servers, each running SQL Server 2005.
One of these is subscribing fine, but the other always seems to fail subscribing, both when attempting to set up the subscription from the publisher (SQL2000) to the subscriber(SQL2005), and when trying to set it up from the subscriber to the publisher, both via Server Management Studio 2008 and via SQL Enterprise Manager
In both cases, the publication is created on the publisher, but a corresponding subscription is not created on the subscriber.
I then get an error message saying "The process could not connect to Subscriber [ServerName]", and no more sign of activity. There's no problem with logins, permissions, etc. The password for sa is the same on both machines, and is different on the 2005 machine that works.
Is this a problem anyone else has encountered?
EDIT: I've now tried adding both a dbSubscriber and a dbPublisher access account on each server so that they're not logging into each other using "sa", but it doesn't seem to have made any difference.
EDIT2: Adding a push subscription does not create a Local Subscription on the subscribing server. Is this normal, or is this the point at which everything is falling to pieces?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
感谢您发布更新，很高兴知道事情的结果。
正如您所发现的那样，在创建包含不同版本的 SQL Server 的 SQL Server 复制拓扑时，会涉及到“复杂性”和问题。
请记住，复制功能仅限于拓扑中最旧版本的 SQL Server 的功能：
在复制拓扑中使用多个版本的 SQL Server
Thanks for posting an update, always good to know how things turned out.
There are "complications" and intracacies involved when creating SQL Server Replication topologies incorporating different versions of SQL Server, as it sounds like you are discovering.
Keep in mind that Replication functionality is limited to that of the oldest version of SQL Server in your topology:
Using Multiple Versions of SQL Server in a Replication Topology
我们并不真正了解出了什么问题，但我们认为2005 服务器无法接受 2000 服务器作为推送发布者。
我们在 2005 年的服务器上创建了四个不同的 Pull 订阅，前三个失败了，而第四个却神奇地工作了。
我们将此视为计算机之神的祝福，不会质疑他的仁慈。
We don't really understand what was going wrong, but we think that the 2005 server was unable to accept the 2000 server as a Push Publisher.
We created four different Pull subscriptions on the 2005 server and the first three failed, while the fourth magically worked.
We are accepting this as a blessing from the God of Computers and will not question His benevolence.