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

vchiem

Members
 View Profile  See their activity

  • Posts

    443

  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Everything posted by vchiem

  1. vchiem
    Issue:The domain is created using a virtual data source with MySQL as the database. Is it possible to get the row numbers in the domain designer using derived tables and/or calculated fields ? Solution:Virtual Data Source is based on the TEIID engine. You can explore the various TEIID functions that can be used in SQL from this page : https://docs.jboss.org/teiid/7.6.0.Final/reference/en-US/html_single/#d0e4503 There is the ROW_NUMBER() function which assigns a number to each row in a partition starting at 1. This function can be used when creating a derived table.
  2. vchiem
    Issue:Any new jobs created using TIBCO Jaspersoft® ETL Studio are not appearing in TAC. When the user tries to create a new task using Job Conductor in TAC, the Job is not listed in the drop-down menu. Solution:The project may be out of synch with the TAC temp folder. Clear the TAC cache by following the steps below: Stop TAC ServiceNavigate to <tac-installation-folder>apache-tomcat and clear all contents of the temp and work foldersClear the web browser cacheRestart TAC ServiceWhen the restart of TAC is performed, the newly checked-out objects from SVN will be placed in the apache-tomcattemp directory. Note: This issue can also be observed if the TAC service is started by a user who is not the owner of the apache-tomcattemp directory. See article below for more information. Related Articles:https://community.talend.com/t5/Design-and-Development/A-Job-that-can-be-viewed-from-Studio-is-not-available-from/ta-p/36864
  3. vchiem
    Issue:After carrying out a search for reports in the repository, there is a "Deprecated reports" type that appears in the left Filters pane. What reports can be expected to appear here ? Solution:The "Deprecated reports" will list the Ad Hoc reports that failed the migration or conversion from an older TIBCO JasperReports® Server version pre-4.7 to version 4.7+ Ad Hoc views. This is because version 4.7 introduced Ad Hoc views and there was a need to do the conversion of all Ad Hoc reports to Ad Hoc views during upgrade. Any Ad Hoc reports that did not convert/migrate properly to Ad Hoc views will be listed in "Deprecated reports". An example scenario where this can happen is when the Ad Hoc report has been customized and failed the conversion.
  4. vchiem
    Security Vulnerabilities are published under TIBCO Security Advisories here : https://www.tibco.com/services/support/advisories?_ga=2.246362756.1838132487.1593397409-1433776992.1552885607 If the CVE is not addressed by the page then it becomes an unknown until it is published. SV issues are of sensitive nature and any other information should not be provided on this platform.
  5. vchiem
    You drag a filter from the left pane (under Filters section) onto the dashboard canvas and once this is done, the "Filter Group" dashlet is automatically created with the filter inside. You can then add more filters onto the same dashlet.
  6. vchiem
    The error is very generic but if the test button failed the connection then its best to check the Hive log to see full stack trace.Check the port 10000 is open. This may give you ideas: https://stackoverflow.com/questions/22431984/unable-to-establish-a-jdbc-connection-to-hive-from-eclipse
  7. vchiem
    You can use the browser F12 console to trace the location of the jsp file but I think it could be in : WEB-INF/decorators/decoratorCommonComponents.jsp since there is this line: "< li id="main_logOut" class="last"><a id="main_logOut_link" href="#"><spring:message code="menu.logout"/></a></li>" So an example you can try is : <li id="main_logOut" class="last"><a id="main_logOut_link" href="http://(MYSERVER):PORT/webapp/logout"><spring:message code="menu.logout"/></a></li>
  8. vchiem
    A lot depends on what error the user is receiving. Publishing a report from Studio to the server is one way of getting the report onto that server but it requires the data source behind the report to be valid as well. Alternatively, there is the Export and Import facility that allows you to export the resource with its dependencies and import into the target environment. For a report this would be right click on the report and click on Export along with its dependencies. The Import can be done under the Server Settings tab. Migrating of resources 'generally' can be done for environments which has the same JRS version or from an older version to a higher version (there are exceptions) but not from a higher version to an older version.
  9. vchiem
    I hope you understand that the path is a repository path and not a path on the actual server host. So if you login to the JR Server application via a browser under 'superuser' account' you can browse to the folder under the Repository section.
  10. vchiem
    It should be a matter of getting the right REST request format. There are examples in the REST API guide. The guide is downloadable from https://community.jaspersoft.com/documentation?version=59011 CHAPTER 13 REST API REFERENCE - THE reports SERVICE
  11. vchiem
    Issue:We have exported reports and its dependencies from TIBCO JasperReports® Server 6.x and imported the reports into TIBCO JasperReports® Server 7.5. After trying to edit and run the imported report as a user (eg. jasperadmin) under the new organization, the following error appears to the user: "There was an error on the server. Try again or contact site administrators. (ERROR UID: 8c6d4f7a-7dbb-4644-9db6-e07911accf55)" The ../WEB-INF/log/jasperserver.log file captured the following error: 2020-04-27T16:19:30,538 ERROR ErrorPageHandlerAction,https-jsse-nio-8443-exec-37:118 - Error UID 8c6d4f7a-7dbb-4644-9db6-e07911accf55com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: You may not access resources which do not belong to your organization....Caused by: com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: Path /organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME> is not visible in organization context [/code]Note: The issue does not occur for the superuser account. Solution: The error comes from a resource referenced from the report where there is an absolute path: /organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME> There were changes implemented in the TIBCO JasperReports® Server 7.x release where an absolute path referenced in report resource is no longer acceptable. The solution is to update the affected resources to reference relative paths which is relative to the organization user. In the TIBCO JasperReports® Server 7.5 Release Notes, the following statement was documented: JS-34346: This release changes resource visibility constraints in multi-tenant deployments (that is, those that include more than one organization). The change disables certain cases of improper resource referencing, such as providing an absolute repository path (starting with the root organization) for a resource referenced in a report. If you have a reference to an image, a subreport, or other resource that has an absolute path (or uses a $P{} parameter that later resolves to an absolute path), the server returns an error. Please update such references to use path that are visible to users in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations. ref: 01861769
  12. vchiem
    Your export command exports "--everything" and not just reports. There are a lot of changes between 5.2 and 7.5 to export everything and expect it to be successful. The recommendation is to follow the Upgrade guide and do a two phase upgrade and let the upgrade scripts take care of it. 1. Upgrade to the latest version of 6.4.x. 2. Upgrade from 6.4.x to version 7.5.
  13. vchiem
    This is not a current feature so the answer is no.
  14. vchiem
    Installation should really be on a certified version of Mac OSX. The supported platforms guide that comes with each release will list out the versions. Catalina would be 10.15 which is not certified even on the current 7.5 version. However, there is a community article on how to get the install to run on Catalina. https://community.jaspersoft.com/wiki/how-run-bundled-installer-tibco-jasperreports-server-macos-1015-catalina
  15. vchiem
    Issue:In TIBCO JasperReports® Server 7.5, the following exception is generated upon starting up the server : log4j:ERROR Unexpected char [e] at position 17 in conversion patterrn.[/code]How to resolve this error ? Solution:On the TIBCO JasperReports® Server, edit the file: ..webappsjasperserver-proWEB-INFapplicationContext-diagnostic.xml Locate the following bean: <bean class="org.apache.log4j.PatternLayout">[/code]and modify: <value>%-5p %c[1] - %m%ex%n</value>[/code]to delete the 'e' so it looks like this: <value>%-5p %c[1] - %m%x%n</value>[/code]Restart the TIBCO JasperReports® Server. Related Articles:JS-56613: Non critical exceptions in JRS startup
  16. vchiem
    In JR Server 7.5, the options are in the "Select Visualization Type" button next to the drop down box. The Table and other types are displayed as icons.
  17. vchiem
    TIBCO Jaspersoft Studio is a report development tool that allows you to build reports with table and crosstab components.
  18. vchiem
    According to the supported platforms, Oracle/Sun Java JDK / JRE (64-bit) versions 1.7, 1.8 are certified.
  19. vchiem
    Issue:While executing the below js-export.bat command from the <js-install>/buildomatic folder, the following error was encountered: Command: js-export.bat --everything --output-zip jrs-7.1-export.zip[/code]Error: Exception in thread "main" java.lang.NoClassDefFoundError: com/jaspersoft/jasperserver/export/ExportCommand[/code] Solution: The cause of this error was due to js-export.bat picking up an old unsupported version of java installed on the machine. A typical scenario would be having Java JDK 1.4.2 installed on the machine and its bin directory added to the front of the system PATH environment variable. The js-export.bat which runs the following command: java -classpath "%EXP_CLASSPATH%" %JAVA_OPTS% com.jaspersoft.jasperserver.export.ExportCommand %JS_CMD_NAME% %CMD_LINE_ARGS%[/code]would execute java under the incorrect JDK 1.4.2 bin directory. This is despite %JAVA_HOME% set to point to the correct version of Java (eg. C:Program FilesJavajdk1.8.0_161) The solution is to remove the old version of Java from the system PATH environment variable, then open up a new command shell and first run "java -version" from buildomatic folder to ensure the right version of java is detected. Then run the js-export.bat command again. Note: This error can also occur with running js-export.sh as well as js-import.bat [.sh] scripts. ref: 01852956
  20. vchiem
    Issue:As per the command: pg_dump --username=postgres jasperserver > js-db-dump.sql we received an error message: pg_dump: [archiver (db)] connection to database "jasperserver" failed: could not connect to server: No such file or directoryIs the server running locally and acceptingconnections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?[/code] To get rid of this error, we tried the following command for backup: pg_dump jasperserver -U jasperdb -h localhost > js-db-dump-13FEB2020.sql but received: connection to database "jasperserver" failed: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?[/code]How to overcome these issues to successfully generate the dump file ? Solution:The error represents a connection problem to the postgres database. So it is essential to firstly know whether the postgres is running and on what port number (default port is 5432). Once you know this information, you can use this to force the connection with extra parameters passed with the pg_dump command : -h host -p port -U username -W You can refer to the following page for reference: https://www.postgresql.org/docs/9.3/app-pgdump.html If it is still an issue and the error that you are getting remains exactly the same then probably there is an incorrect path to socket. Backup tried to connect to /var/run/postgresql/.s.PGSQL.5432 but it does not exist. Hence you can check this article: https://stackoverflow.com/questions/31645550/why-psql-cant-connect-to-server to check for the location of the socket file and verify the configuration files, pg_hba.conf and postgresql.conf are correctly set. There are mentions to check for unix_socket_directories parameter setting and set it to /tmp. It is recommended to check that this parameter is in place as well: listen_addresses = '*'
  21. vchiem
    Issue:In a report, we are trying to use the column filter on a table column field to filter on values matching the condition but it does not return the expected rows. For example: In the report there is a table with a field containing value 1.629214. We set the JIVE 'Column filters' on this column to the following: Condition: "Show only rows where" Equals 1.629214 Result: There are no rows returned We noticed that when we select the 'Column filters' again, the actual value was automatically truncated to 1.629 instead of keeping the entered value of 1.629214. How do we resolve this so that we get the results returned for the exact filter value entered ? Solution:There is a configurable pattern in: <jasperserver-webapp>/WEB-INF/bundles/jasperreports_messages[_lang[_country]].properties under the key: net.sf.jasperreports.components.number.pattern that defaults to: ###,###.### This can be adjusted to contain more digits after the decimal place : ###,###.###### The pattern is used to adjust both numbers on server and the ones coming from the UI when comparing them for filtering purposes. ref: 01844211
  22. vchiem
    Issue:After installing TIBCO JasperReports® Server 7.5 with Weblogic Server 12.2.1, there was no jasperserver.log file generated under the directory: <weblogicdomain>/servers/<myserver>/tmp/_WL_user/jasperserver-pro/jjb30p/war/WEB-INF/logs Upon starting up the Weblogic Server, the following exception was generated in the console: <Mar 2, 2020 5:59:29,837 PM PST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "jasperserver-pro".weblogic.application.ModuleException: org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger com_jaspersoft_jasperserver_api_security at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:233) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:228) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45) Truncated. see log file for complete stacktraceCaused By: org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger com_jaspersoft_jasperserver_api_security at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:256) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:178) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:56) at org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:35) at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:458) Truncated. see log file for complete stacktrace[/code] This problem did not occur in the previous version TIBCO JasperReports® Server 7.2. Solution:In TIBCO JasperReports® Server 7.5, log4j was updated to log4j2. In the WEB-INF/log4j2.properties file, the cause of the problem is this entry: # Security Logginglogger.com_jaspersoft_jasperserver_api_security.level=INFO[/code]It is missing a name for this logger. 1> Modify the "# Security Logging" entry and replace it with : # Security Logginglogger.com_jaspersoft_jasperserver_api_security.name=com.jaspersoft.jasperserver.api.securitylogger.com_jaspersoft_jasperserver_api_security.level=INFO[/code]2> Save the WEB-INF/log4j2.properties file and restart the Weblogic Server: STOP: <wl-domain>/bin/stopWeblogic.sh START: <wl-domain>/bin/startWeblogic.sh Note: If the above still does not generate the jasperserver.log, then try setting the full path to the file log4j2.properties for the parameter : -Dlog4j.configurationFile= with the JAVA_OPTIONS in the script ../jasper_domain/bin/setDomainEnv.sh and restart the server. Example: -Dlog4j.configurationFile=<weblogicdomain>/servers/<myserver>/tmp/_WL_user/jasperserver-pro/jjb30p/war/WEB-INF/log4j2.properties ref: 01848116
  23. vchiem
    The error represents a connection problem to the postgres database. So it is essential to firstly know whether the postgres is running and on what port number (default port is 5432). Once you know this information, you can use this to force the connection with extra parameters passed with the pg_dump command : -h host -p port -U username -W You can use this postgres command line reference as a guide: https://www.postgresql.org/docs/9.3/app-pgdump.html If it is still an issue and the error that you are getting remains EXACTLY the same then probably there is an incorrect path to socket. Backup tried to connect to /var/run/postgresql/.s.PGSQL.5432 but it does not exist. You can check this article: https://stackoverflow.com/questions/31645550/why-psql-cant-connect-to-server to check for the location of the socket file and verify the config files pg_hba.conf and postgresql.conf accordingly. There are a few comments that mentions to check for unix_socket_directories parameter setting. I also recommend to check the for this setting as well: listen_addresses = '*'
  24. vchiem
    According to: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-user-guide/v62/representing-filters-xml it states: Filters defined in the Domain Designer are limited to conditions on one column or comparisons of two columns, with more complex filters created by the conjunction (logical AND) of several conditions. Other filter expressions are not supported. You can upload a design file with more complex filters, but they are overwritten or cause errors if you open the design in the Domain Designer.
  25. vchiem
    It is best to contact Fishbowl support.
×
×
  • Create New...

© 2024 Cloud Software Group,
Inc. All rights reserved.

Products

Explore