SQL Profiler event to trace - Snapshot isolation transaction aborted due to update conflict

Check:
http://technet.microsoft.com/en-us/library/cc546518.aspx

Indeed, This is of the common data consistency issues of transaction isolation level either it posted you an error or not posted…How ..?

1. Since perhaps might be transaction isolation level Read or DML operate some data from a snapshot older than other DML operations carried out by other end users concurrently .

2. In this case it read or DML operate the data entity based on old values not recent values…And this is most repeated while concurrent DML transactions

Hence To avoid such that ,you have to supersede it by transaction isolation level read committed using row versioning