DX NetOps

 View Only
  • 1.  The capm_reports-xxxx.zip package on 20.2 capc

    Posted Oct 23, 2020 09:00 AM
    Hello Community

    When I upgrading the CAPC to 20.2 the groups in jasper reports disapeared as you can see in this image below:


    So I've tried to run install.bat from The capm_reports-xxxx.zip package in CAPC new and got this message:

    --------Start installing--------
    "Get CABI install path from Windows registry: E:\CA\JASPER "
    java path is "E:\CA\JASPER \jre\bin\java.exe"
    Thu 10/22/2020 14:21:38.95 There is no java.exe in the directory
    Thu 10/22/2020 14:21:38.95 Installation failed

    What i need to do to fix this error ?




    ------------------------------
    Valéria Revheim
    ------------------------------


  • 2.  RE: The capm_reports-xxxx.zip package on 20.2 capc

    Broadcom Employee
    Posted Oct 26, 2020 03:51 PM
    Hi Valeria,

    Only reference to that specific error I've found was part of larger problems on the CABI server itself.

    Is there a java.exe present in the E:\CA\JASPER\jre\bin directory?

    If yes, who owns it? What are it's current permissions?

    Thanks,
    Mike

    ------------------------------
    Technical Support Engineer IV
    Broadcom
    ------------------------------



  • 3.  RE: The capm_reports-xxxx.zip package on 20.2 capc

    Posted Oct 26, 2020 05:49 PM
    Hello Michael,

    Yes,in this directory there is a java.exe,but the problem is when I run install.bat this script put space among JASPER and  \     and that directory doesn't exists :"E:\CA\JASPER \jre\bin\java.exe"   
    Is there any other way to install The capm_reports-xxxx.zip on cabi Server?

    thank you



  • 4.  RE: The capm_reports-xxxx.zip package on 20.2 capc

    Posted Oct 29, 2020 11:17 AM
    Hello Michael,

    Is there other way to recovery my groups from CAPC on jasper reports?



  • 5.  RE: The capm_reports-xxxx.zip package on 20.2 capc

    Broadcom Employee
    Posted Oct 29, 2020 11:48 AM
    This might be better off worked in a new support case.

    Not sure why the installer would be adding a space to a path making it the wrong the path. Don't see any past instances of the same issue in old cases or KB articles.

    ------------------------------
    Technical Support Engineer IV
    Broadcom
    ------------------------------