Symptoms: On an SVM On-Premises with the latest ActiveX Plugin, a message prompts with the following: An error occurred while loading the Software Vulnerability Manager Plugin. Error loading plugin: Unable to verify checksum signature : 12037 Diagnosis: Attempts to remove and reinstall to no avail. Same issue occurs on another system. Solution: Check and verify the SSL PKI Certificate on your SVM On-Premises.  More details can be followed here: Swap SVM On-Prem SSL certificates [Centos VA] or [RHEL] - Community (flexera.com) ... View more

Symptoms: The SVM Plugin fails to install and prompts with "Error opening file for writing: C:\Program Files\FIexera Software\Corporate Software Inspector Plugin\csiplugin.ocx"     Software Vulnerability Manager Plugin Setup Error opening file for writing: C:\Program Files\FIexera Software\Corporate Software Inspector Plugin\csiplugin.ocx   Click Abort to stop the installation, Retry to try again, or Ignore to skip this file. Diagnosis: This repeats if aborted and rerunning setup, or even with retry from the prompt. If ignored, then the Plugin does not operate correctly. Solution: Abort setup. Open Task Manager. Remain in "Process" tab. Search for "COM Surrogate" End all "COM Surrogate" tasks.  Any Access Denied is fine, they can remain running. Restart setup. ... View more

Question: Advisory emails sent according to watchlist do not add exact CVE numbers and details, how can this be included in the email? Answer: Login to your SVR software account at https://app.flexerasoftware.com. Navigate to "User Profile" from left Menu. Scroll down, select "Edit"  Two settings in Personal Settings require to be to set to the following: Advisory type email (default normal item): Receive normal emails Attach advisory PDF (default no): Yes Save the settings with save. You may need to create a custom Watchlist if emails are still being sent without PDF. Please contact Flexera Support if you require assistance. Advisory Emails will now be sent with an attached PDF including the CVE details.  ... View more

Symptoms: A message prompts in Step 3 of Create Update Package on certain packages that it is unable to display more than 3000 paths. Diagnosis: The message prompts only a specific package.  The message may also prompt on SVM Patch Publisher. Solution: This is a notice to inform the user that the WebUI is unable to display more than 3000 paths. The package creation should be able to continue. The wizard may select the default location path when you create an update package. If no path is selected: 1. Select a path of the default location. 2. Create your own path. 3. Select "Select All" paths from column check box. ... View more

Symptoms: The SPS right click feature is unresponsive.  Diagnosis: The ActiveX plugin is installed and up-to-date.  A message in the browser developers tools shows "Unable to get property 'GUID' of undefined or null reference." Solution: 1. Check and, if necessary, Install RSAT Tools or from Windows 10 October 2018 install RSAT: Windows Server Update Tools from the Optional features. 2. If the above is installed, check the SSL Certificate on your on-premises server. Update if necessary. 3. Contact Flexera Support if the above two steps are checked and accurate. ... View more

English Some manually maintained Asset types may have custom fields. For example, mobile device may have "IMEI 2" as some mobile devices have dual SIM capability. When Importing with the excel solution, you may find that the custom field is missing. Solution: 1. Add the column and relevant data of the customer field to your Excel.  2. From "Bulk Import" either Browse... or Drag and Drop the Excel file. 3. At the "Assignment of data" area, you will see "Object type". From here, select the specific "Asset type" the Excel is based on. For example, mobile device. 4. Once you have selected the correct "Object type", remember to select the "Import mode" task.  The custom fields will appear and the import validator will confirm the columns being update/imported.   Deutsch Manche Assets, welche manuell gepflegt werden, haben ggf. speziell angepasste Felder. So kann z.B. ein Mobiles Gerät das Feld "IMEI 2" haben, da in dem Gerät zwei SIM Karten verwendet werden können. Wenn man nun Daten mit Excel importiert, dann kann es vorkommen, dass dieses Feld nicht dargestellt wird. Lösung 1. Fügen Sie die Spalte samt Feld mit Daten in Excel hinzu 2. Von der 'Mehrfachimport' Option nun auf 'Durchsuchen...' oder die Excel Datei mit Drag und Drop hinzufügen 3. Im Bereich 'Zuordnen der Daten' sieht man nun 'Objekt Typ'. Hier nun den spezifischen Asset Typ eintragen, wie auch in der Excel Tabelle z.B. Mobiles Gerät 4. Denken Sie daran, nachdem der korrekte Objekt Typ ausgewählt wurde, den Import Modus auf 'Import' zu setzen. Im nächsten Schritt können dann die zu importierenden Spalten und Felder bestätigt werden ... View more

