469,608 Members | 2,632 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,608 developers. It's quick & easy.

SQL Server Enterprise Manager could not start the service 'MSDTC'

KO
SQL Server Enterprise Manager could not start the service 'MSDTC' on server
'NTAS21'.

1722 - (The RPC server is unavailable)

I Setup A publication on a server called NTAS4D, then Pushed The
Subscription to another server called NTAS21. If I configure so that the
changes at the subscriber are not replicated to the publisher, all works ok,
I make a change at the publisher, it is replicated to the subscriber.

If I configure for updating at the subscriber, I am presented with a screen
stating that the following services must be started for replication to work:

SQL Server Agent on NTAS4D - Running
MSDTC on NTAS4D - Running
MSDTC on NTAS21 - Unknown

When I complete the wizard, I receive the message listed above.

The Servers are in two separate locations, each behind a NAT enabled router
using the internet to transfer data between the publisher and subscriber.

Any Suggestions will be greatly appreciated.
Thanks
Steve
Jul 20 '05 #1
1 7994
"KO" <no****@anyplace.com> wrote in message news:<bf**********@ngspool-d02.news.aol.com>...
SQL Server Enterprise Manager could not start the service 'MSDTC' on server
'NTAS21'.

1722 - (The RPC server is unavailable)

I Setup A publication on a server called NTAS4D, then Pushed The
Subscription to another server called NTAS21. If I configure so that the
changes at the subscriber are not replicated to the publisher, all works ok,
I make a change at the publisher, it is replicated to the subscriber.

If I configure for updating at the subscriber, I am presented with a screen
stating that the following services must be started for replication to work:

SQL Server Agent on NTAS4D - Running
MSDTC on NTAS4D - Running
MSDTC on NTAS21 - Unknown

When I complete the wizard, I receive the message listed above.

The Servers are in two separate locations, each behind a NAT enabled router
using the internet to transfer data between the publisher and subscriber.

Any Suggestions will be greatly appreciated.
Thanks
Steve


Have a look at Q191168 in the Microsoft Knowledge Base - there is a
good section on troubleshooting MSDTC connectivity issues. From your
description, it seems likely that the firewalls are preventing RPC
calls, and this is causing the problem.

Simon
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by David Gray | last post: by
8 posts views Thread by M K | last post: by
1 post views Thread by =?Utf-8?B?QmlsbHkgWmhhbmc=?= | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.