CA Service Management

 View Only

Top 10 Knowledgebase Articles: CA Service Desk Manager Jaspersoft Reporting - September 2018                

Oct 09, 2018 04:49 PM

Here are the 8 most used Knowledge Base articles about Jaspersoft Reporting for CA Service Desk Manager in September 2018. When you view one of these articles, please take a moment to let us know that you like it with a comment and a quick thumbs-up rating in the article. You can also reply to this document to let us know of other articles you would like to see about Jaspersoft Reporting.

 

Thanks for taking a few moments of your busy day to look through these articles!

 

"" "" "" "" ""

Article (with link)Summary
KB000005332: Error: "An internal error occurred while trying to authenticate the user. org.springframework.security.authentication.InternalAuthenticationServiceException" after configuring JasperSoft with LDAP authenticationThe following error appears in jasperserver.log file after configuring JasperSoft with LDAP authentication: ERROR EncryptionAuthenticationProcessingFilter,http-bio-8080-exec-3:218 - An internal error occurred while trying to authenticate the user. org.springframework.security.authentication.InternalAuthenticationServiceException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ] at org.springframework.security.ldap.authentication.LdapAuthenticationProvider.doAuthentication(LdapAuthenticationProvider.java:191) ... Caused by: org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1 ]
KB000010048: How to configure Jasper Studio for editing existing reports and creating new reports for CA Service Desk Manager data on Jasper Server.You can use Jasper Studio Professional to edit existing reports that are delivered with the CA Service Management content for CABI-Jasper, or to design new reports to view your CA Service Desk Manager data.  To edit or copy existing reports, and then publish them to Jasper Server for use, it will require you to configure Jasper Studio to connect to your Jasper Server instance where the CA Service Management content was imported.  To design/create new reports, it will also require you to create a Data Adapter in Jasper Studio to connect to the CA Service Desk Manager object layer.  This document will explain the steps to configure Jasper Studio properly, enabling you to edit existing reports, create new reports and publish reports to Jasper Server.
KB000010750: Jasper Studio License ExpiredAfter installing Jasper Studio Professional, if the license file is not properly applied, a "License Expired" message might be displayed by the "License Manager".
KB000007037: Jaspersoft login page error HTTP Status 404Checking at jasperserver.log files, there are several messages as below (in this case Oracle database is referred, but it might happen for other RDBMS). ERROR JDBCExceptionReporter,localhost-startStop-2:101 - Cannot create PoolableConnectionFactory ([TibcoSoftwareInc][Oracle JDBC Driver][Oracle]ORA-28000: the account is lockedChecking at jasperserver.log files, there are several messages as below (in this case Oracle database is referred, but it might happen for other RDBMS). ERROR JDBCExceptionReporter,localhost-startStop-2:101 - Cannot create PoolableConnectionFactory ([TibcoSoftwareInc][Oracle JDBC Driver][Oracle]ORA-28000: the account is locked
KB000007352: When using JasperSoft Studio, receive a JAVA Heap Space ErrorWhen using JasperSoft Studio, receive a JAVA Heap Space Error similar to the following: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Unknown Source) at java.io.ByteArrayOutputStream.write(Unknown Source) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at sun.nio.cs.StreamEncoder.write(Unknown Source) at sun.nio.cs.StreamEncoder.write(Unknown Source) at java.io.OutputStreamWriter.write(Unknown Source) at java.io.Writer.write(Unknown Source)
KB000106148: "The Report is Empty" when trying to publish a report from Jaspersoft Studio to JasperReports ServerCustomer creates a new jasper report having Input Controls. When he clicks on preview in Jaspersoft Studio, the report content comes up correctly. However, when he publishes it in JasperReports Server, he gets: ""The Report is Empty"".
KB000107035: Error upgrading JasperReports Server from 6.2.0 to 6.3.0Error message when upgrading JasperReports Server from 6.2.0 to 6.3.0: install.bat -r sample_sql.properties ""Found JAVA_HOME environment variable"" ""Found both java.exe and javaw.exe in JAVA_HOME's bin directory"" ""Validation of JAVA_HOME is done"" ""Validation of argument count is done"" ""ANT_ARGS are -Dproperties.file=sample_sql.properties -Dlog.file=install.log"" ""Starting build.xml with ANT_ARGS -Dproperties.file=sample_sql.properties -Dlog.file=install.log"" Buildfile: c:\jasperserver63\ca_install\build.xml BUILD FAILED c:\jasperserver63\ca_install\build.xml:2: The following error occurred while executing this line: c:\jasperserver63\ca_install\create_master.xml:2: java.lang.UnsupportedClassVersionError: com/ca/bicoe/cajasperserver/install/preinstall/utils/Decryption Task : Unsupported major.minor version 52.0
KB000112961: CABI JasperReports Server 6.3 installation stuck at "Installing...Starting Jasper Server installation ( 13% )" when DBMS is Oracle clusteredWe are trying to install the CABI JasperReport 6.3 in our pre-production environment, but the installation stalls at 13%. We have a Oracle clustered environment, like this: Database node #1 (DB_Node1) has SID represented by ""SID1"" and the hostname of the server represented by ""hostname1"" Database node #2 (DB_Node2) has SID represented by ""SID2"" and the hostname of the server represented by ""hostname2"" The servicename is represented by ""SN"". A cluster_hostname is not set. During the installation we must specify a hostname and sid (or servicename). We don't have a unique cluster_hostname defined, and so we tried to use ""hostname1"" with ""SN"".   The installer validated the connection with the db and let us to continue but got stuck at 13%.

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.