Replication Error

I have a database thats got sql as the engine and access 2000 for the client side.Now my problem is every time I edit a record this "Write Conflict" comes up. I did some investigating and I found out its due to a REPLICATIONCONFLICT ERROR.
Can anyone help me plsIs your Access FE running against a database that participates in merge replication? You need to have a serious talk with your DBA about whether you should be developing any app using a db that is already part of another app.|||the only application involved is access 2000, and the network techs are the dba|||what do you mean pls explain FE??sql

Replication does detect Mirrored Source Fail Over

I'm trying setup a proof of concept for a client but I’m having issues with mirroring and replication.

With the help of http://technet.microsoft.com/en-us/library/ms151799.aspx I’ve done the following..

The setup is as follows, I have several instances of SQL Server

A+B are mirrored with each other, with A being the principle and B the mirror

C is the distributor

E is subscribes to A, with parameters for PublicationFailoverPartner set to B

The mirroring between A+B works fine, I can manually fail each and the databases keep in step.

Without testing the mirroring failover, the replication between A+C+E also works.

However when I test the mirror to failover between A+B no transactions are replicated though to E. The publication moves from A to B in the Server Management Studio.

The logs state that the log reader agent can not gain access to A, however nothing is recorded regarding any attempts to contact B. In the replication monitor the error message

"The concurrent snapshot for publication ABCXYZ is not available because it has not been fully generated of the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Spapshot Agent for the publica..." (cut off).

"the process could not execute 'sp_replcmds' on 'A'

I have checked that the SQL Server Agents are running on all agents,

I have checked that that server B is set at the PublisherFailoverPartner on server C agent configuration, I'm now at a lost as to what is wrong,

Any help or suggestions are greatly appreciated.

Pls do not duplicate

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1958649&SiteID=1

|||

Sorry about this Deepak, I had duplicated this as I though I had lost my original post, it was just in anothor forum,

appologies for being a Topic Hog

Replication between SQL Express 2005

Hi All,

I am trying to do a Replication between a network SQL Server Express Edition 2005 DB with a client SQL Server Express Edition 2005 DB. My question is

1. Can we do replicaiton between SQL Server Express Edition 2005. (No SQL SERVER present)

2. If yes can any of you provide me some guidance or some pointers on how to achieve it.

Thanks

Suresh

Quick answer is no. Check out the following posting for more info.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941980&SiteID=1

Gary

Replication and Licensing

I'm in the process of discovering what type of licensing my client has for
their SQL Server 2000 (Standard). It's either Server plus device CAL or
Server plus user CAL. I think they have 35 CAL.
Now, what will we need to do with regard to licensing if we add in a new,
separate machine to be a subscriber in transactional replication. Will they
have to purchace an whole new set of licences?
Thanks,
Tom
As I dig along, it looks to me like I just need to get them to skin down for
one more server licence @. $667 US per server according to
http://www.microsoft.com/sql/howtobuy/default.asp
Does that seem right?
"Tom Gaughan" <tgaughan@.numail.org> wrote in message
news:OURp501aEHA.2340@.TK2MSFTNGP09.phx.gbl...
> I'm in the process of discovering what type of licensing my client has for
> their SQL Server 2000 (Standard). It's either Server plus device CAL or
> Server plus user CAL. I think they have 35 CAL.
> Now, what will we need to do with regard to licensing if we add in a new,
> separate machine to be a subscriber in transactional replication. Will
they
> have to purchace an whole new set of licences?
> Thanks,
> Tom
>

Replication and Different Domains

Hi guys,
We have a client who wants to set up the publisher (for merge
resplication) on a particular domain, but the subscribers will be on a
different domain. Is this even possible?
The main question was about the snapshot folder location. Is there a way
for the subscriber to get access to the folder being on a different domain?
Thanks,
Maer
You could have a look at
http://www.replicationanswers.com/InternetArticle.asp for details of
non-trusted setup. If there is a posibility of setting up a trust (or VPN)
then things are pretty straightforward.
HTH,
Paul Ibison
|||Hi Paul - Thank you so much for the article, it was extremely helpful!
Maer
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:7A661F57-4BB5-4D0C-9936-0A358E71683D@.microsoft.com...
> You could have a look at
> http://www.replicationanswers.com/InternetArticle.asp for details of
> non-trusted setup. If there is a posibility of setting up a trust (or VPN)
> then things are pretty straightforward.
> HTH,
> Paul Ibison
>

Replication - Row not correctly sync

Hi Everyone!

I have a strange issue in my replicated databases.

I've a 5 merge subscribers replication schema. Our client discover a row that isn't matching with another database.

After some research it seam that the correct row is only at one database and all other database, have a the same row in a incoherent status.

Anyone have a idea on how this could happen?
I'm clue less right now

Thanks!

To fix the issue I decide to bring a change to the correct row to let it propagate to every other subcriber. But event more strange, not all collumn are updated to other subscriber!!!

