RE: coattachMSTR error GP 2013 R2
Hi Sean,
The two main causes we've seen for this error message, are as follows:
1. The ODBC System DSN that Dynamics GP 2013 is using, is not setup as per the settings in KB 870416, with a 'Server' or 'Server\Instance' name value for the SQL Server name. What happens is that in the CO00101 table, the Attachment_ID column, which is the primary key for the table, will be blank, and because of this, any subsequent attachments will throw the violation key error because two records will have the primary key column, Attachment_ID, as blank.
2. We've also seen this issue occur if the file or document that you're attempting to attach is currently open, because it cannot be attached with the document open, due to processes that are being run in the background.
Other possible causes are:
* Unsupported environment using multiple Dex.ini files.
* Dynamics.exe.config file renamed as a result of attempting to resolve another issue
I hope this information helps.
Thanks,