replication timeout

I have 3 production machines which are replicated to a dr site, all
machines are using a central distributor machine. I have created a
separate distributor database for each system.
My problem is that one of my systems will not replicate I am doing
snapshot and transactional, it just keeps timing out I have put sql
profiler on the dr box and can see that the data gets to the box but
it just times out. All boxes publisher, distributor, subscriber can
see each other so why is it timing out?
what is the exact error message you are getting?
"stephen" <twolf@.icon.co.za> wrote in message
news:75c81dee.0404170439.22bbd18d@.posting.google.c om...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?
|||Have you looked into creating a different snapshot profile?
If you go into Publisher/Distributor Properties, Agent Profiles, and
then Snapshot Tab, If you look at the existing "Default profile" the
Query time-out is set to 300; you might want to increase that number
to maybe 1000 or so.
Here is something that I have found interesting though that you might
want to know ahead of time so you DON'T CANCEL the replication
process:
Depending on how high you increase this number to, there is always the
potential of getting a somewhat bizare error message while the
replication is running stating that no response has been received from
the snapshot agent, and the Replication monitor will display the red X
symbols (like if it had failed). However, the process is still alive
and well (you can check it under jobs to see if it is still in fact
running), so once it goes past the table that may be causing it to
time-out, the Replication monitor will refresh and the Xs will be
removed.
Try this on a test environment first as every environment reacts
diferently, and always remember to keep a current backup just in case.
Hope this helps.
Jose
twolf@.icon.co.za (stephen) wrote in message news:<75c81dee.0404170439.22bbd18d@.posting.google. com>...
> I have 3 production machines which are replicated to a dr site, all
> machines are using a central distributor machine. I have created a
> separate distributor database for each system.
> My problem is that one of my systems will not replicate I am doing
> snapshot and transactional, it just keeps timing out I have put sql
> profiler on the dr box and can see that the data gets to the box but
> it just times out. All boxes publisher, distributor, subscriber can
> see each other so why is it timing out?

Replication Subscription Error

Hi,
I tried setting a server up as the publisher, distributor and subscriber.
When I tried to create either a push or pull subscription I got the following
message:
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
SQL Server Enterprise Manager could not create a pull subscription to
publication XXXX
Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one
of the DLLs it references. Reason: 126(error not found).
The subscription could not be updated at this time.
The subscription could not be created.
Has anyone seen this before?
Server running SQL 2000 on Windows 2000 Server
Thanks
Something is not installed correctly. Reapply your latest service pack.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DavidW" <DavidW@.discussions.microsoft.com> wrote in message
news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
> Hi,
> I tried setting a server up as the publisher, distributor and subscriber.
> When I tried to create either a push or pull subscription I got the
> following
> message:
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> SQL Server Enterprise Manager could not create a pull subscription to
> publication XXXX
> Error 14053: Cannot load the DLL replincrementlsn extended procedure, or
> one
> of the DLLs it references. Reason: 126(error not found).
> The subscription could not be updated at this time.
> The subscription could not be created.
> Has anyone seen this before?
> Server running SQL 2000 on Windows 2000 Server
> Thanks
>
|||Thank you Hilary, that has resolved the problem!
"Hilary Cotter" wrote:

> Something is not installed correctly. Reapply your latest service pack.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "DavidW" <DavidW@.discussions.microsoft.com> wrote in message
> news:895B9996-9D97-4CAA-84F2-FF314F842E6F@.microsoft.com...
>
>

Replication Stops at distributor in some cases

