/build/static/layout/Breadcrumb_cap_w.png

Many patch schedules are timing out with error 8151, with the log error "The system cannot find the file specified"

I'm new to KACE patching.  We have been experiencing issues with the schedule for quite some time, and I have been tasked with determining the cause and finding a solution.  So, after examing many of the agent logs on affected systems, I am seeing a common problem.  During the patch run, a file is attempted to be downloaded from the local server at each location.  This file is supposed to reside in the repl2\patches\patch_catalog\windows location.  The file has a name that is a string of numbers and letters, with no discernable file extension.  This file should then be copied to a location on the host that is being updated, and given a new name (based on what I'm seeing in the log).  However, the file that it is looking for does not exist.  This is happening over and over on many hosts.  

In KACE, the error I see is "agent timeout."  In the log, the error I see is "8151."  Again, as someone who is new to KACE patching, despite having extensively scoured KACE and the internet for a reason, I'm turning up empty handed.  Thought I would ask the pros here at ITNinja.  I sincerely appreciate your time and any effort offered to assist.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Nico_K 3 months ago
Red Belt
0

8151 means: failure downloading a requested file.
So we need to go a bit deeper into your setting:
Do you have any security software which can block downloads? (like Antivirus) and did not setup them correctly? See here: https://support.quest.com/kb/4272244/
Which systems are affected? A remote location or the main location? If remote: is there a replication share? If yes: how is it configured?
In addition for remote shares: are they replicating correctly? Do they have a fallback set or not?

In addition: look into the KACE logs (C:\programdata\quest\kace\user) and determine which file is affected.

I suggest to call support for analysis since it is more effective to check this remote.


Comments:
  • There is nothing that would be blocking the download. I have checked and the file simply is not there. It was not created.

    This is at one of our remote locations and yes there is a replication share. It is full of many other recently created files. It is configured to allow files to be created there.

    Here is a snippet from the log:

    [2022-12-19.20:35:25][KacePatch:KacePatchFileDownloade] KacePatchFileDownloader::Download: Failed to get patch file from server, try #3
    [2022-12-19.20:35:25][KacePatch:KacePatchFileDownloade] KacePatchFileDownloader::Download: Failed to download file: 'C:\ProgramData\Quest\KACE\kpd\6ecf58a0-cb6a-485c-aa25-57e3083b919d.kpf' Error: '8151'
    [2022-12-19.20:35:25][KacePatch:KacePatchDetectFile::D] KacePatchDetectFile::DownloadAndProcess: Download primary and failover url failed: 8151
    [2022-12-19.20:35:25][KacePatch:KacePatchModule::Detec] KacePatchModule::Detect: Failed to process detect file 6ecf58a0-cb6a-485c-aa25-57e3083b919d for patch ID PTCH208915
    [2022-12-19.20:35:25][KacePatch:KacePatchModule::Detec] KacePatchModule::Detect: Processing patch ID: PTCH208916, Name: Autodesk Navisworks Manage 2015 12.3 x64
    [2022-12-19.20:35:25][KacePatch:KacePatchDetectFile::L] KacePatchDetectFile::Load: loaded detect file C:\ProgramData\Quest\KACE\kpd\27d542f8-7dab-49bc-81fd-e77137d6e7aa.kpf
    [2022-12-19.20:35:25][KacePatch:KacePatchDetectFile::P] KacePatchDetectFile::Parse: patch info
    [2022-12-19.20:35:25][KacePatch:KacePatchDetectFile::P] KacePatchDetectFile::Parse: handler specific data
    [2022-12-19.20:35:25][KacePatch:KacePatchDetectFile::P] KacePatchDetectFile::Parse: MSI
    [2022-12-19.20:35:25][KacePatch:DetectFileMsi::ParsePr] DetectFileMsi::ParseProduct: MSI product ID {813D2B53-2300-0000-866C-59F9BC27A235}
    [2022-12-19.20:35:25][KacePatch:KacePatchModule::MsiDe] KacePatchModule::MsiDetect: Finished
    [2022-12-19.20:35:25][KacePatch:KacePatchModule::Detec] KacePatchModule::Detect: Patch PTCH208916 Name Autodesk Navisworks Manage 2015 12.3 x64 Applicable No
    [2022-12-19.20:35:25][KacePatch:KacePatchModule::Detec] KacePatchModule::Detect: Processing patch ID: PTCH208918, Name: Autodesk Navisworks Manage 2016 13.2 x64
    [2022-12-19.20:35:25][KacePatch:KWeb::DownloadSMBFile ] DownloadSMBFile: unable to copy file from: '\\[REDACTED]\KSHARE/repl2/patches/patch_catalog/windows/f642408d-e47c-4618-8364-337eba3dad28.f76b60c944bc3c53ea96983f332c03ae' to: 'C:\ProgramData\Quest\KACE\kpd\f642408d-e47c-4618-8364-337eba3dad28.kpf': (2) The system cannot find the file specified.

    I would also point out that I recently, for this location, changed this from "Detect and Deploy" to simply "Deploy." Detect was taking hours and never finishing and nothing was deploying. There is actually a separate "Detect" routine that runs at another time, and so we didn't need to be doing this twice. - cornponious 3 months ago
  • You need to detect first and then deploy, if you do not detect first, the agent will not notify about needed patches....

    1-Agent runs a detect job
    2-It creates a list of missing patches that are needed in the replication share
    3-Replication share passes this list to the SMA
    4-The SMA sends the payload(the patches) back to the replication share.
    5-Deploy comes in and pulls and install them. - Channeler 3 months ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