We are getting this message “Entity DmsStorageType with specified keys is not found” as part of a large stack message… any stabs at what might be the issue?
We use attachment links for the attachments in our environment and get this whenever we try to download or view them. Tried searching high and low for anyone with same issue.
We use attachment links and after the upgrade to 2025.2.7 (cloud) the attachment links still work ok.
Thanks for confirming that to me. Was wondering if anyone else had an issue that may have come from an older version to the newest one.
I think it’s because our document type is blank on every XFileRef record and I think with the newer versions it’s required whereas in the older one’s when these attachment links were created, it wasn’t… waiting on support to confirm…
2025.2 in Gov Cloud. Not the same message but all our local attachments now say “Error received from Edge Agent Unable to validate call”. They were working before the update and other Edge Agent functions are working (printing, classic screens).
Alexander, feel free to submit a case and reference ours CS0005242054.
Tell me something, when you query the XFileRef table, do your records have a DocTypeID defined or are they blank?
Do you have some records that do have a DocTypeID defined? IF so, do those work fine? Does the DocTypeID on those rows exist in Document Type Entry?
What is in the Edge Agent log, you can reach it from tray application context menu
Empty doctype always meant company default attachments.
Did you check that your link attachment type did not lose Company Default checkbox:
That is set, that’s the first thing I checked.
I see. This is a bug in Edge Agent, it looks for file attachment instead of links.
Okay thank you Olga as always. What do we do then? I found that if I make a Document Type called “Default” and link it to that attachment type you pictured above and then DMT that onto all of my xfileref records, the edge agent works…
What do we do, use the workaround or wait for edge agent?
Better wait, then you won’t need to do anything.
I don’t know what waiting means because our users need to be able to view these attachments as part of the ISO process in manufacturing. I may just have to act. I was just trying to get a sense of timing.
Are you going to relay this to support on our case, or? Is there any way you can relay the supporting tests you did so I can relay it to them and get a PRB started?
Well it will take time to fix and test in any case.
If you cannot wait, then you have to switch.
Also if people only view them and not add new, then maybe adding fake file attachment as default will help…
Thanks for this. Adding “Default” to mine also allowed it to open.
When you say that, did you create a document type called “Default” or did you just DMT the word “Default” in the DocTypeID column without creating the document type?
Thanks Olga, so you have communicated the details of the problem to the team handling our cases? Or do I need to link this thread to my ticket?
I created a document type called “Default” first.
you always can communicate to them too.
Okay yeah, I will do that regardless then every time. Thanks so much Olga for everything.
