Attachment_ID field blank when using Document Attachment Management

(0) Share

Report

Posted on by jpaul246

When adding an attachment to a customer, the attachment_ID field in tables CO00101, CO00102, CO00104 and CO00105 is blank. When this procedure is adding the 2nd record to the tables, error "A save operation on table 'coAttachMSTR' has created a duplicate key" occurs. This problem happens on all workstations, with any login from sa to another user and any company on GP 2013 (12.00.1482 SP2). I appreciate you reading this post and posting any possible solutions. I have provided multiple traces to Microsoft Support for assistance for about a month without any solution. I assume that the problem lies in the function or procedure trying to create the attachment_ID field or a SQL security problem in calling the function or procedure. This problem does not stop the user from using GP. Again, Thanks for any assistance!

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (1)

Verified answer

jpaul246 on at

Like (0)

Report

Microsoft finally reported that GP uses ADO.NET (a Dexterity Shared Component) to reconnect to SQL in Document Management Attachment and the Dexterity setup maybe causing the problem. After additional research by myself and this info, I was able to solve the problem by changing my ODBC server name in ODBC Data Source Administrator from (server name, port) to (server name\instance name, port) whereby including the name of the 2nd instance running on SQL. I assume GP strips this info from the ODBC to create the connection string and now I have a valid connection string! :)

Was this reply helpful? Yes No
Suggested answer

Abdulrahman Alshaikh 5 on at

Like (0)

Report

The problem may result if the "DexteritySharedComponents" is not installed in the PC.

First find out if the Dexterity Shared Components is installed or not (Control Panel>Programs>Programs and features), if it is not installed you can install it from the GP installer media under the file (DexteritySharedComponents) match the correct installer to your OS type (x86 for 32bit, and x64 for 64 bit OS)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I'm encountering a similar issue with blank Attachment_ID in the tables you mentioned however the difference for me is that I'm able to attach without any issues using the sa account; I just can't do it using any other account (no matter what Dynamics or SQL permissions are granted).

Any thoughts?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I am having the exact same issue where using the sa account - the attachments seem to work fine where I can view existing attachments and add new attachments. Although I did notice that I dont see any files getting added in the share folder that i have mapped in the Dex.ini file. Since I have mapped a specific folder, I would assume files would show up

When i try adding attachment with any other user account (even with power user access) i get the error (a save operation on table 'coAttachMSTR' has created a duplicate key)

and if i try to open existing attachments with any user other than sa, I get the error 'Unable to preview the attachmment'

I have checked the mapping in Dex.ini file and have reviewed that there is a folder created based on the company name and OLE notes e.g. c:/GPShare/Notes/CompanyName/OLENotes/

Would appreciate any help anyone can provide.

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report

Hello Prem

In which version do you encounter this issue ? If it is 2015 R2, then this is a different problem than the one reported in this thread.

It has been reported on MSConnect, check this thread for further details Document Attach Issue

Was this reply helpful? Yes No
jpaul246 on at

Like (0)

Report

My company upgraded to a live version of GP 2015 R2 on July 15, 2015 and we now have the same problem again. My mistake as we forgot to test the document attachment process with a different user name other than "SA" in my test migration a month ago. I have spent the last few days testing various combinations of the ODBC, setting up various aliases, checking my SQL settings and I have not discovered any solution. I did have another security problem with the Excel Builder. I was not able to run my excel reports until I set up an alias using "Named Pipes". If I find a solution to the attachment problem, I will post 1.

Was this reply helpful? Yes No
Navin Mirpuri on at

Like (0)

Report

Hello Mahmoud,

We are facing the issue in GP 2015 R2.

If I understood the comments in the thread correctly it indicated that is the issue is occurring in GP 2015 R2 then it has been submitted as a bug in MS Connect and we have yet to receive a solution? (although in the link you provided for MS Connect - it shows resolved. Has anyone tested it with the May hotfix by any chance?)

And the ODBC solution provided pertains to version prior to GP 2015 R2?

Just trying to clarify since I am desperate to find a solution for this client that we just upgraded. It was working for them before and with the new version its not so a bit difficult to explain how the latest version is not the best :(

Was this reply helpful? Yes No
Mahmoud Saadi 32,738 on at

Like (0)

Report

Hello Navin

You just got it perfectly right, this seems as a quality issue in Dynamics GP 2015 R2 for all the users other than the sa.

The issue is reported to MSConnect, the support team indicated that a future resolution will be provided.

Add your vote on MSConnect, to get this resolved as soon as possible.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Yes; this issue is particular to GP2015 and GP2015 R2. We have created a support request with MS and they confirmed that this is a bug and they do not have a workaround for it. I've tried modifying the ODBC connection and SQL permissions to no avail.

The good news is that MS will be releasing a patch to address the issue next week (it was scheduled for this week but was delayed).

Hopefully we just need to hold out a bit longer.
Finansys

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (0)

Report

Hi All,

This is issue in GP 2015 R2. We need to update our system to latest hot fix(804) from below link and it will resolve the issue.

https://mbs2.microsoft.com/fileexchange/downloadfile.aspx?fileid=11c673cf-1c1a-4c5e-bfc6-5bc6659bbe65

Hope this helps!!!

Was this reply helpful? Yes No