Hi @kibsdk 

Make sure you have installed Aurena Agent (AA) and it is working as expected. AA is needed in order for macros to be exected in Aurena client. Also before running any complex macros, always make sure that the macros are working as expected by running a simple macro. (Ex. A simple script with a message box)

BR

Hi Amila

I have installed Aurena Agent, but it is actually not working as expected. Usually Aurena Agent helps open eg. a word document, when you press edit, but it does not for me..

I do not get any errors when installing the agent - or when trying to use it. And it says it is installed OK in my User Settings form.

Hi @kibsdk 

Testing the AA by editing a word doc would not be the best way as there could be a broken macro script that is running when the word is checked out for edit which prevents the opening of the document. you can do the same test by disabling macros for the given class or try to view a PDF file (Less chance of a macro being intervened). If AA still does not work, try to re install it and also make sure you have enabled the browser extension. Also, if you are testing from Chrome, try doing the same from Edge as well 

BR

Thank you for the tip - testing my AA now without macros - and it works as it should.

So I guess it is :

• either the macro scripts - but the same scripts run in another IFS Cloud environment and works there
• Or it is Macro security .. I got a message previously that Macros had been blocked. Then I tried to enable all macros to run in the MS Word Trust Center - and now the message is not appearing anymore but still the macros does not seem to work

@kibsdk best way to figure out would be to add message boxes in the macro code here and there and figure out from which line of code the execution breaks. 

Hi Amila - not sure how to do that.. but I found a set of macros that was working and now I got my macros up and running..

If you have a macro code example with message boxes - please share. It is probably not the last time I end up in this scenario..

Had a look in to the issue with @kibsdk and there were macros running inside word document other than Docman macros and probably those macros were causing permission problems. 

Issue was solved after clearing everything in C:\Users\<user>\AppData\Local\Microsoft\Windows\INetCache as well as the browser cache. 

Our documentation for macros has such an example and I think someone even posted the same or a similar example here.