Converting a Jaspersoft Studio project to a JasperReports IO project results in a 'Service Unavailable' error in Studio - org.apache.http.client.HttpResponseException: Service Unavailable at com.jaspersoft.studio.jrio.server.JrioRunner.lambda...

Converting a Jaspersoft Studio project to a JasperReports IO project results in a 'Service Unavailable' error in Studio -
org.apache.http.client.HttpResponseException: Service Unavailable
at com.jaspersoft.studio.jrio.server.JrioRunner.lambda$1(JrioRunner.java:144)
...

Problem:
A report compiles and runs fine in Jaspersoft Studio in standard mode (JasperReports Library), but converting this into a JasperReports IO project results in a 'Service Unavailable' error in Studio -
org.apache.http.client.HttpResponseException: Service Unavailable
at com.jaspersoft.studio.jrio.server.JrioRunner.lambda$1(JrioRunner.java:144)
...



Cause:
This issue may arise when a user is working in a domain environment as a “normal” user or maybe not using Jaspersoft Studio with a kinda local administrator account, which may block the ability of Jaspersoft Studio / JasperReports IO to expand some artifacts or write some additional/mandatory files. Usually most internal Eclipse operations (therefore Jaspersoft Studio) are performed using the workspace (i.e. the .metadata folder), and to work with the same and edit or make changes to configuration file, like Jaspersoft Studio Professional.ini file, we require privileged credentials.

Solution:
Following suggestions can be followed for the above causes of the issue:
1. With a low level domain user, have domain admin add the ability to write for normal users in the Jaspersoft Studio Installation folder (for example, C:programstibcojss installation).

2. With a user also having the local machine administrator credentials, try to run the scenario at least once with the privileged credentials (for example, Run as administrator on Windows).