Need help

Hi,
We have publisher and remote distributor with lot of transactional and
merge publications. (SQL2K SP3)
Recently we migrated our publisher to a new machine.
Today I renamed my old publisher server and tried to disable subscribers on
it (because everything works on a new publisher already).
When I did that via EM, all my replication agents on a distributor failed
(probably the old publisher wrote somethig to the distributor).
Then I marked (enabled) all subscribers back on that server (old publisher).
After that all merge replications became good again. Buh the transactional
ones don't work.
I get an error "The remote procedure call failed and did not execute"
Need help.
Thanks
Hi,
How did you rename the old publihser from EM? I'm not familiar with that capability.
-Matt
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

need advise of basic knowledge

I dont know where to put this thread, I just wanna ask a question..actually what is happen when subscription synchronized the publications among IIS process.. (SQLMobile)

could you guys give me a diagram/schema of it?

thanks before

What are you looking for?

If you want a detailed process regarding security and logins that get used using web synchronization, refer to this:

http://msdn2.microsoft.com/en-us/library/ms345212.aspx

If you have any other specific questions, please do post them.

|||

thanks for your reply Mahesh :)

I also curious about, when subscriber do data update on SQLMobile, and then use sync process, what is happen with the data on publisher?is it updated like the subscriber did or subscriber will change back the data to origin publisher's?I'm using merge replication

many many thanks..

|||

If the subscriber updates data and there are no conflicting publisher updates, the subscribers updates will be propagated to the publisher.

If there are conflicts (publisher and subscriber update the same row or same column -- depending on row or column tracking) there could be conflicts and one of them may lose. Also the winning row is governed by the type of article resolver you choose.

|||

thx for ur info

I'll try it