Ask the Community
Groups
Patch Scan error "FAILED in processing THEN step 7, Get Variable, with error File Open Failed" - Connect IT Community | Kaseya
<main> <article class="userContent"> <h3 data-id="n-a"> </h3> <h3 data-id="n-a-1"> </h3> <h3 data-id="problem">Problem</h3> <ul><li>Patch Status shows no patch data (only dashes) even after patch scan</li> </ul><p>In order to determine whether this article may be applicable to the conditions you are experiencing, view the Agent > Agent Logs > Agent Procedure Log for the specific endpoint.</p> <p>Note: ensure you are reviewing the Agent Procedure log, not the Agent log:</p> <p><img src="/attachments/token/AMe9R6BipbtmBR5yV4aV3UcOF/?name=4137.AgentProcLog.png-550x0.png" alt="4137.AgentProcLog.png-550x0.png" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p>Locate the time of a recent Patch Scan. If you see a log entry indicating, <strong>“FAILED in processing THEN step 7, Get Variable, with error File Open Failed, Get content from file ....</strong>” this article may help to resolve the issue. If you cannot find a recent patch scan, go to Patch Management > Scan Machine, select the endpoint, and click “Run Now” to force a new Patch Scan. Once the patch scan completes, review the logs. If you do not find this error in the Agent Procedure log, this article does not apply.</p> <p>Example screenshot from Agent Procedure log:</p> <p><img src="/attachments/token/vtSKeDqb0qEyglsZUP3IX7nby/?name=2015-03-04+16_10_23-Professional+Edition.png" alt="2015-03-04_16_10_23-Professional_Edition.png" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <h3 data-id="cause">Cause</h3> <p>Most of the times, this error is due to not having valid path <a title="Working Directory" rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fhelp.kaseya.com%2FWebHelp%2FEN%2FVSA%2FR8%2Findex.asp%23368.htm"><strong>Working Directory</strong></a> path. The Working Directory is a path to a directory on the managed machine used by the agent to store working files.Depending on the task at hand, the agent uses several additional files. The server transfers these files to a working directory used by the agent on the managed machine. If Working Directory path is invalid you will see above error in Agent Procedure Logs</p> <h3 data-id="solution">Solution</h3> <p>Please go to <strong>Agent > Manage Agents> Working Directory </strong>and ensure "working path" is valid and it exists on the managed endpoint.<br></p> <p>This is link to Working Directory documentation which may be off use to you :- <a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fhelp.kaseya.com%2FWebHelp%2FEN%2FVSA%2FR8%2Findex.asp%23368.htm">http://help.kaseya.com/WebHelp/EN/VSA/R8/index.asp#368.htm</a></p> <p> </p> <h3 data-id="applies-to">Applies to</h3> <p>Kaseya VSA - v6.3 and later</p> <p>Patch Management</p> </article> </main>