-102: Failed to execute the search. HRESULT: -2147024894

BatchPatch Forums Home › Forums › BatchPatch Support Forum › -102: Failed to execute the search. HRESULT: -2147024894

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • February 13, 2020 at 1:05 pm #12214
    jsira7
    Participant

    Hi Doug,

    I keep getting this same error on this one machine when trying to deploy Windows Updates. I always have cached mode and offline mode enabled, since we have several machines on our network not connected to the internet. We also do not use WSUS. This option works great for approx. 1000 clients, but this system keeps failing on the search. Here’s the full log. Is there anything I could try?

    Windows Update Messages
    Error -102: Failed to execute the search. – 09:56:28
    Local Agent Log
    ::Begin download – 2020-02-13 09:53:11

    Microsoft Offline Scan File
    1> wsusscn2.cab :: Skipped: File already exists in cache

    ::End download – 2020-02-13 09:53:11

    Files downloaded: 0
    Files located in cache: 1
    Files excluded by filter: 0
    Files initiated by another row: 0
    Failures: 0

    ::Begin file copy operation – 2020-02-13 09:53:11

    1> WsusScn2.cab :: File already exists in destination

    ::End file copy operation – 2020-02-13 09:53:11
    Remote Agent Log
    ComputerA 02/13/2020 09:53:12

    ::Begin ‘offline sync service’ search

    -102: Failed to execute the search. HRESULT: -2147024894

    ComputerA 02/13/2020 09:56:21
    All Messages
    02/13 09:56:28> Windows Update: END (Offline mode: Check for available updates)
    02/13 09:56:28> Windows Update: Exit Code: -102
    02/13 09:56:28> Windows Update: Error -102: Failed to execute the search.
    02/13 09:53:11> Windows Update: Executing BatchPatchRemoteAgent.exe…
    02/13 09:53:11> Windows Update: Attempting to initiate Windows Update (Action: Search for updates and retrieve url list: ‘SoftwareAndDrivers’ | Server selection: Offline sync service) …
    02/13 09:53:11> Windows Update: Establishing connection…
    02/13 09:53:11> Windows Update: Initializing…
    02/13 09:53:11> Windows Update: WsusScn2.cab file copy complete
    02/13 09:53:11> Windows Update: Copying WsusScn2.cab file from local cache to target working directory…
    02/13 09:53:11> Windows Update: Queued WsusScn2.cab file copy from local cache to target working directory…
    02/13 09:53:11> Windows Update: Initializing copy of WsusScn2.cab file from local cache to target working directory…
    02/13 09:53:11> Windows Update: Local download complete (Files downloaded: 0. Files located in cache: 1. Files excluded by filter: 0. Files initiated by another row: 0. Failures: 0)
    02/13 09:53:11> Windows Update: Executing WsusScn2.cab downloader…
    02/13 09:53:11> Windows Update: Queued WsusScn2.cab downloader…
    02/13 09:53:11> Windows Update: BEGIN (Offline mode: Check for available updates)
    02/13 09:53:11> Windows Update: Queued…
    —————————————————————————————————-

    February 13, 2020 at 2:10 pm #12215
    doug
    Moderator

    Strange. I would start by deleting the wsusscn2.cab file from the target computer’s BatchPatch folder (default location is C:\Program Files\BatchPatch). Then try again and see what happens. BP will copy a fresh copy of the file, and that might do the trick but probably not.

    The next thing to try is on the target computer stop the Windows Update service, then rename C:\Windows\SoftwareDistribution to C:\Windows\SoftwareDistribution.old . Then restart the Windows Update service and try again. Windows will automatically create a fresh C:\Windows\SoftwareDistribution folder. This process will wipe the Windows Update history database on the target computer because it is stored in that folder, which is not necessarily a huge deal, but it should be noted in case you care about it. If the process works to solve the issue, then you’ll just move forward with the new SoftwareDistribution folder that Windows will automatically create when you restart the Windows Update service. If the process does not work, then you can just stop the service again, rename the newly created C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistribution.old2 , and then rename your original C:\Windows\SoftwareDistribution.old back to C:\Windows\SoftwareDistribution. Then start the service again and you’ll be back to where you were before you started messing with that folder in the first place.

    If still no luck, the next thing I would try is the solution outlined by @tinpot at this link. There is probably some file or registry corruption or some weird permissions issue on that target computer that is causing problems. The solution @tinpot posted might help you figure out what exactly is going on.

    -Doug

    February 14, 2020 at 11:19 am #12219
    jsira7
    Participant

    Thanks Doug… I will give this a go and report back

    February 14, 2020 at 12:11 pm #12220
    jsira7
    Participant

    Hey Doug,

    I tried the first two troubleshooting ideas you mentioned, but to no avail. I then researched the article you mentioned. I wasn’t able to find anything mysterious in the CBS.log, but maybe you can see something that I can’t. Here’s the info from the log:

    2020-02-14 08:39:49, Info CBS TI: — Initializing Trusted Installer —
    2020-02-14 08:39:49, Info CBS TI: Last boot time: 2020-02-13 09:37:33.500
    2020-02-14 08:39:49, Info CBS Starting TrustedInstaller initialization.
    2020-02-14 08:39:49, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
    2020-02-14 08:39:49, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
    2020-02-14 08:39:49, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
    2020-02-14 08:39:49, Info CBS Ending TrustedInstaller initialization.
    2020-02-14 08:39:49, Info CBS Starting the TrustedInstaller main loop.
    2020-02-14 08:39:49, Info CBS TrustedInstaller service starts successfully.
    2020-02-14 08:39:49, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2020-02-14 08:39:49, Info CBS Startup processing thread terminated normally
    2020-02-14 08:39:49, Info CBS TI: Startup Processing completes, release startup processing lock.
    2020-02-14 08:39:49, Info CBS WU creates the package, AppID:BatchPatch, UpdateID:{B0B46B74-A0CE-4F74-960F-F7679C1E7304}, revision: 200
    2020-02-14 08:39:49, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4538674~31bf3856ad364e35~amd64~~18362.651.1.0, ApplicableState: 112, CurrentState:112
    2020-02-14 08:39:52, Info CBS WU creates the package, AppID:BatchPatch, UpdateID:{62F62686-8AC6-40CF-81EA-061DBA11458B}, revision: 200
    2020-02-14 08:39:53, Info CBS Read out cached applicability from TiLight for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.657.1.7, ApplicableState: 112, CurrentState:112
    2020-02-14 08:39:55, Info CBS WU creates the package, AppID:BatchPatch, UpdateID:{A485DC85-A3F4-4243-8AC0-F805A4A6889F}, revision: 200
    2020-02-14 08:39:55, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4524244~31bf3856ad364e35~amd64~~10.0.1.6, ApplicableState: 112, CurrentState:0
    2020-02-14 08:39:56, Info CBS WU creates the package, AppID:BatchPatch, UpdateID:{6252BF47-4C3A-4687-A1BC-378227C4B8A0}, revision: 200
    2020-02-14 08:39:56, Info CBS Read out cached applicability from TiLight for package: Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3105, ApplicableState: 112, CurrentState:0
    2020-02-14 08:39:56, Info CBS WU creates the package, AppID:BatchPatch, UpdateID:{41CC88C3-630F-4528-803E-DE824F58958C}, revision: 200
    2020-02-14 08:39:56, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4537759~31bf3856ad364e35~amd64~~10.0.1.0, ApplicableState: 112, CurrentState:0
    2020-02-14 08:41:56, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2020-02-14 08:41:56, Info CBS Ending the TrustedInstaller main loop.
    2020-02-14 08:41:56, Info CBS Starting TrustedInstaller finalization.
    2020-02-14 08:41:56, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
    2020-02-14 08:41:56, Info CBS Ending TrustedInstaller finalization.

    February 14, 2020 at 2:38 pm #12221
    doug
    Moderator

    I don’t know what is going on with that one system, but you might try using the system file checker to try to repair any issues. What OS is it?

    August 13, 2020 at 3:37 pm #12458
    doug
    Moderator

    Please see BatchPatch Error: -102: Failed to execute the search. HRESULT -XXXXXXXXXX for more details on this error. We’ve had a handful of users report that installing Silverlight resolved the issue for them.

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.