I installed Automise 5.5 today, and I have been following the instructions from the blog about how to change the encryption in each project to AES256 in the Project Information. When I try to change the Encryption Algorithm to AES256 then hit OK and try to save the project, the crash screen comes up with “An error occurred in the application”. I can see the bug report, but cannot send it because there is no email set up on the box where this is occurring. This has happened with 3 of the 4 projects I have tried this with. I have tried restarting the application, closing the application, and continuing the application - none of these solve the issue.
The whole reason to install 5.5 was to be able to assign the AES256 algorithm to the projects in our library, so I am hoping that there is an easy fix to this. If there is a way to save the bug report and then email it to you manually, please let me know.
Note - I will be OOO on Friday and Monday, but will be able to try any potential workarounds next week.
Have a look in your %TMP% folder for a bug report.txt file.
If at all possible could you send the project file to support. It sounds like its failing in one of the actions during serialisation, having the project file will make it a lot quicker to find.
P.S - I am travelling for the next few weeks (heading to a conference in Amsterdam and then London) - so really hoping to get this resolved before I leave tomorrow. I’ll see if I can reproduce it here but there are a lot of actions so finding which action is the offending one is going to take time.
As I stated, I was OOO on Friday and am OOO tomorrow as well. It is not just one project that is having the problem…so far only 1 out of 5 projects was able to successfully change the encryption settings. If there is anything I can do to help (I will look for the bug report.txt file), please let me know.
The quickest way for us to resove this will be by looking at the project files to try and narrow down the actions it uses - not all actions have encrypted properties so once we see the projects we should be able to find it pretty quickly.
Email them to support @ finalbuilder.com - only our staff and yourself will be able to see the files and we’ll delete them (and the attachements from the case) once the issue is resolved. We won’t need to run the projects, but if possible leave the passwords etc intact as it may be an issue specific to the values.
The bug report will also be helpful if you can find it.
I have sent two project files as directed. Cannot figure out where the bug report text file lands when created, but can send screenshots of it if needed.
Thanks - I can reproduce here using your projects on a fresh install. The issue is that by default validation is performed when saving a project, in my dev environment I had that turned off so never saw the error. Looking into a fix now.
Apologies for the slowness of this update. I’ve been working though the actions dealing with this bug - there are a lot of actions that need to be checked. At the current rate I suspect it will be next week at the earliest for the updated release.