Merge Replication Issues

Hello All,
I would greatly appreciate some help on this issue. I am very stuck and
struggling.
Basicall I have a SQL 2000 Server, that is the publisher for a merge
replication. This merge replication, is to replicate to handhelds, that via
a mobile application, insert into the tables. The handhelds seem to be
operating fine. The publisher is not however. When I try and insert records
into the tables via web interface, I keep getting:
The identity range managed by replication is full and must be updated by a
replication agent.
So I've read for hours online searching for this issue, tons of people have
hit it, but nobody has a solid answer. Most people just hack crap together
that works, or sometimes works.
Basically how I configured it in the beginning was, each subscriber, and
publisher got 200 identities, using automatic identity range management.
Then the website started to hit problems. So I read some articles, some
people said to set the identity ranges to something high that may never get
hit. So I changed them to 60,000. This doesn't seem to work either. Every
day now, sometimes twice a day, I'm getting range is full errors.
Sometimes I can temporarily fix this by calling stored procedures manually
via:
Sometimes works:
EXEC sp_adjustpublisheridentityrange "PublicationName"
Works more often:
DBCC CHECKIDENT ('TableName', RESEED)
But right now, I have one of our customer databases that neither of these
are working.
I would very much appreciate any help on this. It seems theres many myths
about merge replication not working well at all, and its a huge pain to
manage, if you are even able to make it work. I would greatly appreciate
some help as I'm very stuck. Perhaps contact with a MS rep would be great as
well but not very likely I'm sure.
Perhaps theres some tables I can look up that has values of settings that
could of gotten messed up, that I could show to someone who understands them,
and trouble shoot there if that exists.
Thanks all for listening.
Take care,
Simon
As a side note,
I just looked at the tables constraints, and it says this:
([VID] > 21100 and [VID] < 21200)
Is this correct? Is this an issue that I configured it originally for 200
ranges, then changed it to 60,000 ranges?
Also on one table that all the stored procedures don't work, there are 2
constraints on one table for inserts and both are from replication. This
sounds bad. Something is messed up I think?
Thanks,
Simon
"Si" wrote:

> Hello All,
> I would greatly appreciate some help on this issue. I am very stuck and
> struggling.
> Basicall I have a SQL 2000 Server, that is the publisher for a merge
> replication. This merge replication, is to replicate to handhelds, that via
> a mobile application, insert into the tables. The handhelds seem to be
> operating fine. The publisher is not however. When I try and insert records
> into the tables via web interface, I keep getting:
> The identity range managed by replication is full and must be updated by a
> replication agent.
> So I've read for hours online searching for this issue, tons of people have
> hit it, but nobody has a solid answer. Most people just hack crap together
> that works, or sometimes works.
> Basically how I configured it in the beginning was, each subscriber, and
> publisher got 200 identities, using automatic identity range management.
> Then the website started to hit problems. So I read some articles, some
> people said to set the identity ranges to something high that may never get
> hit. So I changed them to 60,000. This doesn't seem to work either. Every
> day now, sometimes twice a day, I'm getting range is full errors.
> Sometimes I can temporarily fix this by calling stored procedures manually
> via:
> Sometimes works:
> EXEC sp_adjustpublisheridentityrange "PublicationName"
> Works more often:
> DBCC CHECKIDENT ('TableName', RESEED)
> But right now, I have one of our customer databases that neither of these
> are working.
> I would very much appreciate any help on this. It seems theres many myths
> about merge replication not working well at all, and its a huge pain to
> manage, if you are even able to make it work. I would greatly appreciate
> some help as I'm very stuck. Perhaps contact with a MS rep would be great as
> well but not very likely I'm sure.
> Perhaps theres some tables I can look up that has values of settings that
> could of gotten messed up, that I could show to someone who understands them,
> and trouble shoot there if that exists.
> Thanks all for listening.
> Take care,
> Simon