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