replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

sql

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||

yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

Replication failed

Hi,
We are using transactional replication and it failed and
showing following error
Error:
The process could not bulk copy into table 'TableName'.
Error Number:
22001
Category:ODBC
Source: ODBC
Full Message:
String data, right truncation
Is any one having solution for this?
Regards,
Manoj
Manoj,
can you check if the schemas are identical on publisher and subscriber if
you are doing a nosync initialization.
If you are sending over the table schema, can you ensure that you take the
collation.
Regards,
Paul Ibison

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