Wednesday, March 21, 2012

Merge Replication Problem with separate Publisher/Distributor

We are trying to setup merge replication using separate servers for the
publication and distribution. The servers are in the same domain. The same
domain account is used oon all servers involved with the replication. The
setup scripts perform the following task:
Distributor (Master db)
sp_AddDistributor
sp_MSupdateAgentType_default @.profile_id = 1
sp_MSupdateAgentType_default @.profile_id = 2
sp_MSupdateAgentType_default @.profile_id = 4
sp_MSupdateAgentType_default @.profile_id = 6
sp_MSupdateAgentType_default @.profile_id = 11
sp_AddDistributionDB
jobs: Agent History Cleanup
DistributionDB Cleanup
Sp_AddDistPublisher @.SecurityMode = 1
@.Trusted = N'False'
@.ThirdParty_flag = 0
do you have a remote distributor?
If not it sounds like your replication setup is not configured correctly.
Remove replication (follow the menu items to disable publishing) and
reinstall it.
"PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
news:%23r2otLqMEHA.2064@.TK2MSFTNGP12.phx.gbl...
> We are trying to setup merge replication using separate servers for the
> publication and distribution. The servers are in the same domain. The same
> domain account is used oon all servers involved with the replication. The
> setup scripts perform the following task:
>
> Distributor (Master db)
>
> sp_AddDistributor
>
> sp_MSupdateAgentType_default @.profile_id = 1
> sp_MSupdateAgentType_default @.profile_id = 2
> sp_MSupdateAgentType_default @.profile_id = 4
> sp_MSupdateAgentType_default @.profile_id = 6
> sp_MSupdateAgentType_default @.profile_id = 11
>
> sp_AddDistributionDB
>
> jobs: Agent History Cleanup
> DistributionDB Cleanup
>
> Sp_AddDistPublisher @.SecurityMode = 1
> @.Trusted =
N'False'
> @.ThirdParty_flag = 0
> .
>
> Jobs: Expired Subscription Cleanup
> Reinitialize subscription having data validation failures
> Replication agent Checkup
> SnapShot
>
>
> Publisher (Master db)
>
> Jobs: Reinitialize subscription having data validation failures
> Replication agent Checkup
>
> sp_AddSubscriber
>
> Server: Msg 14071 Procedure sp_AddSubscriber, line 129 Could not find the
> Distributor or the distribution database for the local server. The
> Distributor may not be installed, or the local server may not be
configured
> as a Publisher at the Distributor
>
>
> E.M. on the distributor list the publisher with out any publications. Line
> 129 of sp_AddSubscriber is sp_HelpDistributor which according to the help
is
> to run only on the distributor, explaining the error. Sp_AddSubscriber is
> supposed to be run on the publisher.
>
> What am I missing?
>
>
> tia
> Paul
>
>
|||We are using a remote distributor. We did not set a password in
sp_adddistributor. In sp_adddistpublisher we tried both trusted and not
trusted. The authentication on all servers is set to Windows only. I noticed
that the distributor_admin account is a SQL Server account. Can this be the
problem? If so, is there a way to get this to run using Windows only?
Paul
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:ujpd7bxMEHA.2484@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> do you have a remote distributor?
> If not it sounds like your replication setup is not configured correctly.
> Remove replication (follow the menu items to disable publishing) and
> reinstall it.
> "PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
> news:%23r2otLqMEHA.2064@.TK2MSFTNGP12.phx.gbl...
same[vbcol=seagreen]
The[vbcol=seagreen]
> N'False'
the[vbcol=seagreen]
> configured
Line[vbcol=seagreen]
help[vbcol=seagreen]
> is
is
>
|||We tried to setup merge replication using the remote distributor through
E.M. and it worked. Then we used the option to generate SQL scripts. When we
ran the scripts, errors were generated. One of the errors was, in one job
only; the server name was used for the server name and the distributor
database name. They were not the same name.
We did find out that the distributor must be using SQL and Windows
authentication. That option along did not get our scripts working. There
must be something subtle that I am missing.
Paul
"PaulW" <MSNewsGroup@.Digi-Sol.com> wrote in message
news:#7OrH#3MEHA.1644@.TK2MSFTNGP09.phx.gbl...
> We are using a remote distributor. We did not set a password in
> sp_adddistributor. In sp_adddistpublisher we tried both trusted and not
> trusted. The authentication on all servers is set to Windows only. I
noticed
> that the distributor_admin account is a SQL Server account. Can this be
the[vbcol=seagreen]
> problem? If so, is there a way to get this to run using Windows only?
>
> Paul
>
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:ujpd7bxMEHA.2484@.TK2MSFTNGP09.phx.gbl...
correctly.[vbcol=seagreen]
the
> same
> The
> the
> Line
> help
> is
>
|||I believe this is because you don't have the addDistributor S.P. being run
on the publisher as well as the distributor. ;)

No comments:

Post a Comment