Hi,
I recently had a problem with a merge replication publication. In
some cases when data is changed on a subscriber, the change gets back
to the publisher but does not replicate from the publisher to the rest
of the subscribers. I checked the conflict viewer and there are no
conflicts. I am running SQL Server 2000 and I was wondering if anyone
is familiar with this problem.
Thanks,
Paul
Are you using any sort of filtering? This might account for this behavior.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul T." <weluvpaul@.hotmail.com> wrote in message
news:1fe3e09e.0408091019.79d49cf2@.posting.google.c om...
> Hi,
> I recently had a problem with a merge replication publication. In
> some cases when data is changed on a subscriber, the change gets back
> to the publisher but does not replicate from the publisher to the rest
> of the subscribers. I checked the conflict viewer and there are no
> conflicts. I am running SQL Server 2000 and I was wondering if anyone
> is familiar with this problem.
> Thanks,
> Paul
|||I do have some row filters on but none that comes into play in this
particular situation.
|||Can you give us some more details about this topology? How many subscribers,
etc.
I have tried to repro this on a local server with two subscribing database
and can't get the expected behavior. IE an update on Subscriber1 makes it to
the publisher and Susbcriber2. Same with updates on Susbcriber2.
Also can you query the conflict tables directly on the Publisher and
subcriber just to verify the conflict viewer is correct.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul T." <weluvpaul@.hotmail.com> wrote in message
news:1fe3e09e.0408120524.77f6d0ca@.posting.google.c om...
> I do have some row filters on but none that comes into play in this
> particular situation.
|||This publication has 12 subscribers (push subscriptions) that resync
every 2 hours. They are staggered to run 5 minutes apart. This only
happens with one particular table and I think it is perhaps a bug that
is just not listing the conflict. So far I have determined that this
happens when a personnel record is update on two different
subscribers. The only thing is in this case the fields being updated
on the two different subscribers do not overlap. So there should not
be any conflicts, and none of them are showing up in the conflict
manager. I also queried the conflict table and there were no rows in
there.
For example:
Field a and b are changed on subscriber X
Field d and c are changed on subscriber Y
publisher resyncs with X and gets the changes to field a and b
publisher resyncs with Y and gets changes to field d and c but does
update
Y with the changes from X.
I hope this helps, I am currently trying to reproduce this to have get
a more detailed version of what is going down. Thank you very much
for your help Hilary, it is appreciated.

Replication sometimes does not delete all records

Hi all,
I have a following problem with my replication.
I have 3 machines - 1 is publisher and its own distributor, and two are
subscribers. The replication topology model is "central publisher".
The problem concerns the merge replication with filtering (filter is
"2=1"). This replication should take any records inserted into
replicated tables on subscribers and copy them to main server (typical
merge process for new entries). Received rows are checked against the
filter condition and are immediately deleted on subscribers because the
"2=1" condition is impossible.
This is working fine, but sometimes it happens that some rows are not
deleted on subscribers. They are copied properly, but sometimes you can
see the situation when there was 15371 inserts and 15270 deletes. They
are not taken into consideration during the next replication (they are
just left, cluttering the tables on subscribers).
All machines working on sql server 2k with sp2.
Did someone encountered such behaviour? I'm new to replication and I
don't know what can I do to analyse what's going on.
Regards
Xavier
Does anything show up in the conflict viewer?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||> Does anything show up in the conflict viewer?
No, there are no conflicts shown. There are no errors either. Everything
goes smooth (with one exception).
Regards
|||I'd run a validation to verify everything is working fine.
The record being uploaded/downloaded is likely a metadata record for the system tables.
I am perplexed by your filter. If you are filtering updates coming from your subscriber you are also filtering going to your publisher which begs the question - why are you replicating this table?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||> I am perplexed by your filter. If you are filtering updates coming from your subscriber you are also filtering going to your publisher which begs the question - why are you replicating this table?
the task i want to achieve is to move the data from distributed machine
to one central server. is there something i missed?
sql

replication set-up stored procedures

Hello everyone,
I have two questions:
1. about sp_adddistributor - in the case when a remote distributor is being
used does it have to be run both at the publisher and at the distributor?
2. about sp_addsubscriber - where does it fit in the chain of replication
setup SPs? I have this sequence so far:
sp_adddistributor (@.distributor)
sp_adddistributiondb (@.distributor)
sp_adddistpublisher (@.distributor/@.publisher)
sp_replicationdboption (@.publisher)
sp_addpublication (@.publisher)
sp_addarticle (@.publisher)
sp_addsubscriber (@.publisher) is this the right point of execution?
sp_addsubscription (@.publisher)
thanks in advance
sp_adddistributor is run only on the distributor. You have a correct
placement for the add subscriber statement, but really it can be run anytime
after the distributor is created.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MorDeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
news:E505E5B2-6FDD-46A1-8D40-CD2D241A4B5C@.microsoft.com...
> Hello everyone,
> I have two questions:
> 1. about sp_adddistributor - in the case when a remote distributor is
> being
> used does it have to be run both at the publisher and at the distributor?
> 2. about sp_addsubscriber - where does it fit in the chain of replication
> setup SPs? I have this sequence so far:
> sp_adddistributor (@.distributor)
> sp_adddistributiondb (@.distributor)
> sp_adddistpublisher (@.distributor/@.publisher)
> sp_replicationdboption (@.publisher)
> sp_addpublication (@.publisher)
> sp_addarticle (@.publisher)
> sp_addsubscriber (@.publisher) is this the right point of execution?
> sp_addsubscription (@.publisher)
> thanks in advance
>
|||Hi Hilary,
I'm glad you picked up on this question. My confusion started from comparing
the EM generated scripts to the setup procedures described in your book where
I could not find the add subscriber stored procedure.
also, do I have to run grant access statements, or is there a default set of
rights that gets assigned to these objects that could be good enough?
Thanks
Mor
"Hilary Cotter" wrote:

