Subject
Error: 'Core could not find a file' when running vulscan on clients.
Description When running a vulscan on the client side, you see an error message "Warning: Core could not find a file" relating to one of the following files:
- Defaults.txt
- agentbehavior_N.xml (where N is a number)
- av_behavior_N.xml
- cv_behavior_N.xml
Cause
- The file being looked for has become corrupt.
- The file being looked for is not in the Agentbehaviors directory.
Resolution
Check the vulscan.log file to see which file is missing. Then take the following steps:
**Defaults.txt**
This file should be located in the Agentbehaviors directory on the core. If it is not, you may find a backup under the Landesk\ManagementSuite\LDLogon\Spyware folder. If you do, COPY this file to the LDLOGON\AgentBehaviors directory. If the file does not exist anywhere, you will need to email the customer a copy from your core server or get one from another core in their environment.
**AgentBehavior**
This file is used for determining the behavior of the client when scanning and repairing. Check the AgentBehaviors folder to see if a filename exists that is matching.
-If the file does exist, try running 'vulscan /reset' on the client and run a new scan to see is this fixes the local file.
-If the file does NOT exist, try recreating the behavior file. To do this, go into Agent Configuration, select 'Security and Patch Scan' and at the bottom of the right hand pane, look to see what "Scan and Repair Settings" name is specified. Then click 'Configure'. From the 'Configure Scan and Repair Settings' window that comes up, select the behavior that was listed in the Agent Configuration and click 'edit'. Once in the behavior, change ANY value and click 'Ok' , and then 'Use Selected'. This will take you back to the Agent Configuration. Click 'Save' to resave the agent. If this works, we should now have an Agent Behavior that matches the one we are looking for. Run the vulscan again and see if it works.
-The new agentbehavior still fails, create a NEW set of scan and repair settings and push a Scheduled Update or a Settings Change task.
**AV or CV behavior**
These files should not keep the LANDesk agent from running a vulscan. If these files cause the error, simply create a new AV Behavior and a new Custom Variable Behavior, and push these out via a Change Settings Task. This is done via the Schedule a Task--> Change Settings button in Security and Patch Manager.
*Note on AV Behavior: If you no longer have LANDesk Antivirus installed and the avbehavior_X.xml is missing and the client is looking for the avbehavior vulscan will return an error in the log and the GUI but will complete sucessfully. To fix this error, go into the database, open the AgentBehavior table and delete the row that has the avbehavior listed. Then resave your agent this will recreate the default behavior in the directory and then patch manager will complete with no errors.
NOTE: In some cases, the entire AgentBehaviors folder may be gone. If this is the case, recreate the folder and try the above steps for Agent Behavior replacement. If that does not recreate the files, you will need to create new Scan and Repair Settings and push them via a Change Settings task.