merge replication identity range drives me crazy

Hello everybody.
I'm in trouble.
The project I am working on is stuck because Sql Server replication isn't working as it should. At least I think so! :-)
I have a publisher and three subscribers in a merge replication. I had some problems inserting rows at subscribers because identity ranges were not set. But I set them (every identity value has its range up to 50000). When I initialize the subscriber and try to insert values in it, the following error occures:
The identity range managed by replication is full and must be updated by a replication agent. The INSERT conflict occurred in database 'Proba', table 'Cena', column 'IDCena'. Sp_adjustpublisheridentityrange can be called to get a new identity range.
But, this cannot be possible because no data has ever been inserted at the subscriber and identity range has been set to a great value.
Please help me understand what's going on and to solve problem. I'm in a trouble...

Quote:

Originally posted by Pera Pisar
Hello everybody.
I'm in trouble.
The project I am working on is stuck because Sql Server replication isn't working as it should. At least I think so! :-)
I have a publisher and three subscribers in a merge replication. I had some problems inserting rows at subscribers because identity ranges were not set. But I set them (every identity value has its range up to 50000). When I initialize the subscriber and try to insert values in it, the following error occures:
The identity range managed by replication is full and must be updated by a replication agent. The INSERT conflict occurred in database 'Proba', table 'Cena', column 'IDCena'. Sp_adjustpublisheridentityrange can be called to get a new identity range.
But, this cannot be possible because no data has ever been inserted at the subscriber and identity range has been set to a great value.
Please help me understand what's going on and to solve problem. I'm in a trouble...

|||I've solved the problem.
Some old settings for an early ajusted replication remained, so there were some constraints that didn't pass.
I didn't know that settings like identity range remain after the replication is deleted. Or did I do something wrong?

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

Merge Replication Agents

Hi everybody,
I have a system of 2 PC, with installed Win XP and SQL 2000. I
configured one PC as Publisher and Distrbutor, and the other as a
Subscriber with a "push" subscription. The snapshot and the merge
agents are running on the Publisher/Distributor. This PC is always ON
for 24 hours everyday, while the subscriber PC at the evening is
turned off and restarted at the morning.
Looking the Replication monitor at the morning, I see red cross on
both agents (snapshot and merge) and the synchronization doesnt' seem
working; if I restart the agents a message tells that the agent is
already running and the red flags disappear.
Anyone can help me to undertand better the situation, or give me some
suggestion?
Thanks a lot.
Marco
What error messages exist for the agents when there is a red cross - can you
please post it up. I'd expect that the merge agent would be killed if it is
synchronising during the process of rebooting the subscriber, but if there is
a schedule or it is set to run continously then it should restart ok. The
snapshot agent shouldn't be running at all after initialization. So, perhaps
the initialization never worked, and the merge agent failed because the
snapshot agent hadn't run? Anyway, please post up some more info and things
whould get clearer.
Paul Ibison
|||On 19 Giu, 17:57, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> What error messages exist for the agents when there is a red cross - can you
> please post it up. I'd expect that the merge agent would be killed if it is
> synchronising during the process of rebooting the subscriber, but if there is
> a schedule or it is set to run continously then it should restart ok. The
> snapshot agent shouldn't be running at all after initialization. So, perhaps
> the initialization never worked, and the merge agent failed because the
> snapshot agent hadn't run? Anyway, please post up some more info and things
> whould get clearer.
> Paul Ibison
Hi Paul,
I don't know exactly what kind of error there is, because I dont' have
the PC with me; this problem has been explained me by another
technician that is testing the system. But I know that the merge agent
is setted to run continously, and that the synchronization was working
when I setted the replication process; only I tested it with the 2 PC
both running and I didn't test the condition with 1 PC running and the
other PC turned off.
|||OK - there's not much I can do without the error message. Try to get it off
your colleague and post it up and I'll take a look.
Cheers,
Paul Ibison