Deployment: Are you using the hosted EaaSI service, or a local node?
EaaSI Version: This corresponds to the release branch/installer version used to deploy your instance. This information should be available in the Manage Node menu, if accessible
Application Version 1.8.17
Browser: The name and version of the browser you are using to access the EaaSI UI, if applicable
Firefox, though probably not applicable.
Description: Please describe your issue in as much detail as possible, including name + ID of any relevant environments, software or content. You can also attach screenshots or relevant error report files.
We were doing test imports for the 2019 Beta files. After importing the software, attempting to run it paired with the Windows 98 Test Env resulted in a error (attached log files).
We imported the Microsoft Encarta ISO and they produced the attached error log. If we paired the same environment with the same Encarta ISO imported from Yale it worked fine. I think there is an issue with our import process.
Similarly, we imported a private ISO for a Mac OS 9 instance, and it appears to have produced a similar error when we tried to run it with the “Add Software” option.
Are you able to reproduce the issue or did it happen once? What steps can you take to repeat the issue? What did you expect to occur and what was the actual outcome?
We expected in each case that the imported ISO would be present for inspection in the environment, but instead there was an error.
Urgency: If possible, please give an indication of how urgently the issue needs to be addressed - is there a timeline or deadline (e.g. upcoming demo, researcher request, etc.) that EaaSI support staff should be aware of?
I’m using this in coordination with both the University library and for active research with students currently, so not being able to import resources is preventing multiple research studies from proceeding. eaasi_error_1.log (86.6 KB) eaasi_error.log (11.4 KB)