Jump to content
We've recently updated our Privacy Statement, available here ×

Jivan Phadtare

Jaspersoft Staff
  • Posts

    49
  • Joined

  • Last visited

Community Answers

  1. Jivan Phadtare's post in Running into error after upgrading from JasperReports Server 8.0.4 to 9.0.0. "REPORT_CONTEXT" does not exist. was marked as the answer   
    Hello,
    The "Parameter REPORT_CONTEXT does not exist" message in the log is coming from the JRS server monitoring process and should not cause any issue for report execution. This annoying but harmless message has been reported internal  and will get fixed later in upcoming release (no ETA available for the actual date yet).
     
  2. Jivan Phadtare's post in What is the problem? was marked as the answer   
    Hello,
    Could you please check if you have java installed on machine where you are installing the software.
    also, please make sure java version is compatible as per platform support guide document. Check with java 11 as well.
     
  3. Jivan Phadtare's post in Why I am getting an error when doing SQL query from the database for the sequence nexval or currval records via iReports? (SOLVED) was marked as the answer   
    Looking at the error message it is showing caused by "Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist"
    Kindly make sure in your oracle databae "DIL_LIVE_ORDERS_VIEW" this view is present.
    It's possible that the table or view you are referencing does not exist in the database. Verify that the table or view exists by checking the database 
    Apart from this also check on below possibilities :
    Incorrect Table or View Name
    Missing Schema or Owner Name
    Insufficient Privileges : Check if the user executing the query has the necessary privileges to access the table or view. Ensure that the user has been granted the appropriate 
     
  4. Jivan Phadtare's post in name.package.class.Scriptlet resolves to package when report with Scriptlet on Jasper server was marked as the answer   
    Hello,
    while importing the package n jrxml report, we could see it was mentioned as wrong like cp, kindly correct and republish report.
    <import value="cp,.av.jasper.GetExpressionFromStringScriptlet"/>

    Also, you can try editing WEB-INF/applicationContext-adhoc.xml and add the following property somewhere inside the adhocEngineService bean:
    <property name="reportUnitClassLoadingEnabled" value="true"/>
    Reference : https://community.tibco.com/s/article/jasperserver-unable-load-scriplet-jars-repository
    Hope this will find you useful.
  5. Jivan Phadtare's post in using multiple databases was marked as the answer   
    Hello,
    found similar query posted earlier with regards to this where it was mentioned using DATASETS and putting them into table components or subreports it's possible.
    Please refer below URL for reference.
    https://community.jaspersoft.com/questions/1082151/can-we-use-multiple-database-data-source-single-jasper-report#:~:text=Yes%2C%20using%20DATASETS%20and%20putting%20them%20into%20table%20components%20or%20subreports.
    https://community.jaspersoft.com/wiki/how-deploy-reports-tibco-jasperreports-server-subreports-use-different-data-sources
    Hopefully this will help you !!
  6. Jivan Phadtare's post in Hello, when running the report, it gives an error. There was an error on the server. Try again or contact site administrators. was marked as the answer   
    It looks like your report query validation is getting failed.
    If you don't want to validate sql then you can set below property to 'false' in file "security-config.properties", restart JRS and then try to run the report.
    security.validation.sql.on=false
    if you would like to validate sql then Please check file "security-config.properties" for below property.
    security.validation.sql.on=true
    If this property set as true then make sure in "security.properties" file below property is also uncommented.
    # sqlQueryExecutor=Alpha,ValidSQL,500000,true,SQL_Query_Executor_context
    Also, plesae uncomment below property from "validation.properties" file.
    # Validator.ValidSQL=(?is)^\s*(select|call)\b((?!\binto\b)[^;])*;?\s*$
    If your report query using "with" keyword then you can use property below as you mentioend in description.
    Validator.ValidSQL=(?is)^\s*(select|with|declare)\s+[^;]+;?\s*$

     
×
×
  • Create New...