Did anyone ever happen to resolve this issue? I have been reading a lot about the identity issue with merge replication on SQL 2008, but havent come across a solution yet. This issue is haunting me. This happens on articles that have lot of activity. It is not that the entire range allocated us used up, rather sometimes it is 20% used up and a new range is allocated, sometimes 50%, sometimes 100% as expected, and sometimes it doesnt allocate new range at all.

Someone please let me know if there is a fix to this. I am also planning to open a case with MS, soon if dont find a resolution on net.

Thanks in advance.