FlexNet Code Insight Knowledge Base

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Knowledge Base Categories
Symptoms: - Scans fail with the error message 'Unable to Communicate with codeaware 400' - Scan failure happens with codeaware not able to scan Diagnosis: Though Scanner and Core are on the same server, the scanner was not able to communicate with the core and  Solution: 1. Please rename the scanner to use localhost or as the server 2. Please proceed with the following Generate keystore jks file (from tomcat location), keytool -genkey -keyalg RSA -alias codeinsightLH -keystore codeinsightLH.jks -storepass changeit -validity 360 -keysize 2048 -ext san=dns:localhost Export the generated certificate in codeinsightLH.jks to file __ codeinsightLH.cer, keytool -export -alias codeinsightLH -storepass changeit -file codeinsightLH.cer -keystore codeinsightLH.jks Trust the certificate and perform an import keytool -import -file codeinsightLH.cer -alias codeinsightLH -keystore ../jre/lib/security/cacerts -storepass changeit Start Tomcat and now user will be able to create scanner with' localhost' as host.
View full article
Environment The issue occurs in this environment: The operating system on which FlexNet Code Insight and its associated database is installed is CentOS 7 or RHEL 7. The Code Insight database is MySQL version 8. Symptoms When you use the FlexNet Code Insight installer to install the latest version of Code Insight on a Linux machine, an error related to the database connection can occur even though the database log-in credentials provided during installation are valid. To view the error description in a Code Insight installer log, open the attached file. Diagnosis MySQL 8 uses a set of time zone values that are different from values used by CentOS and RHEL. For example, MySQL8 uses time zone values that include “PDT”, “CST”, and so forth, whereas Centos and RHEL use named time zones such as “America/Chicago” and “Europe/Lisbon”. Solution The MySQL time-zone tables must be populated with named time-zone values from the publicly available “zoneinfo” (or “tzinfo”) database used by computers and operating systems internationally. Once these tables are populated, you can configure MySQL with the named time zone appropriate for your location. To populate MySQL time-zone tables and reconfigure the MySQL time zone, do the following: From the machine on which the MySQL resides, run the following command to populate the MySQL time zone tables: mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p To reconfigure the MySQL time zone, open the my.cnf file in your MySQL installation, and edit the "default_time_zone" line to reflect the named time zone appropriate for your location: default_time_zone="America/Los_Angeles"  This example uses the America/Los_Angeles named time zone. To help you locate the appropriate time zone for your MySQL installation, click here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones Save my.cnf. Restart MySQL to apply the changes.  
View full article
Perforce not Installed
View full article