JasperStudio Update failed because wrong path of binary

Changed Status from New to Feedback Requested

Changed Assigned User from - to @mrabbi

---

Hi, not sure which script you are referring to.Can you please detail?Thanks.Best regards,Massimo.

The installation of the plugin update runs until a point in in which the installation routine tries to change the file system rights of updated script. I guess this will only happen in UNIX environments. Windows does not need such a command.

I'm not actually understanding where you see this command being executed / run.

Can you please register a screencast of the problem?

 

Moreover from the extract you posted it seems that you are trying to upgrade the RCP application and not the plugin one. Starting from which version?

I personally tried to upgrade from the 6.10.0 to latest 6.12.2 (MacOS 10.15.3) using the internal update mechanism and it worked fine. The only thing I noticed is that the automatic restart seems to not being "considered". But when I double clicked on the application it started correctly the updated version.

 

Besides this "restart now" not being considered, something we might want to check, I don't get where you found out this chmod message. I don't recall we do something on purpose for it.

 

Please register a screencast and details on the versions of JSS + OS.

 

Thanks.

Regards,

Massimo.

Changed Resolution from Open to Unable to Reproduce

Changed Status from Feedback Requested to Closed

---

Why do you cannot reproduce it. I had actually show exactly where the problem is!

Did you had tested it on a Mac or on Windows?

The shell commands are created by the studio itself. And the last one fails. Why is that hard to understand?

I have uploaded the error message from jasper studio

Changed Status from Closed to New

---

Changed Resolution from Unable to Reproduce to Reopened

---

Changed Resolution from Reopened to Unable to Reproduce

Changed Status from New to Closed

---

Hi, there is nothing "hard to understand". As mentioned in my message I tried to upgrade from a version 6.10 to a 6.12.2. And those are the results.Moreover I just tried with an existing 6.13.0 and I upgraded to a 6.16.0, always on a Mac OS X 10.15.3 and it worked the same.I asked about those stuff because for example in your initial message it was not clear from which version you were upgrading from. And only now I see from the screenshot your original installation was a 6.4.3. But maybe you upgraded to newer versions already in the past, I can only assume that. The reasons why something can not be reproduced can be multiples, like for example the workspace, OS version configuration or like probably in this case the upgrade story. For example that error message is the first time I see it.That said since it's something that seems not easy to debug I would recommend to move to the most recent version directly.Regards,Massimo.