> sp_adddistributor is run only on the distributor. You have a correct
> placement for the add subscriber statement, but really it can be run anytime
> after the distributor is created.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "MorDeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
> news:E505E5B2-6FDD-46A1-8D40-CD2D241A4B5C@.microsoft.com...
>
>

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon Shargorodsky
Run stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky
|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:

> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> exist
> get
>
>
|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"[vbcol=seagreen]
> "Mike Wengler" wrote:
problem.[vbcol=seagreen]
in[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]
|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:

> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> replication"
> problem.
> in
> I
> the
>
>

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon ShargorodskyRun stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:
> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > I have disabled publisher, distributor and subscriber; no publications
> exist
> > on publisher. However, when I try to alter a table on former publisher I
> get
> > this error:
> >
> > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the
> > table 'dbo.MAIN' because it is being used for replication.
> >
> > Please help, thank you in advance for your time!
> >
> > Leon Shargorodsky
>
>|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"
> "Mike Wengler" wrote:
> > Run stored proc sp_removedbreplication and see if that fixes your
problem.
> >
> > Mike
> >
> > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
in
> > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > I have disabled publisher, distributor and subscriber; no publications
> > exist
> > > on publisher. However, when I try to alter a table on former publisher
I
> > get
> > > this error:
> > >
> > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
the
> > > table 'dbo.MAIN' because it is being used for replication.
> > >
> > > Please help, thank you in advance for your time!
> > >
> > > Leon Shargorodsky
> >
> >
> >|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:
> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> > No, I'm still getting the same error: "table is being used for
> replication"
> >
> > "Mike Wengler" wrote:
> >
> > > Run stored proc sp_removedbreplication and see if that fixes your
> problem.
> > >
> > > Mike
> > >
> > > "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote
> in
> > > message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> > > > I have disabled publisher, distributor and subscriber; no publications
> > > exist
> > > > on publisher. However, when I try to alter a table on former publisher
> I
> > > get
> > > > this error:
> > > >
> > > > ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop
> the
> > > > table 'dbo.MAIN' because it is being used for replication.
> > > >
> > > > Please help, thank you in advance for your time!
> > > >
> > > > Leon Shargorodsky
> > >
> > >
> > >
>
>

Replication question - unable to modify table

I have disabled publisher, distributor and subscriber; no publications exist
on publisher. However, when I try to alter a table on former publisher I get
this error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Canno
t drop the
table 'dbo.MAIN' because it is being used for replication.
Please help, thank you in advance for your time!
Leon ShargorodskyRun stored proc sp_removedbreplication and see if that fixes your problem.
Mike
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> I have disabled publisher, distributor and subscriber; no publications
exist
> on publisher. However, when I try to alter a table on former publisher I
get
> this error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]Can
not drop the
> table 'dbo.MAIN' because it is being used for replication.
> Please help, thank you in advance for your time!
> Leon Shargorodsky|||No, I'm still getting the same error: "table is being used for replication"
"Mike Wengler" wrote:

> Run stored proc sp_removedbreplication and see if that fixes your problem.
> Mike
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:37DFDC3E-7435-456E-A137-D94EDFED5915@.microsoft.com...
> exist
> get
>
>|||NOT RECOMMENDED Under normal circumstances only after trying ALL other
solutions . . but I have had this problem resolved in the past by reseting
the value in replinfo column in sysobjects to 0.
HTH
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> No, I'm still getting the same error: "table is being used for
replication"[vbcol=seagreen]
> "Mike Wengler" wrote:
>
problem.[vbcol=seagreen]
in[vbcol=seagreen]
I[vbcol=seagreen]
the[vbcol=seagreen]|||THANK YOU SO MUCH! It worked!!!
"Olu Adedeji" wrote:

