error 0x80096001 after installing Sharepoint

We recently added Sharepoint to a server. Since we did this, Windows Update
no longer works and gives the error 0x80096001.

I have tried installing WSUS on another server and redirecting this server
to WSUS for updates but the WSUS log says exactly same thing. The following
is displayed in the WindowsUpdate.log file every time the server attempts to
check with WSUS.

2006-02-27 07:01:43 1212 778 AU #############
2006-02-27 07:01:43 1212 778 AU ## START ## AU: Search for updates
2006-02-27 07:01:43 1212 778 AU #########
2006-02-27 07:01:43 1212 778 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {4526F542-A654-49EC-A46D-60DDEAE3D478}]
2006-02-27 07:01:43 1212 524 Agent *************
2006-02-27 07:01:43 1212 524 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-27 07:01:43 1212 524 Agent *********
2006-02-27 07:01:43 1212 524 Setup FATAL: IsUpdateRequired failed with error
0x80096001
2006-02-27 07:01:43 1212 524 Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed: 0x80096001
2006-02-27 07:01:43 1212 524 Setup WARNING: SelfUpdate: Default Service:
IsUpdateRequired failed, error = 0x80096001
2006-02-27 07:01:43 1212 524 Agent * WARNING: Skipping scan, self-update
check returned 0x80096001
2006-02-27 07:01:44 1212 524 Agent * WARNING: Exit code = 0x80096001
2006-02-27 07:01:44 1212 524 Agent *********
2006-02-27 07:01:44 1212 524 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-27 07:01:44 1212 524 Agent *************
2006-02-27 07:01:44 1212 524 Agent WARNING: WU client failed Searching for
update with error 0x80096001
2006-02-27 07:01:44 1212 524 AU >>## RESUMED ## AU: Search for updates
[CallId = {4526F542-A654-49EC-A46D-60DDEAE3D478}]
2006-02-27 07:01:44 1212 524 AU # WARNING: Search callback failed, result
= 0x80096001
2006-02-27 07:01:44 1212 524 AU #########
2006-02-27 07:01:44 1212 524 AU ## END ## AU: Search for updates [CallId
= {4526F542-A654-49EC-A46D-60DDEAE3D478}]
2006-02-27 07:01:44 1212 524 AU #############
2006-02-27 07:01:44 1212 524 AU AU setting next detection timeout to
2006-02-27 12:01:44
2006-02-27 07:01:49 1212 524 Report REPORT EVENT:
{5420D029-F014-4EFF-992E-0471DCBB0E96} 2006-02-27
07:01:43-0000 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80096001 SelfUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80096001
2006-02-27 07:14:59 1212 4f4 PT Initializing simple targeting cookie,
clientId = b8ec553e-519d-4f01-86db-4e1e1a26702f, target group = Test, DNS
name = <FQDN of server>
2006-02-27 07:14:59 1212 4f4 PT Server URL =
http://<servername>/SimpleAuthWebService/SimpleAuth.asmx
2006-02-27 07:15:09 1212 4f4 Report Uploading 1 events using cached cookie,
reporting URL =
http://<servername>/ReportingWebService/ReportingWebService.asmx
2006-02-27 07:15:10 1212 4f4 Report Reporter successfully uploaded 1 events.

The WSUS server also reports that the client failed to report even though it
registers with WSUS in the first place.

Please note that all our other servers can connect to both Windows Update
and WSUS correctly.

Thanks,
Adrian
.

Relevant Pages

  • Re: WSUS Client not yet reported
    ... reporting, ... Now the client pc is no longer showing up in WSUS, ... The monitoring component on SBS server was corrupted. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Update wont work on my network anymore. HELP!
    ... wanted to do updates via the server, so I installed WSUS on the system. ... However the clients were not updating in WSUS so I used the Group Policy ... Windows Update STILL does not work on ANY machine at the ...
    (microsoft.public.windowsupdate)
  • RE: Windows Server Update Services 2.0 Error
    ... I examined the configuration for the WSUS site and the scenario number 2 ... On the WSUS Server check the permissions on the following Directory: ... Microsoft Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Check Your Server Configuration
    ... you still get that error message in your WSUS? ... Please note that Windows Server update service currently is not supported ... Microsoft is providing this information as a convenience to you. ... >> site WSUS vroots access settings must be modified to enable WUS clients ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003/WSUS 2.0 Problem
    ... After all is said and done, WSUS setup still gave the same error and I ... Monitoring component we checked in the registry and it appears the ... Please make a full backup of the SBS 2003 server before the following ... select Microsoft SQL Server Desktop Engine ...
    (microsoft.public.windows.server.sbs)