- This topic has 2 replies, 2 voices, and was last updated 5 years, 2 months ago by .
-
Posts
-
Hello Dear,
I have a problem with the function “Generate consolidated report of available update” in Windows 2012!
look;
qua-10:09:24> Windows Update: Error -102: Failed to execute the search.
qua-10:09:02> Windows Update: Executing BatchPatchRemoteAgent.exe…
qua-10:09:02> Windows Update: Attempting to initiate Windows Update (Action: Search for updates. Server selection: Default / Managed) …
qua-10:09:02> Windows Update: Establishing connection…
qua-10:09:02> Windows Update: Initializing…
qua-10:09:02> Windows Update: Queued… (Check for available updates)
qua-10:08:23> Windows Update: Error -102: Failed to execute the search.
qua-10:08:17> Windows Update: Executing BatchPatchRemoteAgent.exe…
qua-10:08:17> Windows Update: Attempting to initiate Windows Update (Action: Search for updates . Server selection: Default / Managed) …
qua-10:08:17> Windows Update: Establishing connection…
qua-10:08:17> Windows Update: Initializing…
qua-10:08:17> Windows Update: Queued…
and other error
Windows Update Messages
Error 1601: Failed to retrieve WMI info. The requested object does not exist. (Exception from HRESULT: 0x80010114) – 11:39:49
All Messages
qua-11:39:49> Windows Update: Error 1601: Failed to retrieve WMI info. The requested object does not exist. (Exception from HRESULT: 0x80010114)
qua-11:39:49> Windows Update: Initializing…
qua-11:39:49> Windows Update: Queued…
qua-11:39:04> Windows Update: Error 1601: Failed to retrieve WMI info. The requested object does not exist. (Exception from HRESULT: 0x80010114)
qua-11:39:04> Windows Update: Initializing…
qua-11:39:03> Windows Update: Queued… (Check for available updates)
Could you help please?
thanks
Error -102: Failed to execute the search
–This error is also discussed at Troubleshooting Common Errors in BatchPatch
The -102 error occurs any time the target computer is unable to execute the search for updates. The HRESULT code that is reported with the -102 error is the key to determining the specific reason for the failure. If you closed BatchPatch without saving the HRESULT code, you can still view this in the target computer’s BatchPatch.log and/or BatchPatchError.log, which will both be stored in the remote working directory. The default location is C:Program FilesBatchPatch unless you have modified the ‘Remote working directory’ location under ‘Tools > Settings > General.’ HRESULT codes will be in decimal format, but we need to convert them to hex in order to figure out what they mean. To do that, you can use a tool such as the one available here: Decimal to Hex Converter. Once you have the hex representation of the HRESULT, you can look it up here to see what it means: Windows Update Error Code List
In almost all cases the cause is due to a connectivity issue where the target computer is unable to reach or communicate with the WSUS server, ‘Windows Update’ server or ‘Microsoft Update’ server. In the event that a local WSUS server is the location being searched, the most common cause for this error is simply due to the WSUS server being down or offline or unreachable due to some type of network problem. In the event that the location being searched is Windows Update or Microsoft Update, this error is usually the result of the target computer simply not having internet access and therefore not being able to reach Microsoft’s servers. In some cases, the cause of this error is due to a proxy configuration preventing the Windows Update Agent on the target computer from accessing the Windows Update server. For more information on proxies and Windows Update, please see the following links:
Using BatchPatch with an Enterprise Web Proxy
Error 1601: Failed to retrieve WMI info. The requested object does not exist. (Exception from HRESULT: 0x80010114)
This WMI error 0x80010114 could be a couple of different things:
0. Make sure WMI is running on the target. The ‘Windows Management Instrumentation’ service needs to be started/running.
1. There might be some sort of weird memory corruption. Try a simple reboot of the target host.
2. WMI might be corrupt on the target computer. To solve this, the WMI repository would need to be rebuilt. The following link contains steps for rebuilding the WMI repository, but if you suspect that your WMI repository is corrupt, I would recommend that you do some google research before performing any actions:
https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/
3. You are dealing with a cluster, not a single server. In this case, please review the troubleshooting steps on the following page:
For all other -102 HRESULT values, please see batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
- You must be logged in to reply to this topic.