even today the same error occurred "Violation of primary key"

when i ran DBCC CHECKIDENT (<tablename>, NORESEED) this is the result it through out..

Checking identity information: current identity value '116', current column...

PK_USER_CITY in this city is the city table pk, and this "839674091" is the USER_CITY pk value

This is what it returned.

Checking identity information: current identity value '839674091', current column value '839674091'.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

what does this mean?

This is the actual record on publisher

 115,285,16,7/6/2005 1:21:20 PM

and when this is getting replicated on the subcriber it goes as

 872516, 285, 16, 7/6/2005 1:21:20 PM and again the id in the...

there is no activity happening on subcription im just using that as a standby unless sql1 goes down. i wouldnt be using for anything. and i dont have an triggers...

Micheal,

       Yea im using identity columns. i dont know at what event this happens but one thing for sure i know is that its generating some strange number which doesnt make sense...

Check if the security is set for SQL server and windows authentication and audit level set to none. Probably this work fine. good luck