We currently have an ongoing issue for some users regarding the Aurena Agent. Some users report that they cannot upload or download files due to the following error.
- EdmFile.The "EDM File" has already been removed by another user.
- Something went wrong when uploading the file using the Aurena Agent. Error message: Missing or empty mandatory parameter: odata
We have added the correct permissions to said users and have confirmed that the users have installed the .msi file and the chrome extension correctly.
Any and all advise would be greatly appreciated.
Thanks, Bryan
Page 1 / 1
What type(s) of Repository are you using?
Hi,
None of those errors have a clear explanation I think. If you can, you need to figure out in detail what steps those users are taking when they get the error.
Most probably, if they try again, they will get the same error, right?
If so, record the steps and report them back here, include as much information as you can. Enable the Aurena debug console and look at what happens there. Plus, follow the advanced troubleshooting instructions here and compare what happens when it works and when it doesn't work:
If this is too much or to complex, consider filing a support case.
And also, let us know what version you are on exactly.
Thanks!
Hi @bdoucette
I have seen this error in newly installed computers sometimes and it has something to do with registry values not being set correctly. Please check the suggestion mentioned in the below post to see if the issue will be solved.
We currently have an ongoing issue for some users regarding the Aurena Agent. Some users report that they cannot upload or download files due to the following error.
- EdmFile.The "EDM File" has already been removed by another user.
- Something went wrong when uploading the file using the Aurena Agent. Error message: Missing or empty mandatory parameter: odata
We have added the correct permissions to said users and have confirmed that the users have installed the .msi file and the chrome extension correctly.
Any and all advise would be greatly appreciated.
Thanks, Bryan
We are experiencing the same problem, after installing the Aurena Agent and Chrome plugin, we get an error when uploading a document!
EdmFile.The"EDM File"hasalready been removed by anotheruser.
Internal Server Error.
We're using the latest version of IFS Cloud, 23R1, and I've determined that this is a definite bug.
@Jackoly Have a look at the post that Amila linked to and see if that helps.
We also have a user experiencing this error (23R1.10) but intermittently and sometimes the document he is trying to attach attaches, sometimes it times out, sometimes this “EDM File removed..” error pops up.
Challenging to get the user to debug/report steps every time they need to attach a document…
Is there a definitive setup guide we can follow to overcome this ‘glitchy-ness’?
Thanks.
Linda
We also have a user experiencing this error (23R1.10) but intermittently and sometimes the document he is trying to attach attaches, sometimes it times out, sometimes this “EDM File removed..” error pops up.
Challenging to get the user to debug/report steps every time they need to attach a document…
Is there a definitive setup guide we can follow to overcome this ‘glitchy-ness’?
Hi,
Can you check if you have any macros installed in Docman? It's not uncommon that a "glitchy" macro creates symptoms like you describe.
We also have a user experiencing this error (23R1.10) but intermittently and sometimes the document he is trying to attach attaches, sometimes it times out, sometimes this “EDM File removed..” error pops up.
Challenging to get the user to debug/report steps every time they need to attach a document…
Is there a definitive setup guide we can follow to overcome this ‘glitchy-ness’?
Hi,
Can you check if you have any macros installed in Docman? It's not uncommon that a "glitchy" macro creates symptoms like you describe.
Thanks for engaging, @Mathias Dahl . We don’t have any Macros at all. We do have a custom event but that is to lift restrictions at the point a document is approved. Our user experiencing the issue just attaching a document - one with a Class that doesn’t have any approval workflow connected so I wouldn’t have expected that to impact ..? Maybe??
BEGIN IFSAPP.Client_SYS.Clear_Attr(attr_); IFSAPP.Client_SYS.Add_To_Attr('', '&NEW:DOC_NO', attr_);
doc_no_ := '&NEW:DOC_NO'; batch_desc_:= IFSAPP.Language_SYS.Translate_Constant('DOC_MAN_RESTRICT','DOCMAN001: Start Deferred Background - Set View access on document no: &NEW:DOC_NO'); ifsapp.Transaction_SYS.Deferred_Call('CB_DOC_MAN_RESTRICT.set_view_on_docman_', doc_no_, batch_desc_);
END;
Linda
@PRODQ
Thanks! What does the custom event trigger on? Which table and for what operations?
Perhaps you can disable the custom event for a little while and see if their problems persists?
Hi we are also having this issue time to time have you found a solution for this? I found that sometime this occur when the pdf is opend with another application but even without the file being open the error occurs and this is very annoying. We have Aurena agent installed.
We changed this default to Create Documents
Make sure User settings are like this…
And now attaching documents looks/work like this.
Since doing this we have had no further Doc Man issues. We did discover documents we thought had been attached to items hadn’t been even though a Document Revision had been created.
The ‘clue’ for those docs affected was that there was no ‘eye’ icon and the file type in the blue box was missing.
Not sure if this helps!
Hi we are also having this issue time to time have you found a solution for this? I found that sometime this occur when the pdf is opend with another application but even without the file being open the error occurs and this is very annoying. We have Aurena agent installed.
Hi,
Do you have any Docman macros running on the check in process?