> NOT RECOMMENDED Under normal circumstances only after trying ALL other
> solutions . . but I have had this problem resolved in the past by reseting
> the value in replinfo column in sysobjects to 0.
> HTH
>
>
> "Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
> message news:8460093D-8C06-43AD-964B-06592F231ADE@.microsoft.com...
> replication"
> problem.
> in
> I
> the
>
>

Replication Problem, Please Urgent Help!

Hello Guys,
I have set up a transactional replication with 2pc's.
One server is the publisher & the distributor, and the other one is the
subscriber.
Everything is fine, but the replication stops when my partner shut down
the subscriber pc, now I have to restart the replication, but I don't
know how to do it because I tried to restart the agents and it didn't
work.
Which agent is supossed to be restarted?.
Thanks,
*** Sent via Developersdex http://www.codecomments.com ***
Javier,
you'll need to restart the distribution agent. If it generates an error,
this might be because of the distribution retention period being exceeded.
Please can you post up any errors you see and we'll work it out.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Problem where Distributor & Subcriber on same machine

What I would like to do is set up transactional replication from server1 (Publisher) to server2 (Subscriber), with server2 acting as the (Distributor).

I am successful on server2 in allowing server2 as a distributor for server1. When I try to configure replication on server1 to use server2 as a distributor and subscriber I get this message once

"
SQL Server Enterprise Manager could not enable 'server2' as a Subscriber.

Error 14071: Could not find the Distributor or the distribution database fom the local server. The Distributor may not be installed, or the local server may not be configured as a Publisher at the Distributor.
"

and this mesage for each database I enable for subscription, I get this message.

"
SQL Server Enterprise Manager could not enable database 'x' for snapshot or transactional replications.

Error 20028: The Distributor has not been correctly installed. Could not enable database for publishing. The replication 'publish' of database 'x' has been set to false.
"

The last message I get is

"
SQL Server Enterprise Manager successfully enabled 'server2' as the Distributor for 'server1'.
"

This message is apparently false.

When I try to Configure Publishing, Subscribers and Distributing... on server1, I get the message

"
SQL Server Enterprise Manager could not retrieve information about the Distributor or the distribution database.
"

In an attempt to fix this I:
1. disable publishing on server1,
2. disable publising and distribution on server2.
3. enable publishing and distribution on server2.
4. enable publishing on server1 using server2 as distributor.

Again I get errors on step 4.

I have even tried re-installing SQL Server 2000 on server2 with no improvement.

Can some one please shed some light on this problem?

Thanks in advance.Connect to the SQL Server using Query Analyzer and run the following query: select @.@.servername.

If it returns NULL you will need to run the sp_addserver procedure to get
the internal server name correct. You may need to run sp_dropserver as
well. These are documented in Books on Line.

A NULL server name can cause wierd behavior with replication.|||I do have a NULL server name problem. I have run the sp_dropserver, sp_addserver and have retarted SQL Server.

I have tried again to create the replication & it now WORKS!

Satya, thanks soooo much for you help!

Replication Problem

I don't know if anyone can help with this, I've got replication running
between 2 SQLServer installations, the distributor is on the the same
server as subscriber. Replication is a once a day snapshot and all has
been working well until recently.

I needed to make a change to the replication and deleted and recreated
the subscription and now it doesn't work. The snapshot runs as before
but the subscription fails within a second or 2 with the following error:

"The process could not retrieve security information from the Subscriber
for Distributer 'MIServer'. The step failed."

The only thing I could think of was that somehow the password for the
'distributor_admin' login had become out of step. I've run
'sp_changedistributor_password' and the subscription still fails.

Any help would be appreciated.

TIA

Laurence Breeze"Laurence Breeze" <laurence_breeze@.yahoo.co.uk> wrote in message
news:4240096D.2000305@.yahoo.co.uk...
>I don't know if anyone can help with this, I've got replication running
>between 2 SQLServer installations, the distributor is on the the same
>server as subscriber. Replication is a once a day snapshot and all has
>been working well until recently.
> I needed to make a change to the replication and deleted and recreated the
> subscription and now it doesn't work. The snapshot runs as before but the
> subscription fails within a second or 2 with the following error:
> "The process could not retrieve security information from the Subscriber
> for Distributer 'MIServer'. The step failed."
> The only thing I could think of was that somehow the password for the
> 'distributor_admin' login had become out of step. I've run
> 'sp_changedistributor_password' and the subscription still fails.
> Any help would be appreciated.
> TIA
> Laurence Breeze

