Summary Reports in Software Vulnerability Manager are not getting generated and the status always stays "In Progress".  Cause Almost always the problems is caused by a problem with the reporting cronjob.  SVM On-Prem Edition users will be able to troubleshoot this issue at their backend server. SVM Cloud customers should contact Flexera support and report the issue as soon as noticing it.  Steps To Reproduce 1. Navigate to Reporting -> Report Configuration -> Generate New Report 2. Select the required parameters including Dashboard Profile and save the report. Resolution Contact Flexera Support for more information on best next steps.  Workaround Reports might also get stuck "In Progress" due to duplicate portlets within the Dashboard. Removing the duplicates creates the report successfully. ... View more

Summary This article provides configuration parameters used in /etc/csia/csia.conf file of the Software Vulnerability Manager Red Hat Linux Agent.  Discussion This article is applicable to Agents installed on Red Hat Enterprise Linux and CentOS systems. It might be applicable to other look-a-like Linux distros, but it will not be officially supported on those.  CSIAUser = "<MasterToken>"; CSIAToken = "<AgentToken>"; CSIAHost = "<ServerFQDN";          CSIAPort = 443; GUID = "<UniqueAgentGUID>"; GroupName = "<CustomSiteName>"; Logging = 2; LogFile = "/var/log/logfile.log"; ConfigSent = 1; Additional Information You may have to restart the csia service to see the effect of the configuration taking effect.  ... View more

Summary You might get the following error while running/connecting to the SVM Plugin for the SCCM Console.  Cause The above error occurs when either the website URL is not added to Trusted Sites and / or the following components are missing from the server i.e. .net framework 4.5 and visual c++ x86 and x64.  This problem can also be the direct effect of Certificate Revocation validation blocking at a local proxy server or a firewall, or simply WinHttp packets are not routed through the correct network channel to successfully access the Internet (where this issue applies to SVM Cloud SCCM Plugins).  Resolution Please check that https://*.secunia.com is added to Internet Explorer Options > Security > Trusted Sites.  Also, check whether dependencies like .Net and Visual c++ both x86 and x64 are installed on the host.  Try to ping in CMD the URLs that are required for CRL validation and SVM access to report scan data General online requirements Additional requirements from the SVM move to AWS CRL Issues You might be experiencing the same issues listed in our WinHttp 12175 KB article. The commands listed in this KB can be used to troubleshoot the plugin with regards to netsh winhttp proxy configuration of the local system and diagnosing if the packets are sent through the right proxy, or they are sent Direct.  ... View more

Summary This document provides information regarding the difference between two scheduled tasks: 1. Merge ManageSoft policies and 2. Reconcile ManageSoft directory tables with AD Synopsis There are two scheduled tasks in FNMP 9.2 related to policy merging. 1. Merge ManageSoft policies Program\Script: C:\Program Files (x86)\ManageSoft\Common\ndcrproc.exe Tasks = -e "C:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -l "E:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -o CREATE_NO_WINDOW=True -- -R -a 2. Reconcile ManageSoft directory tables with AD Program\Script: C:\Program Files (x86)\ManageSoft\Common\ndcrproc.exe Tasks = -e "C:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -o CREATE_NO_WINDOW=True -- -ran Discussion The differences between the above two policies are as follows: 1. Merge ManageSoft policies Program\Script: C:\Program Files (x86)\ManageSoft\Common\ndcrproc.exe Tasks = -e "C:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -l "E:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -o CREATE_NO_WINDOW=True -- -R -a This task generates merged policy across all Active Directory domains that are configured for policy merging. This configuration is done on the inventory server, using the item Setup for multiple domains from the context menu available on the root node in the console tree. The resultant data is merged into the inventory database for checking installation status. 2. Reconcile ManageSoft directory tables with AD Program\Script: C:\Program Files (x86)\ManageSoft\Common\ndcrproc.exe Tasks = -e "C:\Program Files (x86)\ManageSoft\Reporter\polmerge.exe" -o CREATE_NO_WINDOW=True -- -ran This task reconciles your Active Directory without generating merged policies, then modifies your inventory database to reflect any renamed, moved, or deleted computers, users, or organizational units. ... View more

Summary "Invalid Login Response" error after installing Cognos Analytics Symptoms This document provides steps to resolve "Invalid Login Response" error after installation of Cognos Analytics while accessing any reports via the URL. Cause This error is shown as a result of using "Easy Install" method and not choosing the "Optional Gateway" during installation. Resolution To resolve this issue, uninstall Cognos first, then re-install it. When following the instructions for installing Analytics in the "Installing FNMS 2017 R3 on Premises.pdf" document on page #58, the required Cognos Gateway is not installed. On the "Install type" dialog, instead of the "Easy install" radio button, please select "Custom install". On the subsequent dialog "Choose components", both the checkbox for "Application services" as well as the checkbox for "Optional gateway" MUST be selected. Additional Information In addition to the above, please also check the CognosConfigProperties.xml file : --- <!-- Content store database settings --> <!-- ContentStore database location. When using TCP, the format for this value is hostname:port. Alternatively, the hostname\instancename format (without a port) can be used. --> <property name="ContentStoreDatabaseLocation" value=" abcdefgh "/> <!--Required--> <!-- ContentStore database name. This database must already exist. --> <property name="ContentStoreDatabaseName" value="ContentStore"/> <!--Required--> -- The ContentStoreDatabaseLocation value should be "hostname:port" or "hostname\instancename" whereas the configured value only shows the hostname " abcdefgh ". ... View more

Summary You might get an error while running CSI console on Windows Server 2008 and below versions. Symptoms Cause The error occurs because the operating systems Windows Server 2008 and below versions only support SHA-1 encryption algorithm and our recent binaries support SHA-256 algorithm. Resolution Corporate Software Inspector is a security product, and follows the latest security standards. Windows Server 2008 does not meet those standards, and is already End-of-Support according to Microsoft. Customer will need to upgrade their OS to Windows Server 2008 R2 and above. Additional Information ... View more