offline mode error -102

[dtodd]

Hello,

I have two machine which are configured to cache and offline line mode.
The catalog file copies to the local directory, I can see the agent appear in the program folder\batchpatch when trying to update and the cache folder is configured to a local temp location.

I’m getting an error
Error -102: Failed to execute the search. HRESULT: -2147012894
Which translates to proxy issue BUT there is no Internet connection and the only NIC is the MS loop adapter.

It seem like BatchPatch is still trying to access the Internet while in offline mode.

I’m using the latest version of BP and have tried an older version of PsExec and the 2.33 version with the same results.

Any suggestions?

[doug]

It’s not clear to me how this error could be possible under cached mode. Furthermore, while BatchPatch is capable of running on a computer and targeting itself (so BP computer is both source and target), BP does require that the computer have a NIC, even if it’s not connected to an actual network. I just did a test where I ran BatchPatch on a computer with no NIC (where I entered the computer that BatchPatch was running on as a target computer into a row in the BatchPatch grid), and the error that I see in BatchPatch is “Error 1800: Failed to create remote working directory” which is what we would expect because while BatchPatch does not need internet access to run in offline mode, it does still require a NIC in the computer and for the local network to be functional (because BatchPatch essentially will make network calls to the target computer in that case, even if the target computer is also the source computer), so it’s a network call to itself, effectively, when no network cable is even plugged in. That said, I don’t know how you could have gotten the error that you got in the situation that you described. If you have an active support contract with us, please reach out to us directly. We will want to see an HTML grid export of your grid that shows the entire context of what you’re doing. In this way we’ll be able to see exactly what’s going on in your situation and if there might be any other ways to accomplish what you’re hoping to do. It might simply not be possible, but I’m unsure at the moment with the limited info we have on the situation.

[dtodd]

A little more details:

I use BP on a few air gapped machines and typically I can burn the latest updates and wsusscn file to a disc, sneaker net it to the machine, copy the files to a temp folder and run BP in cached/offline mode and the cache pointed to the temp folder.

I usually have to add the MS loopback test adapter for a visual network interface in order give BP something to communicate through (because NICs are not allowed on the workstations). Again, this works on other machines in the same configuration.

What I’m experiencing, running BP as Admin, I add the local machine > elect the download, install and reboot option and wait. On two machines the operation fails with Error -102 (-2147012894). The help documentation describes this issue as a timeout and proxy settings issue. I can confirm the app is set in offline mode so I’m not sure why it’s trying to connect to the Internet.

Durning the process, BP copies the wsusscn to the C:\Program File\BatchPatch folder and begins to execute the BatchPatchagent app and seem to stall there and after 3 minutes returns the error -102.

I have tried two versions of BP and swamped the PsExec thinking there might be an issue but I’m still stuck. I did check the PsExec app to make sure is was unblocked and I ran it from the command line to accept the EULA.

The workstations are Windows 10 1809 LTSC. They are hardened so I’t possible there is a GPO in the way put given the process works on other like machines I’m at a loss.

Is there a debug option, direction you can point me in or advice?

Thanks

[doug]

The -102 error occurs when BP issues the “Search” command to the Windows Update Agent (WUA). The WUA in this case is returning 0x80072EE2 -2147012894 ERROR_INTERNET_TIMEOUT. A few things to note:

1. ERROR_INTERNET_TIMEOUT may not specifically be referring to the “internet”. It could potentially just be referring to a network call, in general. There isn’t a way to know for sure in this case.

2. The only time we have seen this error occur is in the case where a proxy was the cause, but that doesn’t mean that a proxy is the *only* cause of this error.

3. When running in offline mode, the search for updates is performed against the WsusScn2.cab file, not a WSUS, and not a Microsoft public Windows Update server. However, the WUA operates somewhat as a black box, and it’s hard to know what specifically it’s hiccuping on in this case. There are really only a few things that come to mind:

A. Check for dual scan.

“Dual Scan” Difficulties with Windows Update on Windows 10 versions 1607 ‘Anniversary update’ and 1703 ‘Creators update’

Deciphering “Dual Scan” Behavior in Windows 10

B: Also check all Group Policies, particularly the ones related to Windows Update. I would suggest that if you have two computers that are seemingly identical in their configurations but with this problem occurring on one computer but not the other, it makes sense to do a full group policy audit on the two computers to compare the policies that are enabled. It seems like there is a decent chance that you’ll see immediately that there’s a particular policy that’s enabled on one computer but not the other and is causing the issue.

C: Check the WindowsUpdate.log to see if it reveals the culprit. There was a time when this log was much more useful than it tends to be nowadays, but it’s definitely still worth taking a look. ‘Actions > Windows Updates > View Windows Update Log’ Note, this might be a problem to retrieve because I believe the process it has to go through to convert the log into human-readable form requires it to be able to download symbols from the internet.

[doug]

For other HRESULT values please see: https://batchpatch.com/batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx

[Author]

Posts