It sounds rather similar to this KB article:

http://support.microsoft.com/?id=312106

But you might get a better response in
microsoft.public.sqlserver.replication.

Simon

Replication Problem

I am settng up a Distributor, Publisher and Publication. The subscriber will be enabled later.
A1 is the Distributor
A2 is the Publisher
I configureed A1 as Distributor and enter a password for A2 to use when connecting.
Then, I enabled A2 to be a Publisher.
When I try to create the Publication on A2, I get the following error:
Error 20028: The Distributor has not been installed correctly. Could not enable database for publishing. The replication option 'publish' of database 'dbname' has been set to false.
As a test, I enabled my local SQL Server to be a Publisher using the Distributor and it works fine.
Both A1 and A1 have SQL Services under the same domain admin. From A2, I can see the snapshot folder on the Distributor.
Could someone provide some insight into this?
Thank you in advance.
Robert M.
Thanks to those who read this...I kept at it. Did a select @.@.servername and it was null on the Publisher. Ran sp_addserver 'a2', 'local' and restarted the services.
Now I can create the Publication.
Robert M.
"Robert M." wrote:

> I am settng up a Distributor, Publisher and Publication. The subscriber will be enabled later.
> A1 is the Distributor
> A2 is the Publisher
> I configureed A1 as Distributor and enter a password for A2 to use when connecting.
> Then, I enabled A2 to be a Publisher.
> When I try to create the Publication on A2, I get the following error:
> Error 20028: The Distributor has not been installed correctly. Could not enable database for publishing. The replication option 'publish' of database 'dbname' has been set to false.
> As a test, I enabled my local SQL Server to be a Publisher using the Distributor and it works fine.
> Both A1 and A1 have SQL Services under the same domain admin. From A2, I can see the snapshot folder on the Distributor.
> Could someone provide some insight into this?
> Thank you in advance.
> Robert M.
>
>

Replication Problem

I am settng up a Distributor, Publisher and Publication. The subscriber wil
l be enabled later.
A1 is the Distributor
A2 is the Publisher
I configureed A1 as Distributor and enter a password for A2 to use when conn
ecting.
Then, I enabled A2 to be a Publisher.
When I try to create the Publication on A2, I get the following error:
Error 20028: The Distributor has not been installed correctly. Could not e
nable database for publishing. The replication option 'publish' of database
'dbname' has been set to false.
As a test, I enabled my local SQL Server to be a Publisher using the Distrib
utor and it works fine.
Both A1 and A1 have SQL Services under the same domain admin. From A2, I ca
n see the snapshot folder on the Distributor.
Could someone provide some insight into this?
Thank you in advance.
Robert M.Thanks to those who read this...I kept at it. Did a select @.@.servername and
it was null on the Publisher. Ran sp_addserver 'a2', 'local' and restarte
d the services.
Now I can create the Publication.
Robert M.
"Robert M." wrote:

> I am settng up a Distributor, Publisher and Publication. The subscriber w
ill be enabled later.
> A1 is the Distributor
> A2 is the Publisher
> I configureed A1 as Distributor and enter a password for A2 to use when co
nnecting.
> Then, I enabled A2 to be a Publisher.
> When I try to create the Publication on A2, I get the following error:
> Error 20028: The Distributor has not been installed correctly. Could not
enable database for publishing. The replication option 'publish' of databa
se 'dbname' has been set to false.
> As a test, I enabled my local SQL Server to be a Publisher using the Distr
ibutor and it works fine.
> Both A1 and A1 have SQL Services under the same domain admin. From A2, I
can see the snapshot folder on the Distributor.
> Could someone provide some insight into this?
> Thank you in advance.
> Robert M.
>
>

Replication over WAN setup

Hello, I'm newbie in replication field. At the moment, I am able to setup replication on LAN (1 distributor to few subcribers). However, I found some difficulties on setting-up the replication on WAN. Is there any guidelines, setup documents or examples (like print screen) for me to refer to ? Hope able to get any assistance at here.

Best Regards,

Hans

Hello Hans,

What kind of difficulties did you see? Can you list them?

Thanks.

|||

are you replicating between two different domains? If so, please reference this support article: http://support.microsoft.com/kb/321822/en-us.

If not, please give us some more info, such as complete error number and error message.

|||