English The Spider CheckPage gives an overview of the connections to the database. Any Connection issue with a Spider Application may be visible. A history of Spider Versions is also visible.   The Spider CheckPage is not accessible from the Menu. The URL needs to be entered manually.    ..Spider/Info/checkpage.aspx   Permissions to the following Forms may need to be set to the account:   Spider Core -> CheckPage   Deutsch Bei der Spider Checkpage bekommt man eine Übersicht über die Verbindungen zur Datenbank. Verbindungsprobleme in eine Spider Anwendung werden hier dargestellt. Man sieht auch den Verlauf von Spider Versionen. Die Checkpage kann nicht von einem Menüpunkt aus angesteuert werden, man muss das URL manuell eintragen. ..Spider/Info/checkpage.aspx Berechtigungen für die folgenden Formulare müssen ggf. gesetzt werden Spider Core -> CheckPage     ... View more

English The new Coverage Rules function enables the user to add individual suite definitions which are then considered in the compliance calculation. This allows the user to create his own rules that are not included in the product catalogue. Solution: In Spider, go to "System" Select Roles Select applicable "Asset" Role From the ribbon go to "Forms" Select "+ Assign application forms" Select the following forms: CoverageRule CoverageRuleCreate CoverageRuleEdit Save. Log off from Spider and log back in for changes to take effect.   Deutsch Die neue Funktion Abdeckungsregeln ermöglicht dem Benutzer das Erstellen von Suite-Definitionen, die dann in der Compliance Berechnung berücksichtigt werden. Hierdurch kann der Benutzer eigene Regeln erstellen, welche im Produktkatalog nicht enthalten sind. Lösung: In Spider, auf 'System' Dann auf Rollen Asset Rolle auswählen Oben im Ribbon auf 'Formulare' Dann auf  '+ Assign application forms' Folgende Formulare auswählen: CoverageRule CoverageRuleCreate CoverageRuleEdit Save. Log off from Spider and log back in for changes to take effect. ... View more

Symptoms: Remnants of Inactive and obsolete Spider Data Collectors visible in Spider Web UI Info and Settings. Diagnosis: Findings of Data Collectors with "Inactive" or "Last contact more than four hours ago". Despite the Server being obsolete, either shut down or deleted from the infrastructure, the servers remain within the list in Spider. Solution: Spider does not remove any inactive Servers regardless of actual Server status. However, the removal does require manual handling.    Data in SpiderDataReceiverRegister.csv & SpiderDataReceiverConnection.csv located in  C:\Program Files\Spider\Recognition\DataReceiver are responsible for the data shown in the database and WebUI (Spider/Apps/Asset/SwrImport/SWRImportBoard.aspx?).      There are 2 options: Alter the Status and keep the obsolete Data Collector as a reference. Remove the Data Collector completely. Option 1 Go to "C:\Program Files\Spider\Recognition\DataReceiver" Open "SpiderDataReceiverConnection.csv" Remove the obsolete Server Save and close. Open "SpiderDataReceiverRegister.csv" Remove the obsolete Server Save and close. Optional: If the Server Status is Active, you can change the status from the SQL Database. Go to SpiderRecognition Database Go to Tables > import.Connection Edit the Table and Alter "Status" to INACTIVE Option 2 Go to "C:\Program Files\Spider\Recognition\DataReceiver" Open "SpiderDataReceiverConnection.csv" Remove the obsolete Server Save and close. Open "SpiderDataReceiverRegister.csv" Remove the obsolete Server Save and close. Go to Spider Recognition Database Go to Tables > import.Connection Edit the Table and delete the obsolete Server row. DE to follow ... View more