Replication fail(register fail)

Hi, there
I tried to replicate between the sql 2000 servers
As you know, In order to try to set up the replication, I need a sql server
name on the list box which is used to select the publisher and the
subscriber.
So I had tried to register SQL 2000 Server at the first time. but there is
now server name, so I had registered sql server using IP address.
and then setted up the replication. but one day sql server registered using
IP address removed and replication failed.
I think it's problem is because of the Network.
For the reference, two sql server don't locate under the same HUB and far
from each other. but they are on the same Subnet mask.
What should I check for fixing that problem?
Please, let me know.
Thanks in advance for your help,
Kelly Seo
can you ping the remote server? What does ping -a IpAddress return?
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
"kelly seo" <jyseo@.tricom.co.kr> wrote in message
news:eaRlSybhFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi, there
> I tried to replicate between the sql 2000 servers
> As you know, In order to try to set up the replication, I need a sql
server
> name on the list box which is used to select the publisher and the
> subscriber.
> So I had tried to register SQL 2000 Server at the first time. but there is
> now server name, so I had registered sql server using IP address.
> and then setted up the replication. but one day sql server registered
using
> IP address removed and replication failed.
> I think it's problem is because of the Network.
> For the reference, two sql server don't locate under the same HUB and far
> from each other. but they are on the same Subnet mask.
> What should I check for fixing that problem?
> Please, let me know.
>
> Thanks in advance for your help,
> Kelly Seo
>
|||sure, of course
when I ping to the remote server, return the remote ip address.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:enCfPxfhFHA.2484@.TK2MSFTNGP15.phx.gbl...
> can you ping the remote server? What does ping -a IpAddress return?
> --
> 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
> "kelly seo" <jyseo@.tricom.co.kr> wrote in message
> news:eaRlSybhFHA.1148@.TK2MSFTNGP12.phx.gbl...
> server
> using
>

replication fail

it is not the solution

>--Original Message--
>When doing a search for "Violation of Primary Key
>constraint" in the Knowledge Base, this is the very
first[vbcol=seagreen]
>entry.
>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;813494&Product=sql2k
>
>but
Cannot
>same
>the
>.
>
enable logging as per this kb article. It will tell you eactly which row
your distribution agent is failing on.
http://support.microsoft.com/default...&Product=sql2k
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
<anonymous@.discussions.microsoft.com> wrote in message
news:1f0101c4a775$740874e0$a401280a@.phx.gbl...[vbcol=seagreen]
> it is not the solution
> first
> Cannot
sql

Replication Error using Ras Connection win2003srv

I use Dial up (RAS) Connection for syncronize
If I disable my LAN syncronize success
but if I enable My LAN syncronize Fail (cannot connecting to subscriber)
It sounds like you lan connection can't resolve the host name of your subscriber, but it can for the ras dial up.
Can you try to check your hosts file entry for this subscriber? It will be in c:\%windir%\system32\drivers\etc and is called hosts. open it up in a text editor.
if it is not there check the client network setting for this server and verify that the ip address is valid.
Is the subscriber parked in the DMZ by chance? If so it may have a different address.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Nur Firmanullah" wrote:

> I use Dial up (RAS) Connection for syncronize
> If I disable my LAN syncronize success
> but if I enable My LAN syncronize Fail (cannot connecting to subscriber)
>

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 Breaks after applying SP4

Hi
I installed SP4 on our enterprise server this morning and now all
replication jobs fail with the message "No such interface supported"
Has anyone seen this before / know how to resolve this?
We run Enterprise Edition on Win2003
Many Thanks
D
nope. I suggest you re-register the replication dll's and exes. I think you
can find them in c:\program files\microsoft sql server\mssql\80\com
"DJ" <DJ@.discussions.microsoft.com> wrote in message
news:CA106D94-FD82-4099-A342-BF75A0910D5B@.microsoft.com...
> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||There was apparently an as yet not fully explained registry ACLing problem in
SP4 setup per the following thread (reported by Tomasz Skorupa originally):
http://groups.google.com/group/micro...85 a5a37097d4
With more than one person hitting the same problem, I would like to try
again and see if I can find out more about the cause of it. Was the user
running SP4 setup on the machine the same as the one running SQL Server Agent
service? If not, did the account running SP4 have privilege for enumerating
account information for the SQL Server Agent service account?
-Raymond Mak
"DJ" wrote:

> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||Thanks for the reply Raymond and apologies for not replying sooner but I have
been off work.
I tried re-registering the dll following the steps you mentioned in the
other thread but this did not work for me.
I re-registered them and stopped and started SQL Agent. Did I need to do
anything else?
The version of sqlrepss.dll on my instance is :2000.80.2039.0
I was not connected as the service account so I may not have had the
prvilages for enumeration the account informaion.
I can run the replication from the command line but I always get the error
when using Enterprise Manager.
Do you have any other suggestions to resolve this?
Many Thanks
Daryl
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> There was apparently an as yet not fully explained registry ACLing problem in
> SP4 setup per the following thread (reported by Tomasz Skorupa originally):
> http://groups.google.com/group/micro...85 a5a37097d4
> With more than one person hitting the same problem, I would like to try
> again and see if I can find out more about the cause of it. Was the user
> running SP4 setup on the machine the same as the one running SQL Server Agent
> service? If not, did the account running SP4 have privilege for enumerating
> account information for the SQL Server Agent service account?
> -Raymond Mak
>
> "DJ" wrote:
sql

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoon
This really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =
OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can not
get an exclusive lock.
Regards
John
"jcvoon" wrote:

> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoonThis really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =
OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can no
t
get an exclusive lock.
Regards
John
"jcvoon" wrote:

> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoonThis really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can not
get an exclusive lock.
Regards
John
"jcvoon" wrote:
> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

Replication 2000 - What if Publisher dead

What if a Publication and Distribution server machine fail to work. Do I need to reinitiliaze the whole snapshot on a new machine and retransmit the data to the subscriber. Or can I make use of replication script to recreate the publication and distribution and then replicate to existing subscriber using same machine name?

ThanksHow bad did it fail?|||Let say, if unable to load the SCSI hardisk, or the hardware failured.
Thanks

Originally posted by joejcheng
How bad did it fail?