Issues in connecting Jaspersoft Studio Professional 6.0.1 to JasperReports Server Professional 5.6.1

0

I'm having issues connecting Jaspersoft Studio Professional 6.0.1 to JasperReports Server Professional 5.6.1.  My installation is on Mac OS X 10.9.5 with Java(TM) SE Runtime Environment (build 1.7.0_11-b21).

I confirmed that the username and password are correct.  When trying to connect with default setting, I get the following exception:

--------------------------------------------------------------------------------

    java.lang.UnsupportedClassVersionError: com/jaspersoft/studio/server/protocol/restv2/JSSApacheConnectorFactory
        at com.jaspersoft.studio.server.protocol.restv2.RestV2ConnectionJersey.connect(RestV2ConnectionJersey.java:134)
        at com.jaspersoft.studio.server.protocol.ProxyConnection.connect(ProxyConnection.java:86)
        at com.jaspersoft.studio.server.WSClientHelper.checkConnection(WSClientHelper.java:82)
        at com.jaspersoft.studio.server.wizard.ServerProfileWizard.connect(ServerProfileWizard.java:99)
        at com.jaspersoft.studio.server.wizard.ServerProfileWizard.access$1(ServerProfileWizard.java:95)
        at com.jaspersoft.studio.server.wizard.ServerProfileWizard$2.run(ServerProfileWizard.java:76)
        at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

--------------------------------------------------------------------------------

The following question on this site address the same issue:

http://community.jaspersoft.com/questions/845486/jaspersoft-studio-601-d...

I tried checking the "Use SOAP protocol only" option as suggested in this thread.  This caused the following error instead:

--------------------------------------------------------------------------------

AxisFault
 faultCode: {http://xml.apache.org/axis/}HTTP
 faultSubcode:
 faultString: (401)Unauthorized
 faultActor:
 faultNode:
 faultDetail:
    {}:return code:  401
<html><head><title>Apache Tomcat/7.0.55 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 401 - Bad credentials</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Bad credentials</u></p><p><b>description</b> <u>This request requires HTTP authentication.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.55</h3></body></html>
    {http://xml.apache.org/axis/}HttpErrorCode:401

(401)Unauthorized
    at org.apache.axis.transport.http.CommonsHTTPSender.invoke(CommonsHTTPSender.java:221)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at com.jaspersoft.ireport.jasperserver.ws.RepositorySoapBindingStub.list(RepositorySoapBindingStub.java:336)
    at com.jaspersoft.ireport.jasperserver.ws.WSClient.getVersion(WSClient.java:155)
    at com.jaspersoft.studio.server.protocol.soap.SoapConnection.getServerInfo(SoapConnection.java:107)
    at com.jaspersoft.studio.server.protocol.soap.SoapConnection.connect(SoapConnection.java:128)
    at com.jaspersoft.studio.server.protocol.ProxyConnection.connect(ProxyConnection.java:86)
    at com.jaspersoft.studio.server.WSClientHelper.checkConnection(WSClientHelper.java:82)
    at com.jaspersoft.studio.server.wizard.ServerProfileWizard.connect(ServerProfileWizard.java:99)
    at com.jaspersoft.studio.server.wizard.ServerProfileWizard.access$1(ServerProfileWizard.java:95)
    at com.jaspersoft.studio.server.wizard.ServerProfileWizard$2.run(ServerProfileWizard.java:76)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

--------------------------------------------------------------------------------

I tried implementing the suggestions in the following post:

http://community.jaspersoft.com/jaspersoft-studio/issues/3205

This did not resolve the issue.  Any help in resolving this matter will be greatly appreciated.

iterio.solutions's picture
Joined: Jan 9 2015 - 9:17pm
Last seen: 4 years 5 months ago

2 Answers:

-1

You're suppose to be using the same version of Jaspersoft Studio as JasperReports Server. Switch Jaspersoft Studio to 5.6.1 or upgrade JasperReports Server to 6.0.1.

hozawa's picture
44219
Joined: Apr 24 2010 - 4:31pm
Last seen: 1 month 6 days ago

My colleague did not have any issues connecting Jaspersoft Studio Professional 6.0.1 to JasperReports Server Professional 5.6.1. We believe the problem may have something to do with the fact that he is using the Windows version while I am using the Mac version.

We need to upgrade to Studio 6.0.1 because version 5.6.1 reorders our report parameters when the jrxml files are pushed to the server. This is extremely annoying and results in a bad customer experience.

iterio.solutions - 4 years 5 months ago

Studio has the ability to set the Jasper Reports library version in a server connection. In Studio 6.0.1, the server library options are 6.0.0, then 5.5.2. If that is truly important, then what happened to 5.6.1 as an option?

jay_2 - 4 years 5 months ago

The compatibility setting in Jasper Studio is for JRXML source code only. With this setting, user will be able to use current version of the design tool to create a report template that is compatible with a prior version of JR engine. Since there's no JR API changes between 5.5.2 and 5.6.1, user can use JR 5.5.2 to run report with JR 5.6.1 template (jrxml file).

As for the compatibility issue between Jasper Studio and JasperReports Server, user should use the same release version between the two to ensure web services call used in the Studio to communicate with JRS are compatible to the server application, as stated in Mr. Ozawa's comment.

The compatibility setting in Jasper Studio has nothing to do with web services call to the server application.

tchen - 4 years 5 months ago
show 1 more...

That makes no sense at all. Why on earth would you have such a version compatibility setting when it isn't appropriate to use it?

jay_2 - 4 years 5 months ago
0

Hi,
please give a look to my answer to a similar thread: http://community.jaspersoft.com/questions/847421/remote-access-rest-not-...

Regards,
Massimo.

mrabbi's picture
6800
Joined: Oct 31 2011 - 9:20am
Last seen: 1 day 4 hours ago
Feedback
randomness