Synopsis: When migrating the ISUS database to another server, certain files need to be modified in the Publisher server to point to this new database location.   Solution: When moving database servers, then the following files will need updating with the new connection strings, username and password. These files are located in <FNC home>\FNC1500\tomcat\conf\Catalina\<serverName> axis.xml publisher.xml ROOT.xml The "connection string" refers to something which looks similar to the following: "jdbc:jtds:sqlserver://<serverName>:1433;DatabaseName=<databaseName>"  *Note: There is also a connection string in <FNC home>/FNC1500/reports/runreport.bat and <FNC home>/FNC1500/logloader/logloader.bat which will need to be changed.    ... View more

Symptoms: The Flexnet Connect reports no longer produce an "Interactive graph" option.  Diagnosis: This is down to Adobe Flash Player being EOL from 31-Dec-2020, and is no longer supported in web browsers. Solution: The only option is generating data using XML (on Firefox ONLY). Other browsers do not seem to generate the XML data.    This can be done by selecting "Data (XML)" as the Output Type, as shown below...   ... View more

Summary:  When trying to download an update the error, "General data transfer failure. Couldn't resolve host name" is displayed. Symptoms: When downloading an update using the FlexNet Connect Client the pop-up dialog with the error below is displayed:   Cause: This will occur if the download URL in the Publisher Portal for the update is formatted incorrectly, as shown in the snapshot below:   Resolution: In the Publisher Portal change the download URL to use the correct format (i.e. using forward slash '/', not backslash '\'), as shown below: https://www.testServer.com/joemc/Update/Test/Test1_V1.1.zip ... View more

Symptoms: When performing a capability request or response in FlexNet Operations and the following error is thrown in the UI: "An application error has occurred". If this occurs then search the flexnet.log file for the following error: ERROR (lfs) An application error has occurred com.flexnet.lfs.webservice.LFSFaultResponse_Exception: LFSError:UNKNOWN_ERROR Diagnosis: The issue occurs when the history logging level is set to "Error". This has been fixed in the 2018 R2 release. Solution:  Upgrade to FNO  2018 R2. If this is not possible, then use the following workaround: 1. Go to System Configurations -> Embedded Devices -> History Logging 2. Change logging level from "Error" to "Information". 3. Save.        ... View more

Description When  logging into Flexnet Connect On-Premise you may see the error in the attachment.  There is an problem with the version of Java that FNC installer is using, as this has outdated protocol support and seems to be causing the issue.   Resolution What you'll need to do is the following: 1. Download and install the latest Java SDK* from Oracle based on the FNC architecture you've installed, i.e. x86 or x64.  2. On your FNC machine, stop the 'FNC Connect 15:00' service. 3. In your FNC installation directory, rename '_jvm' folder. 4. Create a new '_jvm' folder. 5. Open up the Java SDK and copy the contents from 'C:\Program Files\Java\jdk1.8.0_231' folder into the '_jvm' folder. 6. Start the 'FNC Connect 15:00' service again. 7. Now update the instance ID in the FNC admin portal under the 'License Rights' page. You should now be prompted with the following: Available Features: Enterprise Update Management** Instrumentation Management** *Note: The latest Java SDK that was tested with at the time this KB was created is 'Java SE Development Kit 8u231'. **Features available are dependent on what you purchased. If you don't see any features, this just means you've purchased no additional FNC features.    ... View more