Clarity

 View Only
Expand all | Collapse all

Jaspersoft Installation Failure

  • 1.  Jaspersoft Installation Failure

    Posted Dec 22, 2015 01:46 PM

    Hello,

     

    I've just upgraded from 14.2 to 14.3 on a linux box, User sync was working fine on 14.2, but here's what I get after having followed instructions :

     

    Failed to get an instance of ClarityJasperAdmin :: Exception getting ClarityJasperAdmin : Invalid AES key length: 8 bytes

     

    I've reinstalled Clarity and Jaspersoft from scratch, resetted NSA jaspersoft infos, gave a new name to my organization, csk installed, content loaded (admin content-jaspersoft csk -userName superuser -password superuser -retryCount 50).

     

    But when I run './admin jaspersoft keystore', I still have the same error message :

     

    [root@COPRSURVMK495 bin]# ./admin jaspersoft keystore

    WARN: Keystore not generated in META-INF/reporting/store directory.

    Error in saving keystore files in Database Generated keystore and its information for organization Name : coprime : orgnaization Id : Coprime in the following location : /app/clarity/config/ , Make them available in Jaspersoft installation in the following directory : <Jaspersoft Tomcat>\webapps\<jasperwebcontext>\WEB-INF\config\

     

    Result is :

                    - 2 files created in /app/clarity/config/ Coprime.properties and Coprime.jks

                    - Only 1 file created in /app/clarity/META-INF/reporting/store/ Coprime.jks

     

    I copied /app/clarity/config/ Coprime.properties and Coprime.jks to /app/tomcat_jasper/webapps/reportservice/WEB-INF/config/

     

    Then Restarted Jaspersoft..

     

    I launched Jaspersoft users sync job and getting back to that AES error :

     

    Failed to get an instance of ClarityJasperAdmin :: Exception getting ClarityJasperAdmin : Invalid AES key length: 8 bytes

     

     

    Any idea ? it's something like 30 hours spent to install/uninstall, end no result except that result..

     

    Thanks,

     

    Julien D



  • 2.  Re: Jaspersoft Installation Failure

     
    Posted Dec 22, 2015 05:43 PM

    Hi @Julien_Demailly I have moved this question to a new discussion as the Tuesday Tip you had it attached to is becoming a VERY long and hard to manage thread. You will likely get better response in a new thread. Thanks, Chris



  • 3.  Re: Jaspersoft Installation Failure
    Best Answer

    Broadcom Employee
    Posted Dec 22, 2015 06:28 PM

    Hi Julien,

     

     

    This issue looks to be due to the keystore generation. It might be due to specific OS environment configuration.
    Try the following workaround:

     

    1. Manually copy the missing Coprime.properties to /app/clarity/META-INF/reporting/store/
    2. If this works fine please restart Jaspersoft and see if that fixes it

     

    If you still have an issue, please try the following:

     

    1. Specify the organization in lower case in CSA, for example: coprime. Don't use upper case or mixed case.
    2. Then please rerun the admin jaspersoft keystore command and see if the files get created properly, and organization name is lowercase
    3. If they do, try restarting the Jaspersoft server and see if that helps

     

    Please let me know how it goes.

     

    Kind Regards

     

    Nika Hadzhikidi
    CA Technologies
    Principal Support Engineer



  • 4.  Re: Jaspersoft Installation Failure

    Posted Dec 22, 2015 07:07 PM

    Hello Nika,

     

    Problems are always coming from little details...

     

    I've entered the value coprime in lower case and it solved my problem :

     

    ./admin jaspersoft keystore

    Generated keystore and its information for organization Name : coprime : orgnaization Id : coprime in the following location : /app/clarity/config/ , Make them available in Jaspersoft installation in the following directory : <Jaspersoft Tomcat>\webapps\<jasperwebcontext>\WEB-INF\config\

     

    As explained before, this is an upgrade, and on the initial version (14.2) 'Coprime' was set and it worked fine, reason why I didn't try to change that value. I guess the difference comes from Java version (1.7 for 14.2 ; 1.8 for 14.3).

     

    My users can now syncronize.

     

    Thanks a lot for your answer,

     

    Julien



  • 5.  Re: Jaspersoft Installation Failure

    Posted Apr 18, 2016 09:30 AM

    Hi is this registered as a BUG that will be fixed in the near future?



  • 6.  Re: Jaspersoft Installation Failure

    Broadcom Employee
    Posted Apr 18, 2016 09:55 AM

    Hi Nadine,

     

    Yes, I raised this as defect: CLRT-79609 Jaspersoft keystore .properties file does not generate on UNIX systems when Upper case or Mixed case is used in Tenant's Name
    It's currently in Sustaining Engineering's backlog, and will be addressed in a next release.

     

    Hope this helps -Nika



  • 7.  Re: Jaspersoft Installation Failure

    Posted Aug 04, 2016 10:20 AM

    ??



  • 8.  Re: Jaspersoft Installation Failure

    Posted Oct 24, 2016 01:55 PM

    Hello NIka, 

     

    We are on 14.2 with JS 5.6 and upgrading to 14.3 with JS 6.1. Based on this thread appears there is an issue if Organization name has Capital Letters or Mixed CapLower letters.

    Was this bug ever fixed for 14.3? Not sure if it is fixed in 14.4 or not. The problem is we have few reports in CABI and we cant go for 14.4 until we migrate all our reports to JS. 

    Please advise. Thanks in advance. 

     

    CLRT-79609 ? 



  • 9.  Re: Jaspersoft Installation Failure

    Broadcom Employee
    Posted Oct 24, 2016 02:27 PM

    Hi Guru,

     

    No, CLRT-79609 is not yet fixed in neither 14.3 or 14.4. So if you are on a UNIX system, I’d recommend you use lower case for your organization name. I’ll let you know as soon as there is an update on ETA on this fix.

     

    Thank you -Nika



  • 10.  Re: Jaspersoft Installation Failure

    Posted Oct 24, 2016 02:47 PM

    Thanks a ton for quick response Nika.

    Is there a tested/proven/recommended solution to export jasper contents from "OrgName" to "orgname"? 

    Earlier i exported all contents to a zip file and replaced all occurrences of "OrgName" to "orgname". As import wont work if orgnames are diff. This approach changed all Report Names, Report IDs along with Organization name. Whereas my requirement is only to change orgname and keep rest of the contents (ReportNames,ReportIds) unchanged. 

     

    Also per release notes i cant export contents using command line. I dont see the option at all. 

    I can export/import via UI though.  

    Thanks. 



  • 11.  Re: Jaspersoft Installation Failure

    Posted Oct 31, 2016 04:41 PM

    Nika and team - Any idea if CLRT-79609 is fixed in PPM 15.1?



  • 12.  Re: Jaspersoft Installation Failure

    Broadcom Employee
    Posted Nov 01, 2016 03:48 PM

    Hi Guru - no this is not yet fixed. If you wish a fix in a patch, please raise a Support issue and let me know the case number. Thank you! -Nika



  • 13.  Re: Jaspersoft Installation Failure

    Broadcom Employee
    Posted Jun 12, 2017 05:35 PM

    Guru, everyone,

     

    This issue was resolved in CA PPM 15.2, any version before that will have to follow the workaround. Please let me know for any questions.

     

    Thank you -Nika



  • 14.  Re: Jaspersoft Installation Failure

    Posted Nov 06, 2018 04:00 AM

    Hi Nika,

     

    I have some serious problem while installation  of my Jaspersoft .

    Currenly my Clarity is 15.2 and Jaspersoft is 6.2.1 and everything works fine here.

    Now i am upgarding my clarity to 15.4.1 and Jaspersoft to 6.4.2

    I have Upgraded my OS 2016  for Clarity and OS 2012 R2 standard for Jaspersoft. DB : Upgraded to Oracle 12c.

    When i am trying to install the Jaspersoft on my machine. it gives me the below error.

    E:\jsins\buildomatic>echo off
    Buildfile: E:\jsins\buildomatic\build.xml
         [echo] Filtering properties (cleaning out blank spaces)
    [encrypt-props] The master properties have already been encrypted. To re-enable the encryption, make sure the passwords are in plain text, set master property encrypt to true and remove encrypt.done.
         [echo] chkIfPackageManagedTomcat: check if package managed tomcat
         [echo] Tomcat DBCP Factory: com.jaspersoft.jasperserver.tomcat.jndi.JSCommonsBasicDataSourceFactory
         [echo] chkAndSetLocaleDbSettings: parse: scripts.properties for db commands
         [echo] chkIfPackageManagedTomcat: check if package managed tomcat
         [echo] using settings file: E:/jsins/buildomatic/build_conf/default/maven_settings.xml

     

    import-minimal-pro:
         [echo]  
         [echo] Property values (in install.xml):
         [echo]  archiveArg = --input-zip=E:/jsins/buildomatic/install_resources/export/js-catalog-oracle-minimal-pro.zip
         [echo]  dbType = oracle
         [echo]  jdbcJar = ojdbc8-12.2.0.1.0.jar
         [echo]  currentConf = E:/jsins/buildomatic/build_conf/default
         [echo]  importExportConfig = E:/jsins/buildomatic/conf_source/iePro
         [echo]  
         [echo] Validating JasperServer database connection at jdbc:oracle:thin:@OORD003A.EU.UNILEVER.COM:16255:OORD003A. Phase: [import-export-test]
         [echo] For JDBC driver the artifactId and version properties are set:
         [echo]   maven.jdbc.artifactId=ojdbc8
         [echo]   maven.jdbc.version=12.2.0.1.0
         [echo]   Specified JDBC driver jar exists
    [select-sql] Executing commands
    [select-sql] 1 of 1 SQL statements executed successfully
         [echo] For JDBC driver the artifactId and version properties are set:
         [echo]   maven.jdbc.artifactId=ojdbc8
         [echo]   maven.jdbc.version=12.2.0.1.0
         [echo]   Specified JDBC driver jar exists
    [select-sql] Executing commands
    [select-sql] 1 of 1 SQL statements executed successfully
         [echo] Connection OK
         [java] First resource path:E:\jsins\buildomatic\conf_source\iePro\applicationContext-adhoc-dataStrategy.xml
         [java] Started to load resources
         [java] Resource name: applicationContext.xml
         [java] Resource name: applicationContext-MongoDbJDBCDataSource.xml
         [java] Resource name: applicationContext-adhoc.xml
         [java] Resource name: applicationContext-adhoc-dataStrategy.xml
         [java] Resource name: applicationContext-adhoc-repository.xml
         [java] Resource name: applicationContext-audit.xml
         [java] Resource name: applicationContext-azure-sql-datasource.xml
         [java] Resource name: applicationContext-cascade.xml
         [java] Resource name: applicationContext-cascading-pro.xml
         [java] Resource name: applicationContext-catFactory.xml
         [java] Resource name: applicationContext-data-snapshots.xml
         [java] Resource name: applicationContext-datarator.xml
         [java] Resource name: applicationContext-diagnosticCollectors-pro.xml
         [java] Resource name: applicationContext-el.xml
         [java] Resource name: applicationContext-el-operators.xml
         [java] Resource name: applicationContext-events-logging.xml
         [java] Resource name: applicationContext-export-config.xml
         [java] Resource name: applicationContext-export-import.xml
         [java] Resource name: applicationContext-export-import-audit.xml
         [java] Resource name: applicationContext-export-import-multi-tenancy.xml
         [java] Resource name: applicationContext-export-import-pro.xml
         [java] Resource name: applicationContext-export-import-report-options.xml
         [java] Resource name: applicationContext-formatting.xml
         [java] Resource name: applicationContext-jms.xml
         [java] Resource name: applicationContext-logging.xml
         [java] Resource name: applicationContext-messages-pro.xml
         [java] Resource name: applicationContext-multiTenancy.xml
         [java] Resource name: applicationContext-multiTenancy-security.xml
         [java] Resource name: applicationContext-olap-connection.xml
         [java] Resource name: applicationContext-pro-remote-services.xml
         [java] Resource name: applicationContext-profiling.xml
         [java] Resource name: applicationContext-propertyChangers.xml
         [java] Resource name: applicationContext-propertySettings.xml
         [java] Resource name: applicationContext-remote-services.xml
         [java] Resource name: applicationContext-report-options.xml
         [java] Resource name: applicationContext-report-scheduling.xml
         [java] Resource name: applicationContext-search.xml
         [java] Resource name: applicationContext-search-pro.xml
         [java] Resource name: applicationContext-security.xml
         [java] Resource name: applicationContext-semanticLayer.xml
         [java] Resource name: applicationContext-themes.xml
         [java] Resource name: applicationContext-themes-pro.xml
         [java] Resource name: applicationContext-virtual-data-source.xml
         [java] Resource name: applicationContext-virtual-data-source-query-service.xml
         [java] Tenant not found with Tenant ID "organizations"
         [java]  -- JasperServer:  EhCacheImpl shutdown called.  This normal shutdown operation.
         [java]  -- JasperServer:  EhCacheImpl calling cleanerTimer.cancel().  This normal shutdown operation.
         [java]  -- JasperServer:  ProfileAttributeCacheImpl shutdown called.  This normal shutdown operation.
         [java] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=64m; support was removed in 8.0
         [java] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0

     

    BUILD FAILED
    E:\jsins\buildomatic\bin\import-export.xml:321: The following error occurred while executing this line:
    E:\jsins\buildomatic\bin\import-export.xml:203: Java returned: -1