The ASWStandard Library is made up of two separate libraries, the ASWGlobal and TraceLevel library. To get past the ASWStandard check, both secondary libraries need to listed in the Programs list, and both libraries need to have their subfolders/files present in the “C:\Program Files (x86)\Hamilton\Library\ASWStandard” folder:
My suggestion would be to uninstall the ASWGlobal and TraceLevel libraries from the Programs List, delete the “C:\Program Files (x86)\Hamilton\Library\ASWStandard” folder, then reinstall the ASWStandard library. This will make sure all of the correct folders/files are present.
Why does the Hamilton PDF Report Generator library need access to the “Hamilton PDF Report Generator.log” file?
We need the “Logfiles” folder to be set to write-once, and therefore, the library cannot have continuous access to the “Hamilton PDF Report Generator.log” file.
I just tested with a method in my VM, but as far as I see it only needs access when it is called upon. Just like your regular logfile would have. How do you work with a method and only have the folder to be write-once?
Out of curiosity, what requirement needs this? Is this a local requirement or a IVD requirement? I am developing methods with IVD in mind, so it would be nice to prep for this if needed.
All the files in this folder are write-once, and a new regular log file is generated every time the method is executed. On the other hand, the PDF generator library appends logs to an existing log file.
We need this setup for GMP, and we want to avoid the possibility of modifying regular Trace files.
The log for the PDF report generator is not really needed, but it prevents the method from finishing.
