J
Jamal
All,
I have posted this issue before and with the help of the group I was able to
recreate the problem and in a not so good way temporary get rid of it..
When we run IM at time this error would come up which prevent us from
loading data to the system.
DOC 1 ERROR: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of
PRIMARY KEY constraint 'PKSOP40500'. Cannot insert duplicate key in object
'dbo.SOP40500'.
I ran a trace and saw where IM is trying to insert a master key for the
newly created document into the SOP40500 table. I checked the master key
being inserted and found that it already exists in the SOP table. I went to
the Transaction screen and tried to create an invoice to see if new document
are inserting into the SOP40500 table and saw that a new master key was
created. I didn't save the invoice and thereafter ran IM and the problem was
gone. Can some of you experts shed light on what might be happening here.
Jamal
I have posted this issue before and with the help of the group I was able to
recreate the problem and in a not so good way temporary get rid of it..
When we run IM at time this error would come up which prevent us from
loading data to the system.
DOC 1 ERROR: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of
PRIMARY KEY constraint 'PKSOP40500'. Cannot insert duplicate key in object
'dbo.SOP40500'.
I ran a trace and saw where IM is trying to insert a master key for the
newly created document into the SOP40500 table. I checked the master key
being inserted and found that it already exists in the SOP table. I went to
the Transaction screen and tried to create an invoice to see if new document
are inserting into the SOP40500 table and saw that a new master key was
created. I didn't save the invoice and thereafter ran IM and the problem was
gone. Can some of you experts shed light on what might be happening here.
Jamal