Problem with queued updating in transactional repl on win/SQL 2000

Hey guys. I've 2 servers with SQL 2000. I've a publisher/distributor and a
subscriber. Now, there is a queued updating setup between this two with push
replication. I'm trying to replicate the employees table of Northwind
database only. the primary key is setup to use identity ranges on the 2
servers. The problem I'm facing is that, when I insert/update data on a
publisher, it gets replicated fine to subscriber, no matter what. But, when I
try to insert data at the subscriber, it doesn't work(update works fine). It
gives me an error msg2627. violation of a primary key constraint at the
subscriber. It says 'cannot insert duplicate key in object 'Employees'. The
thing is that I'm using identity for the primary key. So, I'm very confused
as to what this is saying. Please help. Thank you.
Tejas,
sounds like you haven't set up automatic identity range management, and hte
identity values are clashing. In the article properties you can see this
option, but it'll require reinitialization. As a stop-gap you could reseed
the identity range on the subscriber (dbcc checkident).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)