First define if the problem is the network connection (routing, firewall, e.t.c.)

Then if it is a security problem (different domains without trust, accounts with improper rights, wrong passwords, e.t.c.)

Lastly if it is a SQL config problem (e.g. are you running the SQL service with the SA account?)

Can you give more details?

|||

Sorry for the late reply guys, I guess I just figure out my problem. For WAN setup, wat I need is have to do some alias mapping for the server that I wanna connect (subscriber or publisher server). Once did the mapping , replication is able to run. :) Thx for the advice by the way.

Best Regards,

Hans

replication not working

I set up a transactional, pull publisher, distributor and subscriber last
week on a development system and all worked fine. Then, I did the same set
up on our production system and it is not working. When this was started on
Thursday night the distributor would not start. I was not here Friday so my
boss stopped replication and I did not see the error messages. I set up a
new replication subscriber last night and it looks like it did not
synchronize though I saw transactions going from the publisher to
distributor, but nothing going from the distributor.
I look in the log file viewer and see no error messages. My guess is that
the distributor is not running but I don't know how to see if it is.
I thought that I did everything the same on the production set up that I did
on development, that worked.
TIA - nick
Nick - can you run the distribution agent from EM/SSMS and then post up the
messages you get. Also, what version of sql server are you using and are you
using updatable subscribers - it's not entirely clear from the description.
If updatable subscribers, is data being prevented from flowing in either
direction?
Just a simple check would be to see if the tables are there on the
subscriber (assuming they weren't there originally!) - this means
initalization has worked and the distribution agent has worked at least once.
If SQL Server 2005 you can use a trace flag to test the throughput is working.
HTH,
Paul Ibison
|||Paul,
Thanks for the quick response.
I don't know how to "run distribution from SSMS and then post up the
messages". I'm new to all this.
My publisher is SS 2000; the distributor and subscriber are 2005. I am not
doing updatable subscribers.
I starting from a subscriber database that is a previous backup of the
publisher. I look to see if the record counts, dates, etc. have changed as
they should and they have not.
How do I use this trace flag?
thanks - nick
"Paul Ibison" wrote:

> Nick - can you run the distribution agent from EM/SSMS and then post up the
> messages you get. Also, what version of sql server are you using and are you
> using updatable subscribers - it's not entirely clear from the description.
> If updatable subscribers, is data being prevented from flowing in either
> direction?
> Just a simple check would be to see if the tables are there on the
> subscriber (assuming they weren't there originally!) - this means
> initalization has worked and the distribution agent has worked at least once.
> If SQL Server 2005 you can use a trace flag to test the throughput is working.
> HTH,
> Paul Ibison
|||One thing to add that does look suspicious ... If I right-click on the
subscriber and select View Sync Status, the status window comes up and the
status message reads "The job succeeded ..." nad Start button is enabled. If
I click on View Job History, when the Log Viewer comes up, under Progress it
says Login failed for user 'sa'.
- nick
"Paul Ibison" wrote:

> Nick - can you run the distribution agent from EM/SSMS and then post up the
> messages you get. Also, what version of sql server are you using and are you
> using updatable subscribers - it's not entirely clear from the description.
> If updatable subscribers, is data being prevented from flowing in either
> direction?
> Just a simple check would be to see if the tables are there on the
> subscriber (assuming they weren't there originally!) - this means
> initalization has worked and the distribution agent has worked at least once.
> If SQL Server 2005 you can use a trace flag to test the throughput is working.
> HTH,
> Paul Ibison

Replication Montor 2005

Is there any way to configure repl. monitor in 2005 to view all the publications that go
via a distributor in one place? (as opposed to having to link to each publisher to see the replictaion status).

we have 7 publishers going throigh one distributor and in 2000 could see them all on the distributor...now have to connect to each publisher & look on each...

Thanks

DesX

This is a design change in SQL 2005 (largely based on customer feedback), and there's no way to accomplish what you want with the given tools.

However if you want to build your own tool, you can. SQL Monitor is built around proc sp_replmonitorpublication, which has parameter @.publisher. If NULL, you get everything back for the given distributor.

Replication Monitor disappears

All,
I have setup transactional replication in our dev environment with
publisher, distributor and subscriber on same box for testing and it was
running fine for some time. When I was setting up replication I had SQL
Service logged on using local system account and sql agent login was dev
admin account.
Yesterday when we have restarted the server, sql service came fine but SQL
Agent did not start. when I tried to start agent it manually it errored
saying login donot have permissions.
When I have checked Agent login, its using same dev admin login which should
have all permissions. Finally I was able to start the SQL Agent service by
retyping dev admin and password from services.
This time though SQL Agent started Replication monitor disappeared from
Enterprise manager. Any suggesstions why it happened..?
This could be a rights issue. Connect to the problem server using the sa
account and see if it shows up.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SQL Replicatio Guy" <SQL Replicatio Guy@.discussions.microsoft.com> wrote in
message news:F6019804-2776-4532-836D-C51156354A45@.microsoft.com...
> All,
> I have setup transactional replication in our dev environment with
> publisher, distributor and subscriber on same box for testing and it was
> running fine for some time. When I was setting up replication I had SQL
> Service logged on using local system account and sql agent login was dev
> admin account.
> Yesterday when we have restarted the server, sql service came fine but SQL
> Agent did not start. when I tried to start agent it manually it errored
> saying login donot have permissions.
> When I have checked Agent login, its using same dev admin login which
should
> have all permissions. Finally I was able to start the SQL Agent service by
> retyping dev admin and password from services.
> This time though SQL Agent started Replication monitor disappeared from
> Enterprise manager. Any suggesstions why it happened..?
>
>
|||Yes, I am sure its rights issue but not sure why my replication monitor did
not come up after I have started the SQL Agent service with dev admin account.
FYI If it helps-
SQL Agent started only when I have retyped dev admin and password.
Regards
"Hilary Cotter" wrote:

> This could be a rights issue. Connect to the problem server using the sa
> account and see if it shows up.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "SQL Replicatio Guy" <SQL Replicatio Guy@.discussions.microsoft.com> wrote in
> message news:F6019804-2776-4532-836D-C51156354A45@.microsoft.com...
> should
>
>

Replication Monitor could not connect to Distributor

Hello Guys,

I have the following scenario:

PC1 : located in Dubai representing my laptop

PC2: located in Denver ,

Both pcs are connected to each other via the internet as i am using Aliases ,they can both access and see each other using SQL Auth.

I want to implement Merge Replication to Synchronize TestDB ,

I have NO DOMAIN connnecting them.

I Created a new publication ,under security i asked the agent to use the Sa account to connect

When launching the rep monitor i get the following error:

"Replication Monitor could not connect to Distributor 'laptop'."

"Login failed for user ''. The user is not associated with a trusted SQL Server connection. (.Net SqlClient Data Provider)"

Both Publisher and Distributer are on my Laptop ,why cant they connect to each other?

Another Question : could i implement Traditional Merge replication to synchronize my DBs or do i need to configure Web Synch in Merge rep to enable connecting via the internet?!

Thanks Guys!

Moodi

First off while you are free to use web synchronization where appropriate you probably can use traditional merge replication.

It is probably that you have configured replication monitor to connect to your distributor with an account which does not have the necessary rights to monitor SQL server. Can you ensure that SQL Server is able to authenticate using mixed authentication (right click on it, select properties, select security and ensure that SQL Server and windows authentication is selected. Add an account in the sysadmin role or verify you know the sa password. Then right click on your distributor in Replication Monitor and select remove. Then right click and add it again, this time use the sa account and its password to add it.|||

Thanks Hillary,

i was able to fix this by configuring the property of the connection used to connect to distributer ,it was windows auth. so i changed it to run under SQL auth. now replication monitor can run and show all subscribers but i have another problem.

I get the following error when i try to initialize the subscription located on my USA server :

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.1]
2007-07-05 11:55:11.00 Logon Error: 18456, Severity: 14, State: 11.

Please note that i am using merge replication via the internet with out web synch. ,when i run the SQL Agent under the local system account i get the above mentioned error although i configured Sa account with the same pwd to be used on both machines.

I created a windows account RepUser on both machines as part of Admin group ,then i configured the agent on both machines to run under this account ,i got the following error:

Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]
2007-07-05 11:55:06.15 Logon Error: 17806, Severity: 20, State: 2.

Looks like the SQL agent process account is the one thats being authenticated and NOT the Sa account ,why is this happening?

|||

Hi Ali

I am a little lost here, but it sounds like you need to configure your publication to use a ftp snapshot and then configure ftp for anonymous authentication.

HTH

|||

Hello Hilary ,

Are u saying that if i have two mahcines replicating via the internet then i should have the snapshot folder accessible via FTP?

Ali

replication issue

need to set up replication with a distributor - does anyone know a good
article on how to do this ?
when i publish the articles, how do I like the subscriber to the publisher
when there is a distributor in the middle... do I point to the distributor ?John
Look at these articles
http://www.swynk.com/friends/achigrik/SetupMR.asp -- Setting Up Merge
Replication: A Step by Step Guide
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"John Smith III" <jsmithIII@.yahoo.com> wrote in message
news:eO7B2eVuDHA.3224@.tk2msftngp13.phx.gbl...
> need to set up replication with a distributor - does anyone know a good
> article on how to do this ?
> when i publish the articles, how do I like the subscriber to the publisher
> when there is a distributor in the middle... do I point to the distributor
?
>

Replication is failing due to use of FTS on my subscriber, what can I do?

Hi Daniel,
If you are using push subscriptions from a SQL2000 distributor, you are
essentially using the SQL2000 replication components which, I am sorry to
say, are ill-equipped to handle things like full-text indexes during
snapshot processing. This also means that upgrading the subscriber to
SQL2005 SP2 will probably not do you any good. Alternatively, you can use a
SQL2005 SP2 instance as the distributor of your SQL2000 publisher so you can
enable the FulltextIndex (0x0000000001000000) article schema option via
sp_add|changearticle (both SQL2000 and SQL2005 GUI will not allow you to
specify that for a SQL2000 publisher) and let the SQL2005 replication
components handle the full-text index dependencies for you (ideally using
"drop" as the article pre-creation commands). That said, I can imagine that
moving the distributor can involve a substantial amount of work.
Hope that helps,
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:uAOtEPAjHHA.1272@.TK2MSFTNGP04.phx.gbl...
> I'm in the middle of setting up a non-updating transactional replication
> from SQL Server 2000 SP3 (can't put SP4 on as the main application we use
> hasn't been certified for SP4 yet) to SQL Server 2005 SP1 (I could put SP2
> on if it will fix the issue, but it would mean taking our e-commerce sites
> down while doing so and I'd need to schedule a maintenance window for
> this). At first it was working fine, but snapshots were set to delete the
> tables and so we'd lose the FTS setups. I've now changed the snapshots to
> not do this, and now the replications fails with the error:
> Cannot drop index 'PK_Product' because it enforces the full-text key for
> table or indexed view 'Product'.
> This occurs with both "Delete data. If article has a row filter, delete
> only data that matches the filter.", "Truncate all data in the existing
> object" (which is the preferred option), and "Keep existing object
> unchanged". It also doesn't matter if I have the clustered and/or
> nonclustered index copy set to true or false (the PK is the clustered
> index on this table).
> This is a push subscription, with the distribution agent running on the
> publisher.
> Any ideas how I can retain the table structure (so keeping the FTS index
> and not having to rebuild it each time the snapshot is applied) and have
> transaction replication working? Or is it not possible?
> Dan
>
Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>
|||Hi Daniel,
I probably don't understand all the details about your scenario but given
that applying a snapshot typically replaces most of the data at the
subscriber, I would think that a FTS rebuild is likely required (or at least
a good idea) after the snapshot has been applied. That said, we no longer
drop the primary key\unique constraints (which is an arguably bad fix for
some other issue) in a "mostly" SQL2005 environment (SQL2005 snapshot and
distribution agent) if the article pre-creation is 'delete'. However,
leaving any unique constraints\indexes (especially non-clustered) while the
snapshot is being applied runs the risk of slowing down the snapshot
delivery process significantly (no minimal logging) and may prevent a
concurrent snapshot from being delivered successfully since bcp data
generated for a concurrent snapshot can violate uniqueness constraints
(compensated later on during the reconciliation phase).
-Raymond
"Daniel Crichton" <msnews@.worldofspack.com> wrote in message
news:eLx1McKjHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Raymond wrote on Tue, 1 May 2007 09:54:35 -0700:
>
> It seems strange that all options require the PK to be dropped - I would
> have thought that the options to delete or truncate data in the
> destination table would leave the PK untouched (after all, it shouldn't be
> touching the schema). I don't have an FTS index on the SQL Server 2000
> source tables - the FTS is handled solely on the subscriber, so I'm not
> trying to replicate the FTS catalog, just the data in the tables so that
> the change tracking on the subscriber handles all the FTS work.
> Dan
>