Hello
I have made a merge replication between two server W2k with sql2000 sp3. Those servers are connected via internet. In distributor (also publisher) I have setting up aliases for both servers. Have generated snapshot but when agent run I have this error: -2
147201019 and 14010 : "the subscription for pubblication [bla bla] is invalid".
I have searching in the net some solutions but I have noticed that in all cases it is depended by alias setting. But I have defined its ?
Some ideas ?
Have solved the puzzle.
In subscription I have noticed with sp_helpserver that the subscription server hav id = 1 so have do this:
sp_dropserver 'DIST_SERVER'
sp_dropserver 'SUB_SERVER'
sp_addserver 'SUB_SERVER', @.local = 'LOCAL'
where DIST_SERVER is my distribution, publisher server and SUB_SERVER is my subscription server.
Bests
|||Rafal,
OK, and the last 2 commands will require a restart of the services.
I'm not clear what the first line is for though (sp_dropserver 'DIST_SERVER').
Regards,
Paul Ibison
Showing posts with label w2k. Show all posts
Showing posts with label w2k. Show all posts
Monday, March 26, 2012
Wednesday, March 7, 2012
Merge replication error
Hello, everybody,
I'm using SQL 2000 SP4 on W2K & W2003 Server. In the last 2 weeks, I
encounter a very annoying problem with the replication:
"The merge process encountered an unexpected network error. The connection
to Publisher 'AR-MAIN' is no longer available" - error number -2147199469
And along with that: "General network error. Check your network
documentation."
The problem is that the error occurs only sometime.
And only occurs to the merge process on one table (no filters, table to
table replication).
The others replicate just fine...
However, it's true that this one is the most accesed table.
I have a VPN connection between the Publisher's site and the Subcriber.
But the VPN link is stable, there are no bottlenecks - only the two SQL
servers seem to have problems.
Any idea? Could it be something related to the SQL server, or should I look
elsewhere?
Thanks,
Valentin
This error is most frequently transient and caused by lossy network
connections. Try using the verbose profile to see if this shows the error
which occurs before this error which is sometimes masked by the general
network error.
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
"Valentin Holban" <ValentinHolban@.discussions.microsoft.com> wrote in
message news:D362A7BA-5D76-480E-9B94-4C145F65B520@.microsoft.com...
> Hello, everybody,
> I'm using SQL 2000 SP4 on W2K & W2003 Server. In the last 2 weeks, I
> encounter a very annoying problem with the replication:
> "The merge process encountered an unexpected network error. The connection
> to Publisher 'AR-MAIN' is no longer available" - error number -2147199469
> And along with that: "General network error. Check your network
> documentation."
> The problem is that the error occurs only sometime.
> And only occurs to the merge process on one table (no filters, table to
> table replication).
> The others replicate just fine...
> However, it's true that this one is the most accesed table.
> I have a VPN connection between the Publisher's site and the Subcriber.
> But the VPN link is stable, there are no bottlenecks - only the two SQL
> servers seem to have problems.
> Any idea? Could it be something related to the SQL server, or should I
> look
> elsewhere?
> Thanks,
> Valentin
I'm using SQL 2000 SP4 on W2K & W2003 Server. In the last 2 weeks, I
encounter a very annoying problem with the replication:
"The merge process encountered an unexpected network error. The connection
to Publisher 'AR-MAIN' is no longer available" - error number -2147199469
And along with that: "General network error. Check your network
documentation."
The problem is that the error occurs only sometime.
And only occurs to the merge process on one table (no filters, table to
table replication).
The others replicate just fine...
However, it's true that this one is the most accesed table.
I have a VPN connection between the Publisher's site and the Subcriber.
But the VPN link is stable, there are no bottlenecks - only the two SQL
servers seem to have problems.
Any idea? Could it be something related to the SQL server, or should I look
elsewhere?
Thanks,
Valentin
This error is most frequently transient and caused by lossy network
connections. Try using the verbose profile to see if this shows the error
which occurs before this error which is sometimes masked by the general
network error.
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
"Valentin Holban" <ValentinHolban@.discussions.microsoft.com> wrote in
message news:D362A7BA-5D76-480E-9B94-4C145F65B520@.microsoft.com...
> Hello, everybody,
> I'm using SQL 2000 SP4 on W2K & W2003 Server. In the last 2 weeks, I
> encounter a very annoying problem with the replication:
> "The merge process encountered an unexpected network error. The connection
> to Publisher 'AR-MAIN' is no longer available" - error number -2147199469
> And along with that: "General network error. Check your network
> documentation."
> The problem is that the error occurs only sometime.
> And only occurs to the merge process on one table (no filters, table to
> table replication).
> The others replicate just fine...
> However, it's true that this one is the most accesed table.
> I have a VPN connection between the Publisher's site and the Subcriber.
> But the VPN link is stable, there are no bottlenecks - only the two SQL
> servers seem to have problems.
> Any idea? Could it be something related to the SQL server, or should I
> look
> elsewhere?
> Thanks,
> Valentin
Subscribe to:
Posts (Atom)