This is really really strange

replication - agent is suspect

I setup a client with merge replication, the following error was
returned after working successfully for a day "The agent is suspect.
No response within the last 10 minutes". Most research I found on
the newsgroup is this error does not stop merge replication from
working, but in my case it did stop replication from working. I was
able to get to working again by running the following command.
sp_replication_agent_checkup @.heartbeat_interval = 6000
Can anybody explain why replication stopped working altogether with the
agent is suspect message, and what can I do to avoid this message to
begin with?
Thank you,
Pauly C
Suspect means that the agent hasn't communicated with the job subsystem in
the interval defined in the heartbeat_interval.
The job will be failed after the heartbeat_interval has passed, but I am not
exactly sure when.
The agent could be busy, dead, or trying to connect. Run profiler on the
subscriber to try to figure out what is going on. Profiler might not reveal
anything. There is a condition when the publisher or subscriber has
exhausted buffers and hangs on initialization. You can clear this by
rebooting.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"paulysc" <paulysc@.optonline.net> wrote in message
news:1141228700.833217.245870@.t39g2000cwt.googlegr oups.com...
>I setup a client with merge replication, the following error was
> returned after working successfully for a day "The agent is suspect.
> No response within the last 10 minutes". Most research I found on
> the newsgroup is this error does not stop merge replication from
> working, but in my case it did stop replication from working. I was
> able to get to working again by running the following command.
> sp_replication_agent_checkup @.heartbeat_interval = 6000
> Can anybody explain why replication stopped working altogether with the
> agent is suspect message, and what can I do to avoid this message to
> begin with?
> Thank you,
> Pauly C
>
|||I saw this error message if the job runs against a wrong database. In my
case, the Queue Reader was running against the master database, not the
distribution, which resulted to the same error message as yours.
hope it helps,
FJY
"paulysc" wrote:

> I setup a client with merge replication, the following error was
> returned after working successfully for a day "The agent is suspect.
> No response within the last 10 minutes". Most research I found on
> the newsgroup is this error does not stop merge replication from
> working, but in my case it did stop replication from working. I was
> able to get to working again by running the following command.
> sp_replication_agent_checkup @.heartbeat_interval = 6000
> Can anybody explain why replication stopped working altogether with the
> agent is suspect message, and what can I do to avoid this message to
> begin with?
> Thank you,
> Pauly C
>

Replicating over VPN to non trusted workgroup

I have a situation where a client connects to our network via VPN has set up
a SQL Server on a small workgroup that wishes to subscribe (via
transactional replication) to publications on my SQL Publisher.
My stumbling block is permissions to the \\myserver\repldata folder on our
domain. The client machine being a non-trusted domain (in fact not even a
domain) means I can't set up read and list files & folders permissions.
My plan is that I set up the pull subscriptions, create the snapshots and
then copy the entire \\myserver\repldata folder to the client machine and
point the pull subscriptions there.
Is this the best solution in the circumstances? After the initial snapshot,
does transactional replication ever need to access \\myserver\repladat
again?
Cheers!
Simon
Simon,
you can use the alternative snapshot location option - I do it this way for
large snapshots which I zip up before sending over.
If FTP is available this is probably an easier option though to set up the
publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Many thanks.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OzVonAjYHHA.208@.TK2MSFTNGP05.phx.gbl...
> Simon,
> you can use the alternative snapshot location option - I do it this way
> for large snapshots which I zip up before sending over.
> If FTP is available this is probably an easier option though to set up the
> publication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
|||Try to use pass-through authentication. This is where you have two identical
local machine accounts with the same name and the same password.
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
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:%23W9Y9siYHHA.448@.TK2MSFTNGP04.phx.gbl...
>I have a situation where a client connects to our network via VPN has set
>up a SQL Server on a small workgroup that wishes to subscribe (via
>transactional replication) to publications on my SQL Publisher.
> My stumbling block is permissions to the \\myserver\repldata folder on our
> domain. The client machine being a non-trusted domain (in fact not even a
> domain) means I can't set up read and list files & folders permissions.
> My plan is that I set up the pull subscriptions, create the snapshots and
> then copy the entire \\myserver\repldata folder to the client machine and
> point the pull subscriptions there.
> Is this the best solution in the circumstances? After the initial
> snapshot, does transactional replication ever need to access
> \\myserver\repladat again?
> Cheers!
> Simon
>
|||That works when I log on that account and browse to the folder. Should I
then run SQL Server and Agent under that local account?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
> Try to use pass-through authentication. This is where you have two
> identical local machine accounts with the same name and the same password.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
|||Yes!
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
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:eQmS6QlYHHA.4692@.TK2MSFTNGP04.phx.gbl...
> That works when I log on that account and browse to the folder. Should I
> then run SQL Server and Agent under that local account?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
>