AKX wrote:
> Hello,
>
> I've been getting a rather annoying error when I try to search for
> updates in Windows Update (and Microsoft Update as well) -- it merely
> tells me that there's been a problem, error code 0x80010105. The
> \Windows\WindowsUpdate.log tails as follows (I removed some stars and
> dashes from there):
>
> 2856 c38 Service ** START ** Service: Service startup
> 2856 c38 Agent * WU client version 5.8.0.2469
> 2856 c38 Agent * SusClientId = '532fdb4c-51c4-4c0d-a0e4-ce41a4379a9d'
> 2856 c38 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
> 2856 c38 Agent * Access type: No proxy
> 2856 c38 Agent * Network state: Connected
> 2856 700 Agent Agent: Initializing Windows Update Agent
> 2856 700 Agent Agent: Initializing global settings cache
> 2856 700 Agent * WSUS server: <NULL>
> 2856 700 Agent * WSUS status server: <NULL>
> 2856 700 Agent * Target group: (Unassigned Computers)
> 2856 700 Agent * Windows Update access disabled: No
> 2856 700 DnldMgr Download manager restoring 0 downloads
> 2380 110 COMAPI -- START -- COMAPI: Search [ClientId = WindowsUpdate]
> 2380 110 COMAPI - Online = Yes; Ignore download priority = No
> 2380 110 COMAPI - Criteria = "IsInstalled=0 and IsHidden=1"
> 2380 110 COMAPI - ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77}
> 2380 110 COMAPI WARNING: ISusInternal::BeginFindUpdatesEx failed,
> hr=80010105
> 2380 110 COMAPI - WARNING: Exit code = 0x80010105
> 2380 110 COMAPI -- END -- COMAPI: Search [ClientId = <NULL>]
> 2380 110 COMAPI FATAL: Unable to initiate asynchronous search,
> hr=80010105
>
> Should the WSUS server be null or the target group unassigned?
If you don't have a WSUS server, yes, but if you have installed a
WSUS server, it should absolutely not be null.
> I have
> tried to incinerate the SoftwareDistribution folder, re-register DLLs,
> set security descriptors to no avail.
>
> Does anyone else have (or had) this problem, and how was it resolved,
> or can anyone give me any tips on how to fix this without reinstalling
> Windows?
0x80010105 is RPC_E_Serverfault
I have no idea what can cause this, and a search for 0x80010105 doesn't
come up with anything relevant as I can see.
Also check your event logs for any clues:
Start/Run --> eventvwr.msc
--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx