cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Scan data not available

Scan data not available

Symptoms:

When the Software Vulnerability Agent is installed and running as a service, you may see a white list added in the scan agent log that does not appear when running agent scan manually using the command line.

 

[12/03 11:39:23.899] Append in whiteList path = D:\TEST

[12/03 11:39:23.023] : Initializing Filesystem Inspector

[12/03 11:39:24.052] Added "C:\" to search list

[12/03 11:39:24.073] Added "D:\" to search list

[12/03 11:39:24.099] Skipping "C:\" from the scan, since it is not allowed.

Diagnosis:

If there is no white list configured on the server, you need to check two local locations and make sure there are no rules.json file present.

When scan is running as a service it uses rules.json from below location

C:\Windows\System32\config\systemprofile\AppData\Local\Vulnerable Software Discovery Tool

Executing Software Vulnerability Manager Agent scan manually will use below location for rules.json file

%LocalAppdata%\Vulnerable Software Discovery Tool

Solution:

Deleting rules.json should correct issue with data not showing or scan results differ between scan executed manually in command line and automatically by the Flexera Corporate Software Inspector Agent service.

Was this article helpful? Yes No
No ratings
Comments

Hello all,

It appears that the location %LocalAppdata%\Vulnerable Software Discovery Tool is no longer valid for where the rules.json file is stored during an execution of the client when it is not installed. I have no such directory in local app data for my logged in user after executing a scan from CMD. Where does the file download to now for Windows and Mac scans from a non installed agent? Thank you.

Version history
Last update:
‎Dec 17, 2020 05:56 AM
Updated by:
Contributors