Spider Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Summary This article describes the recommended and supported operating systems for Spider. Spider 6.4.x Recommended Windows Server 2019 Standard or  Windows Server 2016 Standard  Supported Windows 2019 Windows 2016 Windows 2012 / 2012 R2 Spider 6.3.x Recommended Windows Server 2012 R2 Standard or  Windows 2016 Server Standard  Supported Windows 2016 Windows 2012 / 2012 R2 Windows 2008 SP2 / Windows 2008 R2  
View full article
You can download the full Data Collector guide here (in English) or in here (in German)  Table of Contents 1 General  1.1 Typographical conventions 1.2 Help 1.2.1 Support 1.2.2 Documentation 1.2.3 Training information 1.3 Abbreviations   2 What's new    3 Compliance with DSGVO/GDPR 9 3.1 Connectors with personal data 3.1.1 API based connectors 3.1.2 Database based connectors 3.2 Inventory Components 3.2.1 Windows 3.3 File locations containing personal data 3.4 Secure data transport   4 Install and configuration of the Data Collector  4.1 System Requirements 4.1.1 Software 4.1.2 Hardware 4.2 Installation 4.3 Configuration 4.3.1 Data Collector 4.3.2 SFTP Server 4.4 Resetting last upload date 4.5 Add Publisher to Trusted Publishers 4.6 Uninstall 4.7 Troubleshooting Connection /Authentication Issues 4.8 Data Collector Service Account   5 Configuring execution of connectors 5.1 SQL based connectors 5.1.1 Discovery Systems Data Connector (DSDC.exe) 5.1.2 Suppress export of MAC and IP information (DSDC.exe.config) 5.1.3 System Center - Configuration Manager (SCCM) 5.1.4 Frontrange Discovery 5.1.5 Heat Discovery 5.1.6 Landesk 5.1.7 Lansweeper 5.1.8 Microsoft Assessment and Planning Toolkit (MAP) 5.1.9 Generic Connector 5.1.10 Matrix42 (beta) 5.1.11 Empirum Workplace Management (beta) 5.1.12 Baramundi (beta) 5.1.13 Snow (beta)  5.1.14 Altiris 7 (beta) 5.1.15 Overview of discovered Items   5.2 API based connectors 5.2.1 Introduction 5.2.2 Active Directory 5.2.3 VMWare vCenter / ESX Server 5.2.4 Microsoft Azure (Microsoft Online) 5.2.5 Adobe Online 5.2.6 Microsoft Application Virtualization (App-V) Connector 5.2.7 Columbus Datacenter Inventory 5.2.8 LDAP (beta) 5.2.9 Hyper-V (beta) 5.2.10 Hyper-V via Virtual Machine Manager (beta) 5.2.11 Microsoft Exchange Connector (beta) 5.2.12 XEN Server (beta) 5.2.13 Microsoft Intune (Beta)   6 Inventory using Columbus Tools  6.1 Windows 6.1.1 System Requirements for Columbus Inventory 6.1.2 DSGVO / GDPR Settings 6.1.3 Columbus Inventory Agent 6.1.4 Columbus Inventory Agent MSI 6.1.5 Columbus Inventory Scanner 6.1.6 Columbus Inventory Scanner Resetting Last Scan Date 6.1.7 Discovered Hardware Items 6.1.8 Feature Comparison 6.1.9 Advanced Inventory with Scanner Add-on DLLs 6.1.10 Additional Inventory Items from Registry 6.1.11 SSL Secured Transmission   6.2 Linux, Mac & UNIX 6.2.1 Columbus Inventory Scanner Location 6.2.2 Columbus Inventory Scanner Configuration 6.2.3 Columbus Inventory Scanner Installation 6.2.4 Columbus Inventory Scanner Execution   7 FAQ 7.1 TCP/IP Socket based communication (OTB) 7.2 Log file locations 7.3 Data Flow   8 Appendix 8.1 Powershell Module - bwgTools 8.2 Generic Connector Stored Procedures 8.2.1 dbo.swrGetWorkList 8.2.2 dbo.swrGetHardwareScan 8.2.3 dbo.swrGetFileScan 8.2.4 dbo.swrGetSoftwareScan 8.2.5 dbo.swrGetDeviceRelationship 8.2.6 dbo.swrGetADUserObject 8.2.7 dbo.swrGetADGroupObject 8.2.8 dbo.swrGetADGroupMember 8.2.9 dbo.swrGetSwidScan 8.3 Inventory using MAP Toolkit 8.3.1 Database 8.3.2 Installation 8.3.3 Configuration 8.3.4 Collecting inventory data  
View full article
Download the Spider 6.4 Technical Reference Manual here. (in German) 1 General 1.1 Typographical conventions 1.2 Help 1.2.1 Support 1.2.2 Documentation 1.2.3 Training 2 Introduction 2.1 Chronological order for new installations 3 GDPR requirements in Spider 3.1 Personal data 3.2 Personal data fields related to selected Spider data objects 3.3 Principles relating to processing of personal data (Article 5 GDPR) 3.4 Lawfulness of processing (Article 6 GDPR) 3.5 Data protection by design and by default (Article 25 GDPR) 3.6 Conditions for consent (Article 7 GDPR) 3.7 Information obligation (Article 13 and 14 GPR) 3.8 Records of processing activities (Article 30 GDPR) 4 Spider 4.1 System requirements 4.1.1 Application server 4.1.2 Database - Microsoft SQL Server 4.1.3 Indexing - OneSearch 4.1.4 Hardware requirements 4.1.5 Clients / Browser 4.1.6 Implementation system 4.1.7 Permission requirements 4.1.8 Hardware-Scaling 4.2 Installation 4.2.1 Software to be installed in advance 4.2.2 Start of the installation 4.2.3 License agreement 4.2.4 New installation or update 4.2.5 License file 4.2.6 Installation directory 4.2.7 Start menu item 4.2.8 Database server 4.2.9 Index proxy server 4.2.10 Web Logins 4.2.11 Database names 4.2.12 Language and format settings 4.2.13 SMTP settings 4.2.14 Administration account 4.2.15 IIS configuration 4.2.16 Transfer directory 4.2.17 Installation 4.2.18 Activate the license 4.3 Advanced configuration 4.3.1 Operation with domain account 4.3.2 Subsequent setup of the index proxy 4.3.3 Conversion to SSL operation 4.3.4 HTTP(S) Redirect 4.3.5 Setup of Active Directory login 4.3.6 Info page - support.config 4.3.7 Available languages - culture.config 4.3.8 Settings in the Config table 4.3.9 Display of advanced error messages 4.3.10 Encryption of the configuration 4.3.11 Error handling system 4.4 Update 4.4.1 Start of the update 4.4.2 Update 4.4.3 Selection of the Instance 4.4.4 Database server 4.4.5 Index proxy server 4.4.6 Select updates 4.4.7 Installation 5. Spider Web API 5.1 Technical information 5.2 Authetnication 5.3 Admin section 5.4 Entity section 5.5 Search section 5.6 Report section 5.7 Meta section 5.8 Version information 5.9 Swagger 5.10 Web API documentation 5.11 Spider Web API Explorer 6. Software Services (Catalogs and Recognition) 6.1 System requirements 6.2 Installation 6.3 Advanced configuration 6.4 Update 7 Data center module (nova ratio appliance) 7.1 Sizing of the virtual machine 7.2 Launching of the appliance 7.3 Setting up the data center module 8 Log files 8.1 Brainware.log 8.2 Smart-Inspect log files (*.sil)  
View full article
Summary Spider LCM 5 installations cannot be used together with a SQL Server 2014. If you plan to migrate your SQL server(s) you have to be aware of this fact. Cause Spider LCM 5 databases are written for SQL Server 2005 and therefore require compatibility level of SQL Server 2005 (Level 90). This compatibility level is automatically set through the Spider setup. With another compatibility level the Spider LCM databases are not released. From SQL Server 2014 onwards the required compatibility level 90 is not available anymore. https://msdn.microsoft.com/en-us/library/ms144262.aspx Resolution Update your Spider LCM installation to the most recent version.   Products LCM5, Spider 5  
View full article
Summary This article explains how to reactivate an asset that has been set to archive. Synopsis If you set an asset to a status which sets the asset to archive, you won't probably be able to reactivate the asset because an archived asset is not editable anymore in Spider. Discussion Use the Asset Import Launcher to update the status of the appropriate asset creating an xml file with the following content (sample):   <?xml version="1.0" encoding="iso-8859-1"?> <ResultBatch> <Asset> <AssetNo>VM000023</AssetNo> <AssetStatusName>Active</AssetStatusName> </Asset> </ResultBatch>   Replace the content of the AssetNo and the AssetStatusName with your values      
View full article
Summary Nach einer Migration von Spider LCM Version 5 auf Version 6 erhalten Sie die Fehlermeldung: Das Formular 'PRODUCTVERSIONSOFTWAREDELETE' kann nicht geöffnet werden oder ist nicht lizenziert. Symptoms Nach einer Migration von Spider LCM Version 5 auf Version 6 erhalten Sie die Fehlermeldung: Das Formular 'PRODUCTVERSIONSOFTWAREDELETE' kann nicht geöffnet werden oder ist nicht lizenziert.     Additional Information Bei der Migration wurde im Formular ProductVersionSoftwareEdit im Feld Detach der ControlTyp nicht angepasst und somit zeigte er auf ein nicht existentes Formular.   Lösung Der ControlTyp muss von ButtonRedirector auf ButtonDelete geändert und die URL geleert werden. Schlüsselwörter PRODUCTVERSIONSOFTWAREDELETE, ButtonRedirector, ButtonDelete Produkte LCM6  
View full article
Summary This article explains what to do if the data collector reports Visual C++ 2010 Redistributable Package (x64) as missing. Symptoms The Spider Data Collector reports Visual C++ 2010 Redistributable Package (x64) as missing. Cause For the Adobe Online connector to work, it is necessary that "Visual C++ 2010 Redistributable Package (x64)" is installed. Resolution Follow these steps: Download Visual C++ 2010 Redistributable Package (x64) for your OS Install Visual C++ 2010 Redistributable Package (x64)   Products Spider Data Collector (SDC)
View full article
Summary This article provides a resolution if the XObjectHistory table in the Spider Core database gets filled with data. Symptoms The XObjectHistory table in the Spider Core database gets filled with lots of data     Cause The EmployeeParameterMapping for any key has been filled with FullName. This is not allowed since FullName is a calculated field and the Core service will evaluate it as different and create a history entry.     Resolution Remove the Value FullName from the EmployeeParameterMapping in Spider Admin Tool:   Open Spider Admin Tool Open Spider Core > Config Navigate to SoftwareRecognition> EmployeeParameterMapping Remove the FullName value from the list   Additional Information Spider 6.2.15115.162 
View full article
Summary While document uploads you get the following error: Maximum request length exceeded. Symptoms While document uploads you get the following Spider error: Maximum request length exceeded.   Cause The default size is set to 4MB (4096). This normally is sufficient for web applications. But if big attachments need to be uploaded this needs to be changed.     Resolution Change the configuration key maxRequestLength to the reqired value (in KB) Example: <system.web> <httpRuntime maxRequestLength="11000"/>    
View full article
Summary In case of the PowerShell execution policy being set to "AllSigned", it is necessary to add the publisher of the signing certificate to the trusted publishers store of the local machine. Symptoms Setup detects PowerShell execution policy being detected to "AllSigned" Cause In case of the PowerShell execution policy being set to "AllSigned", it is necessary to add the publisher of the signing certificate to the trusted publishers store of the local machine. The Setup will ask you to add the Publisher to the Trusted Publishers store before continuing, this will only place it in the store for the current user, for the certificate to be valid across all accounts of the local machine please follow the instructions below. Resolution Warning: It is important that the certificate is imported to the Trusted Publishers of the local machine, not only the user! If it is only imported into the user store it will not be available if the service is running under another account other than the user the Data Collector was installed with. Navigate to the file VMware.VimAutomation.Sdk.ps1 file (default: C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Modules\VMware.VimAutomation.Sdk\), right klick and choose Properties Choose Tab Digital Signatures Click Details Click View Certificate Click Install Certificate Choose Local Machine and click Next Choose Place all certificates in the following store and click Browse... Choose Trusted Publishers and click OK Click Next Click Finish Close all dialogs by clicking OK until you are back to the following screen Highlight the Symantec signature and press Details Click View Certificate Click Install Certificate Choose Local Machine and click Next Choose Place all certificates in the following store and click Browse... Choose Trusted Publishers and click OK Click Next Click Finish Done   Additional Information The command "Get-ExecutionPolicy -List" executed in a PowerShell window, will tell you which policies are activated. Products  Spider Data Collector (SDC)  
View full article
Summary After an update of Spider LCM to version 6.1 you get an error when trying to do an export from Columbus to Spider Asset. Symptoms After an update of Spider LCM to version 6.1 you will get the following error when trying to do an export from Columbus to Spider Asset:   Initialize connection process to : http://<SpiderServer>/ISpiderColumbus/ISpiderColumbus.asmx Attach to SOAP interface... Get remote system info... Remote interface (ISpiderColumbus) version is: 6.1.1.0 Databasename: Spider_Core, Servername: <SpiderSQLInstance>, Active True Databasename: Spider_Asset, Servername: <SpiderSQLInstance>, Active True Retrieving Session ID... Server was unable to process request. ---> The authentication of user failed. Retrieving Session ID... Server was unable to process request. ---> The authentication of user failed. Finished   Furthermore you will notice that the user iSpiderColumbus in Spider LCM does not exist anymore   Cause Since Spider LCM 6.1 the iSpiderColumbus user is not needed as a user anymore, therefore it gets deleted by the setup. Resolution Configure the user and password that should be used in the following settings file of the iSpiderColumbus interface: <SpiderInstallDirectory>\CoreServer_00\iSpiderColumbus\_Settings\appSettings.config <?xml version="1.0" encoding="utf-8" ?> <appSettings> <add key="User" value="iSpiderColumbus" /> <add key="Password" value="bra!nware" /> <add key="SnapshotIsolationLevelEnabled" value="true" /> <add key="SpiderAssetApplicationGuid" value="38F96E97-C314-44B8-B137-C966D35A3BA0" /> </appSettings>   Additional Information For security reasons please DO change the default password Products C7, LCM6, ISC6  
View full article
Summary Spider Data Collector Installer complains about Recognition having another Data collector installed. Cause Recogntion utilizes it's own Data Collector to transfer the unknown products to the Recognition Service. Only one copy of the Data Collector can be installed on any given system. Resolution Choose another machine to install the Data Collector on. Additional Information In case you have a non productive license, or you choose not to install the Recognition Upload during the installation of Recognition, you can install a Data Collector for collecting inventory information on the same machine as Recognition was installed on. Products Spider Data Collector (SDC)  
View full article
Summary The Setup will ask you to add the Publisher to the Trusted Publishers store before continuing, this will only place it in the store for the current user, for the certificate to be valid across all accounts of the local machine please follow the instructions in this article. Symptoms Spider setup detects PowerShell execution policy being detected to "AllSigned" Cause In case of the PowerShell execution policy being set to "AllSigned", it is necessary to add the publisher of the signing certificate to the trusted publishers store of the local machine. The Setup will ask you to add the Publisher to the Trusted Publishers store before continuing, this will only place it in the store for the current user, for the certificate to be valid across all accounts of the local machine please follow the instructions below. Resolution Warning: It is important that the certificate is imported to the Trusted Publishers of the local machine, not only the user! If it is only imported into the user store it will not be available if the service is running under another account other than the user the Data Collector was installed with. Navigate to the file GetExecutionPolicy.ps1 file (placed in the same directory the installer was started from), right klick and choose Properties Choose Tab Digital Signatures Click Details Click View Certificate Click Install Certificate Choose Local Machine and click Next Choose Place all certificates in the following store and click Browse... Choose Trusted Publishers and click OK Click Next Click Finish Done     Additional Information The command "Get-ExecutionPolicy -List" executed in a PowerShell window, will tell you which policies are activated. Products Spider Data Collector (SDC)  
View full article
Summary The Spider setup warns about the vCenter Invalid Certificate Action not being set to ignore. Cause The vCenter PowerShell Command Line Interface checks the validity of the server certificate upon connecting to the vCenter/ESX server. If the InvalidCerticateAction ist not set to ignore and the certificate is not valid, the connector will not connect. The setting can be checked by issuing: Get-PowerCLIConfiguration The InvalidCertificateAction has to be set for "AllUsers" so the service is also covered by the setting. Resolution In case the action is NOT set to ignore you can issue the following command (start PowerShell as Administrator) to change the setting. Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Scope AllUsers   Additional Information vSphere PowerCLI Reference - Set-PowerCLIConfiguration Products SDC
View full article
Summary The Spider setup reports the Recognition version to be below 1.1805. Cause When updating to Spider 6.4 a minimum version of Recognition is required. Resolution Update Recognition to at least 1.1805 prior to the 6.4 update. Products Spider
View full article
Summary Depending on the version of Spider, installation is possible on the following operating system versions. Spider 6.4.x Application Server Recommended Version Windows Server 2016 Standard or Windows 2019 Server Standard  Supported Versions Windows 2019 Windows 2016 Windows 2012 / 2012 R2 Spider Data Collector (SDC) The Spider Data Collector needs to be installed on  a separate machine. Recommended Version Windows Server 2016 Standard or Windows 2019 Server Standard  Supported Versions Windows 2019 Windows 2016 Windows 2012 / 2012 R2 Windows 2008 SP2* / Windows 2008 R2** * For Windows 2008 SP 2 the patch KB980368 (https://support.microsoft.com/en-us/kb/980368) is required ** Versions 2008 and 2008 R2 will not be supported by Spider 6.4 or later   Spider 6.3.x Application Server Recommended Version Windows Server 2012 R2 Standard or Windows 2016 Server Standard  Supported Versions Windows 2016 Windows 2012 / 2012 R2 Windows 2008 SP2* / Windows 2008 R2** * For Windows 2008 SP 2 the patch KB980368 (https://support.microsoft.com/en-us/kb/980368) is required ** Versions 2008 and 2008 R2 will not be supported by Spider 6.4 or later   Products Spider 6.4.x  
View full article
Summary The setup queries your database to find the amount of tenants present. Depending on the number you will be offered to execute the calculation after the setup has finished installing. Symptoms The Spider setup queries your database to find the amount of tenants present.   Resolution Depending on the number, you will be offered to execute the calculation after the setup has finished installing. Additional Information    
View full article
Summary You have been installing Spider LCM 6.x or Columbus 7.x and your License Console tells you to activate your license or you get an e-mail from the Columbus server that you should activate your license. Discussion To activate your license please follow these steps:   If you got an e-mail from your Columbus server you can jump to #5 Open the License Console (Start > All Programs > Columbus | Spider > License Console ) Select one of the items which is not activated yet Open Main Menu > Save Activation Request for Selected License ID Save the file with your company name to a location you can remember Send this file to licensing@brainwaregroup.com You then will receive an activation file (xml). Save it to a known location you can access within the License Console. Open the License Console again Open Main Menu > Import Activation Information File Select the activation file you have got After confirmation your license has been activated Congratulations :-)  
View full article
Summary This article explains how to test if you can get a connection to the remote service such as SDC Receiver, Columbus OTB, Mail server, etc. Synopsis You want to test if you can get a connection to the remote service such as SDC Receiver, Columbus OTB, Mail server, etc... Discussion To test the connection run the following PowerShell command: Test -NetConnection -Computername <ServerName> -Port <Port> -InformationLevel Detailed You then will get a reply like the following: ComputerName : collector.bwg.testing RemoteAddress : 172.16.0.65 RemotePort : 1685 NameResolutionResults : 172.16.0.65 MatchingIPsecRules : NetworkIsolationContext : Internet IsAdmin : False InterfaceAlias : Ethernet0 SourceAddress : 192.168.0.75 NetRoute (NextHop) : 192.168.0.254 TcpTestSucceeded : True or if the test failed: WARNUNG: TCP connect to collector.bwg.testing:1686 failed ComputerName : collector.bwg.testing RemoteAddress : 172.16.0.65 RemotePort : 1685 NameResolutionResults : 172.16.0.65 MatchingIPsecRules : NetworkIsolationContext : Internet IsAdmin : False InterfaceAlias : Ethernet0 SourceAddress : 192.168.0.75 NetRoute (NextHop) : 192.168.0.254 PingSucceeded : True PingReplyDetails (RTT) : 0 ms TcpTestSucceeded : False     Additional Information This command is available on Windows 8.1/ Windows Server 12 R2 and higher Products C7, LCM6, OM4  
View full article
Summary This article explains how to configure Operations Manager SSL Keys to overcome a secure connection failure when accessing Spider Operations Manager. Synopsis You are experiencing a secure connection failure when accessing Spider Operations Manager (Incident/KB/Change). Discussion To overcome this problem on server side please follow these steps: Login to the GlassFish Administration Console http://<YourOMServerName>:8048 with username admin and the password you have been choosing upon OM installation (default: brainwaregroup) Navigate in tree to: Configuration > HTTP Service > HTTP Listeners > om_ssl Choose tab SSL Add all four Available Common Ciphersuites to the selected ones Save this configuration by clicking on the Save button Restart Operations Manager services Products OM4
View full article