Known issues
Review the issues with workarounds and limitations for this release.
Workarounds
The following issues in this release have workarounds.
ID | Description |
---|---|
495000 | DCC shows old product names on the Resource Group Configuration page First occurrence: 7.0 Problem: When you upgrade the Data Collection Component to version 7.0, on the Resource Group Configuration page, you might see old product names or versions such as Rational DOORS Next Generation. Workaround: Complete these steps:
|
465842 | Draft reports cannot be edited First occurrence: 6.0.5 Problem: If you build and edit a report and do not save it, the report is auto-saved in a draft state with a generated title and timestamp, but you cannot edit the draft later. Workaround: Complete these steps:
|
447935 | Licensing errors might occur if you upgrade the Java environment or upgrade applications to
version 6.0.5 or later First occurrence: 6.0.5 Problem: If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 or later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys. Workaround: The licenses in the IBM License Key Center (formerly known as IBM Rational License Key Center) were updated to use a different signature algorithm.After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:
|
420229 | Links in an exported Word document cause authentication errors First occurrence: 6.0.4 Problem: If you export a Report Builder report that contains hyperlinks to Microsoft Word, clicking a hyperlink in the exported Word document might fail and cause the following error after you complete the login for CLM (now known as ELM):Invalid path to authentication servlet. Workaround: Complete the steps in the following article to add a registry key entry for Word, which enables you to successfully log in to CLM (now known as ELM) after clicking the hyperlink in the Word document:Error message when clicking hyperlink in Office: "Cannot locate the Internet server or proxy server" |
513820 | Logging information not available for changes made to reports, schedules, report managers,
and data sources First occurrence: 6.0.6.1 Problem: Report Builder does not log the following tasks:
Workaround: Add the following content to the
Jazz_Install_Dir/server/conf/rs/log4j.properties file if you upgrade JRS by replacing the
rs.war files:log4j.additivity.R=false# Logger to analyze creation/deletion/updation of
report/schedule/endpoints/report managerslog4j.logger.AUDIT=DEBUG,
AUDITlog4j.additivity.AUDIT=falselog4j.appender.AUDIT=org.apache.log4j.RollingFileAppenderlog4j.appender.AUDIT.File=logs/rs_audit.loglog4j.appender.AUDIT.MaxFileSize=10MBlog4j.appender.AUDIT.MaxBackupIndex=10log4j.appender.AUDIT.layout=org.apache.log4j.PatternLayoutlog4j.appender.AUDIT.layout.ConversionPattern=%d{ISO8601}
- %m%n
Note: Report Builder does not log tasks that involve draft reports.
|
521219 | Restoring LQE databases from backup gives an error for text indexes that do not exist First occurrence: 7.0.2 Problem: While restoring an LQE database from a backup, the following error occurs:"server\conf\lqe\datasets\history\historyText' does not exist"It is because shapes\textIndex and history\textIndex subfolders are not available anymore in the LQE backup folder.Note: The creation of the default\textIndex subfolder is optional. In the LQE Advanced Properties page, if the Create Index for Full Text Search option is selected, then the default\textIndex subfolder is created. Workaround: To resolve the error, contact IBM Support for a test fix for LQE. Installation of the test fix will resolve the error. |
493553 | Workarounds: RM types are displayed as URLs in (LQE) Requirements trend report First occurrence7.0 Problem: If you are writing a requirements trend report for a LQE data source, the RM types might display as URLs instead of type names. The problem is that there is a configuration missing which prevents the job that updates the type names from running. This problem might be seen in previous versions of this product. Workaround: Complete these steps:
|
511252 |
The clmhelp.war file and the updateSite.zip for release 7.0.2 are unavailable for download First occurrence: 7.0.1 Problem: The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download due to technical issues. Workaround: You can install the KCCI.zip file on your intranet server to view the help locally. Click here to download the ELM702_KCCI_contents.zip file.For information about installing the KCCI.zip file, see the Installing help on an intranet server topic. |
522104 | The links_am data source is added in a failed state to LDX when the ELM 7.0.1 environment is
renamed First occurrence: 7.0.2 Problem: After you rename the Engineering Lifecycle Management 7.0.1 environment, the links_am data source is added to LDX in a failed state. Therefore, the links_am data source cannot be reindexed. Workaround: To enable reindexing of the links_am sources, complete the following steps:
|
496705 | Timeout limits must be increased before metamodel refresh First occurrence: 6.0.6.1 Problem: For servers with many project areas, the Report Builder metamodel fails to refresh, because the “sparqlShapeTypes” type queries time out. Workaround: Increase the timeout limits to provide enough time for all the metadata to refresh.Increase all the following timeout values to 1200 seconds. If the problem still persists, set them all to a higher value, such as 1800 seconds.
Note: Add + 1 to the query timeout value to set the socket timeout value. For instance, if the
query timeout value is set to 1200, the socket timeout value must be 1201.
|