This project has moved and is read-only. For the latest updates, please go here.

[SOLVED] - WinUpdate Failure 802000F and Trigger for SQL Database did not work

Topics: Configuration Issue
Aug 8, 2014 at 1:05 PM
Hello together,

at first sorry when my english is not so good. I´m from Germany and don´t use is very often. But hopefully it is understandable.

At the company we have Server Windows Server 2008 R2, WSUS 3.2 and a SQL Server 2008 R2.

The normal installation of WSUS PP wasn´t a problem and all is function correctly.

But we have two issues since we use WSUS PP. One is a strong problem and the other is just for comfort.

The strong Problem is a Clientside problem with the WSUS. We get on numeros machines the Error Code 8024000F. The only Solution is to new install the Windows 7 (x64) and all Programms... it is a really bad Solution but the only working.
After trying much of the not working Solutions given by Microsoft and other Websites. Someone had a solution for that? This problem is since the first use of WSUS PP.

The comfort Problem is to integrate the Trigger in the SQL Database. I´m connecting to the Database with the Windows Authentication, using the Domain Administrator. The Server name is:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
At the moment i have to start the SSMS and to start a new Querry with this:
SET QUOTED_IDENTIFIER ON
GO
USE SUSDB;
UPDATE [SUSDB].[dbo].[tbUpdate] SET [IsLocallyPublished] = 0 WHERE [IsLocallyPublished] <> 0
I was reading that a Trigger can be put in the SUSDB but this isn´t function correctly. This is the Code:
USE [SUSDB]
GO
/****** Object:  Trigger [dbo].[SwitchLocallyPublished]    Script Date: 07.04.2013 15:37:05 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

CREATE TRIGGER [dbo].[SwitchLocallyPublished] ON [dbo].[tbUpdate]
AFTER INSERT
NOT FOR REPLICATION
AS

begin
UPDATE [SUSDB].[dbo].[tbUpdate] SET [IsLocallyPublished] = 0 WHERE [IsLocallyPublished] <> 0
End
If i Debug the Code it say that all is correct, but If i tell he has to 'Execute' it he gives following Message:
Msg 33003, Level 16, State 1, Procedure SwitchLocallyPublished, Line 8
DDL statement is not allowed.
I hope my english wasn´t to bad. If it was please feel free to ask questions.
Aug 8, 2014 at 2:14 PM
You don't need the Trigger for WPP. In WPP you can set in Extras that WPP shows Updates in WSUS-Console.
Or you set this Setting for every Update you publish.
Aug 12, 2014 at 8:45 PM
Hi,
The strong Problem is a Clientside problem with the WSUS. We get on numeros machines the Error Code 8024000F
This error code mean : "cycle detected in meta data"
This mean that one or more update has wrong rules.
Please, on an affected client, go to C:\Windows\ and open the file WindowsUpdate.log
Copy/paste its content here.
Aug 13, 2014 at 8:29 AM
Hello WinfriedSonntag,
i forgot to restart the WSUS Server, now i can doesn´t need the SQL workaround anymore. Big thank you.

Hello DCourtel,
here i have a fresh Output from the windowsupdate.log
2014-08-13  08:41:09:054     968    1334    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0200)  ===========
2014-08-13  08:41:09:054     968    1334    Misc      = Process: C:\Windows\system32\svchost.exe
2014-08-13  08:41:09:054     968    1334    Misc      = Module: c:\windows\system32\wuaueng.dll
2014-08-13  08:41:09:054     968    1334    Service *************
2014-08-13  08:41:09:054     968    1334    Service ** START **  Service: Service startup
2014-08-13  08:41:09:054     968    1334    Service *********
2014-08-13  08:41:09:056     968    1334    Agent     * WU client version 7.6.7600.256
2014-08-13  08:41:09:056     968    1334    Agent     * Base directory: C:\Windows\SoftwareDistribution
2014-08-13  08:41:09:056     968    1334    Agent     * Access type: No proxy
2014-08-13  08:41:09:056     968    1334    Agent     * Network state: Connected
2014-08-13  08:41:15:137     968    1094    Report  CWERReporter::Init succeeded
2014-08-13  08:41:15:137     968    1094    Agent   ***********  Agent: Initializing Windows Update Agent  ***********
2014-08-13  08:41:15:137     968    1094    Agent   ***********  Agent: Initializing global settings cache  ***********
2014-08-13  08:41:15:137     968    1094    Agent     * WSUS server: http://ANGHH03:8530
2014-08-13  08:41:15:137     968    1094    Agent     * WSUS status server: http://ANGHH03:8530
2014-08-13  08:41:15:137     968    1094    Agent     * Target group: Workstation
2014-08-13  08:41:15:137     968    1094    Agent     * Windows Update access disabled: No
2014-08-13  08:41:15:137     968    1094    DnldMgr Download manager restoring 0 downloads
2014-08-13  08:41:15:138     968    1094    AU  ###########  AU: Initializing Automatic Updates  ###########
2014-08-13  08:41:15:138     968    1094    AU    # WSUS server: http://ANGHH03:8530
2014-08-13  08:41:15:138     968    1094    AU    # Detection frequency: 12
2014-08-13  08:41:15:138     968    1094    AU    # Target group: Workstation
2014-08-13  08:41:15:138     968    1094    AU    # Approval type: Scheduled (Policy)
2014-08-13  08:41:15:138     968    1094    AU    # Scheduled install day/time: Every day at 12:00
2014-08-13  08:41:15:138     968    1094    AU    # Auto-install minor updates: Yes (Policy)
2014-08-13  08:41:15:139     968    1094    AU  Setting AU scheduled install time to 2014-08-13 10:00:00
2014-08-13  08:41:15:335     968    1334    Report  ***********  Report: Initializing static reporting data  ***********
2014-08-13  08:41:15:335     968    1334    Report    * OS Version = 6.1.7601.1.0.65792
2014-08-13  08:41:15:335     968    1334    Report    * OS Product Type = 0x00000030
2014-08-13  08:41:15:343     968    1334    Report    * Computer Brand = Dell Inc.
2014-08-13  08:41:15:344     968    1334    Report    * Computer Model = OptiPlex 780                 
2014-08-13  08:41:15:345     968    1334    Report    * Bios Revision = A04
2014-08-13  08:41:15:345     968    1334    Report    * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A04
2014-08-13  08:41:15:345     968    1334    Report    * Bios Release Date = 2010-04-30T00:00:00
2014-08-13  08:41:15:345     968    1334    Report    * Locale ID = 1031
2014-08-13  08:41:15:346     968    1094    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:15:346     968    1094    AU  Initializing featured updates
2014-08-13  08:41:15:346     968    1094    AU  Found 0 cached featured updates
2014-08-13  08:41:15:346     968    1094    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:15:348     968    1094    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:15:348     968    1094    AU  AU finished delayed initialization
2014-08-13  08:41:15:348     968    b3c AU  Triggering AU detection through DetectNow API
2014-08-13  08:41:15:348     968    b3c AU  Triggering Online detection (interactive)
2014-08-13  08:41:15:348     968    1334    AU  #############
2014-08-13  08:41:15:348     968    1334    AU  ## START ##  AU: Search for updates
2014-08-13  08:41:15:348     968    1334    AU  #########
2014-08-13  08:41:15:360     968    1334    AU  <<## SUBMITTED ## AU: Search for updates [CallId = {A7B5172C-7E73-4EFC-91AE-8020D574BDF3}]
2014-08-13  08:41:15:367     968    11a0    Agent   *************
2014-08-13  08:41:15:367     968    11a0    Agent   ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-08-13  08:41:15:367     968    11a0    Agent   *********
2014-08-13  08:41:15:367     968    11a0    Agent     * Online = Yes; Ignore download priority = No
2014-08-13  08:41:15:367     968    11a0    Agent     * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-08-13  08:41:15:367     968    11a0    Agent     * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-08-13  08:41:15:367     968    11a0    Agent     * Search Scope = {Machine}
2014-08-13  08:41:15:367     968    11a0    Setup   Checking for agent SelfUpdate
2014-08-13  08:41:15:368     968    11a0    Setup   Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
2014-08-13  08:41:15:368     968    11a0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-08-13  08:41:15:386     968    11a0    Misc     Microsoft signed: Yes
2014-08-13  08:41:15:394     968    11a0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-08-13  08:41:15:399     968    11a0    Misc     Microsoft signed: Yes
2014-08-13  08:41:15:410     968    11a0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-08-13  08:41:15:416     968    11a0    Misc     Microsoft signed: Yes
2014-08-13  08:41:15:420     968    11a0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-08-13  08:41:15:425     968    11a0    Misc     Microsoft signed: Yes
2014-08-13  08:41:15:443     968    11a0    Setup   Determining whether a new setup handler needs to be downloaded
2014-08-13  08:41:15:443     968    11a0    Setup   SelfUpdate handler is not found.  It will be downloaded
2014-08-13  08:41:15:443     968    11a0    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-13  08:41:15:445     968    11a0    Setup   Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-08-13  08:41:15:445     968    11a0    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-13  08:41:15:463     968    11a0    Setup   Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-08-13  08:41:15:463     968    11a0    Setup   Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-08-13  08:41:15:487     968    11a0    Setup   Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-08-13  08:41:15:488     968    11a0    Setup   SelfUpdate check completed.  SelfUpdate is NOT required.
2014-08-13  08:41:16:599     968    11a0    PT  +++++++++++  PT: Synchronizing server updates  +++++++++++
2014-08-13  08:41:16:599     968    11a0    PT    + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ANGHH03:8530/ClientWebService/client.asmx
2014-08-13  08:41:16:673     968    11a0    PT  WARNING: CAgentUpdateManager::DetectForUpdates failed: 0x8024000f
2014-08-13  08:41:16:673     968    11a0    PT  WARNING: Sync of Updates: 0x8024000f
2014-08-13  08:41:16:673     968    11a0    PT  WARNING: SyncServerUpdatesInternal failed: 0x8024000f
2014-08-13  08:41:16:673     968    11a0    Agent     * WARNING: Failed to synchronize, error = 0x8024000F
2014-08-13  08:41:16:674     968    11a0    Agent     * WARNING: Exit code = 0x8024000F
2014-08-13  08:41:16:674     968    11a0    Agent   *********
2014-08-13  08:41:16:674     968    11a0    Agent   **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2014-08-13  08:41:16:674     968    11a0    Agent   *************
2014-08-13  08:41:16:674     968    11a0    Agent   WARNING: WU client failed Searching for update with error 0x8024000f
2014-08-13  08:41:16:699     968    10e0    AU  >>##  RESUMED  ## AU: Search for updates [CallId = {A7B5172C-7E73-4EFC-91AE-8020D574BDF3}]
2014-08-13  08:41:16:699     968    10e0    AU    # WARNING: Search callback failed, result = 0x8024000F
2014-08-13  08:41:16:699     968    10e0    AU    # WARNING: Failed to find updates with error code 8024000F
2014-08-13  08:41:16:699     968    10e0    AU  #########
2014-08-13  08:41:16:699     968    10e0    AU  ##  END  ##  AU: Search for updates [CallId = {A7B5172C-7E73-4EFC-91AE-8020D574BDF3}]
2014-08-13  08:41:16:699     968    10e0    AU  #############
2014-08-13  08:41:16:699     968    10e0    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:16:700     968    10e0    AU  AU setting next detection timeout to 2014-08-13 11:41:16
2014-08-13  08:41:16:700     968    10e0    AU  Setting AU scheduled install time to 2014-08-13 10:00:00
2014-08-13  08:41:16:700     968    10e0    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:16:701     968    10e0    AU  Successfully wrote event for AU health state:0
2014-08-13  08:41:20:345     968    11a0    Report  REPORT EVENT: {3DE87138-5BF7-431A-B536-AA4A1594C77F}    2014-08-13 08:41:16:674+0200    1   148 101 {00000000-0000-0000-0000-000000000000}  0   8024000f    AutomaticUpdates    Failure Software Synchronization    Windows Update Client failed to detect with error 0x8024000f.
2014-08-13  08:41:20:360     968    11a0    Report  CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-08-13  08:41:20:360     968    11a0    Report  WER Report sent: 7.6.7600.256 0x8024000f 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2014-08-13  08:41:20:360     968    11a0    Report  CWERReporter finishing event handling. (00000000)
The certificate is installed on this machine and 'gpupdate' works fine. The WSUS Server (ANGHH03) is the Company WSUS Server.
In the WPP I can do a 'Scan now' and 'Report now' wihtout failure, when i let WPP search for missing Updates i becam the Error Message "COM Exception! Verify the firewall settings on the remote computer." ... the firewall is off for all three Networktypes.

The old (I deletet the old windowsupdate.log today) i can Post too, but it is a large File from 2014-06-13 to today.

Thanks for the help.
Aug 13, 2014 at 10:43 AM
Hi, the error code is still here, but the log didn't tell us in which update the problem is.
You should activate extra-logging :

To turn on verbose logging, add the following registry key with two values:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace
Value name: Flags
Value type: REG_DWORD
Value data: 00000007

Value name: Level
Value type: REG_DWORD
Value data: 00000004
This registry key turns on an extended tracing to the %systemroot%\Windowsupdate.log file. Additionally, this registry key turns on an extended tracing to any attached debuggers.

Restart the computer. Delete the log, and launch a new detection.

Don't forget to disable extra-logging when done.
Aug 14, 2014 at 9:10 AM
Edited Aug 14, 2014 at 9:10 AM
Hello,

i have finaly Uploaded the File on SkyDrive. Cause it is to much text für the Board. Hope it is okay.
windowsupdate.log
Aug 14, 2014 at 10:01 AM
Hi,

pls have a look in the WSUS-FAQ No. 44: http://www.wsus.de/faq

Here you find the Build Numbers from WSUS.
In this Image you will find the place you have to look to the Build Numbers: http://www.wsus.de/images/wsus-version.png

WSUS 3.0 (SP2): Build 3.2.7600.226
WSUS 3.0 (SP2) + KB2720211: Build 3.2.7600.251
WSUS 3.0 (SP2) + KB2734608: Build 3.2.7600.256
WSUS 3.0 (SP2) + KB2828185: Build 3.2.7600.262
WSUS 3.0 (SP2) + KB2938066: Build 3.2.7600.274

Pls control the build numbers from you WSUS. If your WSUS is not on .274, install the updates for coming up to build .274. After this, your clients have to reconnect to WSUS and they will download some files for local Windows Update Agent. Now you can check again %windir%\WindowsUpdate.log for Errormessages.

Do you find files they are not downloaded? Downloadstatus on the WSUS-Startpage: http://www.wsus.de/images/wsus-version.png

Here your Errorcode is listed: http://www.wsus.de/errorcodes.htm
Can you run the Cleanup Wizard in WSUS? Pls run it 2 or 3 times. Is the Synchronization to Microsoft Server succesfull?
Aug 14, 2014 at 12:22 PM
Hello Winfried,

the last three KBs are missing. I downloaded them and will install them on Sunday, cant reboot the Server before. :(

I would replay next week.

Great thanks you two for helping.
Aug 15, 2014 at 11:26 AM
Hi, in the log, we can see : DetectFailed={__8E9567AE-D662-4BDD-AA20-DA86CF9BD49D__}

Open WPP, select each updates one by one and look at the 'Id' field on the Informations tab. Try to locate this UpdateId. Once this is done, look at 'IsIntalled' rules, 'IsInstallable' Rule, Prerequisite, Supersedes update and try to find what's going wrong.

You will probably need to 'Decline' this update then 'Delete' it before re-creating it a differente way.
Aug 15, 2014 at 11:38 AM
Edited Aug 15, 2014 at 11:38 AM
Hello DCourtel,

i searched in WPP for this Update but did not found it.
Could it be a already deletet Update? And if this is the problem... how can i fix this?

I delete the files after a new Update is released. It could be a Flash or a Java Update.
Aug 15, 2014 at 11:50 AM
Edited Aug 15, 2014 at 4:23 PM
Could it be a already deletet Update?
Yes, it's possible.
And if this is the problem... how can i fix this?
On each computer that show the error, Stop 'Windows Update Service' and delete the folder C:\Windows\SoftwareDistribution. Then start 'Windows Update service'. Wait 1 minute and performe a check for update (WuAuClt /DetectNow)
Marked as answer by AntHalus on 8/15/2014 at 7:15 AM
Aug 15, 2014 at 3:15 PM
DCourtel... ThankYou!!! This was it.
I don`t know why it did it now. I was trying it at first... but it is doing it now. :)

Really really big thanks WinfriedSonntag and DCourtel!