The default behaviour for an identity column now is to increase the seed after a restart or failover, etc. By doing this
sql-lover (3/27/2014)
I fixed it via DBCC command
you are likely compounding the issue you are seeing. You should not have touched it. By setting the seed back it will then increment forward and hit a value that's already previously used.
There is a trace flag -T272 to make the database engine behave like SQL Server 2008. Its all detailed here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