Actually, I think I had a similar problem: http://www.nabble.com/Violation-of-PRIMARY-KEY-constraint-%27PK_SERVER_HIT%27.-Cannot-insert-duplicate-key-in-object-%27ofbiz.SERVER_HIT%27-tp23479493p23479493.html
Weixue Zhang wrote: > > I am using ms sql server 2005 and this problem had bothered me for long > time. At last I found it was caused by a few unique indices of some tables > (You can find them by searching with "unique="true"" in files > entitymodel.xml). After I changed them into "unique=false", demo data > works fine. Can anybody explain why this problem doesn't exist with other > database servers, and why we need to set unique=true at some indices while > most others are unique=false? > -- View this message in context: http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p25019038.html Sent from the OFBiz - User mailing list archive at Nabble.com.
