Hi,

for this issue I have already found the thread "http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/2408f2ab-06a8-497e-bf55-a6a0b88d2d15" in this forum but the answer those not corresponds to my case.

My there replica servers which I rebuild new cannot synchronize with the upstream server successfully. According to the logfile there are four updates which are causing this problem. My other replica servers have no problem with these four updates.

The four updates can be found on the upstream server but not on the replica downstream servers.

Upstream server: 3.2.7600.251

Downstream replica servers: 3.2.7600.251

The there downstream replica servers are been rebuild new.

Declining these updates on the upstream server did not help.

2013-01-27 13:08:43.561 UTC Error WsusService.12 CatalogSyncAgentCore.ExecuteSyncProtocol 4 update(s) could not be imported into the local db even with retry
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
2013-01-27 13:08:43.561 UTC Error WsusService.12 CatalogSyncAgentCore.ExecuteSyncProtocol Bad Update Revision #0: 78b86d45-2b71-447d-ae7b-cedf21e63416/103
..
2013-01-27 13:08:43.561 UTC Error WsusService.12 CatalogSyncAgentCore.ExecuteSyncProtocol Bad Update Revision #1: f3a49632-6c6f-4bed-8698-81490e759510/103
…
2013-01-27 13:08:43.561 UTC Error WsusService.12 CatalogSyncAgentCore.ExecuteSyncProtocol Bad Update Revision #2: 6f605520-7281-49ba-821b-8e87610f8aaa/103
…
2013-01-27 13:08:43.577 UTC Error WsusService.12 CatalogSyncAgentCore.ExecuteSyncProtocol Bad Update Revision #3: 5092f51e-64b8-4ad4-a169-df0843cc0e4d/103
…
2013-01-27 13:10:56.217 UTC Info WsusService.12 EventLogEventReporter.ReportEvent EventId=386,Type=Error,Category=Synchronization,Message=Synchronization failed. Reason: System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'RevisionID', table '@BundleAll'; column does not allow nulls. INSERT fails.
Error loading information from upd:BundledUpdates/upd:UpdateIdentity for update 78B86D45-2B71-447D-AE7B-CEDF21E63416\103. Some update revisions in bundle information are not already present in the database.
The statement has been terminated.

Thanks for any help.

kailar

On a Windows Server 2008 Standard OS, I would like to implement WSUS for a small organization, using the simplest possible configuration for WSUS. While looking at the procedure for installation of the service, I saw that one of Roles for the server would be IIS with a security service for "Windows Authentication". The description of this service in Server Manager includes the following sentence: "This authentication scheme allows administrators in a Windows domain to take advantage of the domain infrastructure for authenticating users."

My question, therefore, is whether having a Windows domain is required for implementing WSUS or can it be implemented in a workgroup only environment? I can add that in this particular situation there would be no authentication of users needing to occur in any case because only the administrator himself would be making use of the service on these machines.

Also, would WSUS also work for systems installed in virtual machines? Thanks you.

We have recently setup a couple new servers and trying to get WSUS to work. The primary server that runs WSUS can get updates and can be seen in the WSUS console, however our 2nd server isn't detected by the console. There is definite network connectivity and I can ping between the two servers. There is no proxy set as well.

The windowsupdate.log primarily gives me:

Reporter failed to upload events with hr = 80072efd
Send failed with hr = 80072efd
PTError: 0x80072efd
RefreshConfig failed: 80072efd
RefreshPTState failed: 80072efd
+Last proxy send request failed with hr = 80072efd, HTTP status code = 0
+Caller provided credentials = No

I am also getting all those same things with 80072ee2

Given the UniqueUpdateID (or other data from SCCM databse) how can I programmatically determine a Security Update's file size?

I assume that this data is not available in the SCCM database (because I haven't been able to find it) and that it is in the WSUS database.

I am responsible for reporting (with SSRS) on our monthly patch distribution to 30,000+ workstations and I have a requirement to identify (and exclude from the success rate calculation) those updates that are over 5MB in size. These patches are excluded from our SLA because we have many slow links that may not be able to deliver those patches on time. I've been led to believe that querying the WSUS database is not a supported function so I'd rather not do that but without another solution I will likely have to go that route.

This was easy with ITMU as there was a known folder path to the deployment package in SMS and each patch was in it's own folder which had the UniqueUpdateID as it's name. Now with SCCM and WSUS, I have not been able to figure out how to get this data through code. I can see the file size in the SCCM console but I don't think it's in the SCCM database. I understand that querying the WSUS database is not a supported function.

JD

Wsus installation fails with following alert.

"Windows Server update service 3.0 sp2 Setup cannot continue. Please resolve the following issues, and then reun the Setup again.
At least 1 GB of free disk space on the system drive is necessary for this installation."

Details about my system:
New installation of windows server 2008 sp2 x64 standard on Dell PE R710 with 2 quad core intels,  16 GB ram, 2.3TB NTFS  system partition with over 2.2 TB of free space.

Is there a max system partition size limition for  wsus or is this a bug in the installer?

Anyone out there able to install WSUS on system partition greater than 2TB?

Recently, Microsoft has identified a possible issue with WSUS server and Windows update clients.
These issues would occur and reflect in event logs with following event ID:
Event ID: 16
In the WindowsUpdate.log you may see the following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
While going through event logs under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational you may find an error event ID: 25 as follows
===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 25
Task Category: Windows Update Agent
Level: Error
Keywords: Failure, Check for Updates
User: SYSTEM
Computer: <computer name>
Description: Windows Update failed to check for updates with error 0x800b0001.
======================================

Cause:

This can be due to a version mismatch between the Windows update agent and the WSUS server. WSUS needs to be at version 3.2.7600.251 or later in order to properly communicate with clients at version 7.6.7600.256 or later.

Resolution:
Meanwhile to resolve this issue, one of the most workable troubleshooting steps listed as follows:

NOTE:
However please make sure that the issue that you try to resolve should have error 0x800b0001 and event ID 25 as shown above.
Troubleshooting steps:
1. Check windowsupdate.log in order to understand what is causing this issue.
2. If you find following entries:
“WARNING: Skipping scan, self-update check returned 0x800B0001”
“WARNING: WU client failed Searching for update with error 0x800b0001”
(To understand how to access and read the Windowsupdate.log file please refer to following link –
http://support.microsoft.com/kb/902093 )
Follow the steps:
3. Stop the Automatic Update service or run command: “net stop wuauserv”.
4. Open Regedit and browse to the following Registry Key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate.
5. Save a copy of this WindowsUpdate key (File / Export or Right-click / Export).
6. Delete the following registry values:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\PingID.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\AccountDo
mainSid.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId
7. Close Regedit.
8. Start the Automatic Update service or run command: “net start wuauserv”.
9. On client machine, force synchronization with the WSUS Server: “wuauclt /detectnow”.
10. Now check windows update and click “Check for new updates”.
11. If a message with green bar appears indicates that issue is resolved.
12. If a message with red bar appears indicates that issue is not resolved and proceed with
further troubleshooting.
13. In command prompt run the command: “netsh winhttp show proxy” – and check for
any proxy configuration. If proxy is not configured proceed as follows.
14. Stop WIN HTTP Proxy service and windows update service and registered important
DLLs required for the changes to take place.
net stop WinHttpAutoProxySvc
net stop wuauserv
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s.
15. In windows registry, for following Registry Key - take a backup: "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate."
16. Delete the following registry value.
"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId”
17. Run iisreset command in command prompt to restart all IIS related services and start windows update service.
18. On the client, do force synchronization with the WSUS Server by running command: “wuauclt /detectnow”.
19. After conducting the troubleshooting steps, we checked the event logs and found following success event on the client machine under Applications and Services Logs >Microsoft > Windows > WindowsUpdateClient >Operational:

===================================
Log Name: Microsoft-Windows-WindowsUpdateClient/Operational
Source: Microsoft-Windows-WindowsUpdateClient
Date: <date>
Event ID: 30
Task Category: Windows Update Agent
Level: Information
Keywords: Connection
User: SYSTEM
Computer: <computer name>
Description: Windows Update established connectivity.
===================================

Hence this issue is resolved. No further action is required.
20. If this event is not found proceed further with following steps:
21. Open "notepad"
22. Copy the following commands and then paste them into the opened Notepad window: net stop wuauserv net stop CryptSvc ren %windir%\system32\catroot2 catroot2.old ren %windir%\SoftwareDistribution sold.old net start CryptSvc net start wuauserv pause
23. We are renaming two files by this - catroot2 and SoftwareDistribution.
24. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop.
25. Return to the Desktop, right click the rename.bat file and choose "Run as administrator".
26. You will see a DOS-like window processing. Now try Windows Update to see if the issue has been resolved.
27. If your issue is not resolved again then apply following update on the WSUS server machine Please be sure apply this update to WSUS SERVER MACHINE

http://support.microsoft.com/kb/2734608

28. Apply this update. 29. You must restart the computer after you apply this update.
30. Start synchronization on WSUS
31. Wait for the synchronization to succeed.
32. On the affected client, open cmd.exe in elevated mode
33. Type the following commands. Make sure that you press Enter after you type each command: Net stop wuauserv Net start wuauserv
34. The issue would be resolved once and for all.

 Microsoft has released this update for Windows Server Update Services (WSUS) 3.0 Service Pack 2 (SP2)

 This update strengthens the WSUS communication channels.

 The Windows Update Agent (WUA) on computers that are managed by this WSUS server will be automatically upgraded as needed after you apply this update.

 WSUS must be in a known, good working state for this update to work. If WSUS is configured to synchronize updates from Microsoft Update, make sure that WSUS can synchronize updates. And, clients must be able to communicate with the WSUS server.

 This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012.

Any improvements or feedback on above troubleshooting steps is surely welcome.
Thank You.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I installed WSUS on a Windows Server 2008 Standard OS a few days ago, and I did so for the most part by following the procedure in the Setup Wizard. In this procedure at the point when I select the website to create or use, it recommended using the existing IIS Default website, which I allowed. It is my understanding that this will result in making use of port 80. Although I do not have any intention of using this website for any other purpose than WSUS, I have found that there would be a conflict with another program in the use of port 80. Specifically, I would have a conflict with Windows Event Forwarding services, which I intend to have this same system running as the Collector for the Event Logs.

Because the Event Forwarding Services use port 80 (and this does not appear to be negotiable), I now would like to change the website I have configured for WSUS from the Wizard's recommended one to the alternate one making use of different ports. This configuration will be for minimal use in a Windows Workgroup setting, not in an AD domain environment. Hopefully, a change such as this should not entail too much duplication of effort. I would appreciate if someone can point out a link or other pointers on the best way to go about making these configuration changes. Thanks.

Hello everyone, I have an SBS 2011 server that the c:\ is 3TB and I cant install wsus.  getting the following error:

any solutions?

We have multiple WSUS servers across a highly geographically diverse network and I need to know if we can set up SCCM clients to talk to WSUS servers on a priority list for patching.

Here's an example:

Client is based at a network of 192.168.50.xx

They have a local WSUS server on the local network at 192.168.50.17 .  The client travels to another office that has a 192.168.32.xx network and cannot reach their original WSUS server.  Can we set up a priority list that states because the original WSUS server cannot be reached patches will then be downloaded via the internet, but only the approved patches that were published via SCCM configuration policy?

Thanks.

Hi all,

We would like to get SCSM 2012 SP1 update from WSUS, but we can't find it in the WSUS System Center list.

Any idea where is it hidden ?

Regards.

Unable to sync with upstream server... using 

Synchronize from Microsoft updates

Result: An http error occurred 

WebException: The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2fmicrosoftupdate%2fv6%2ferrorinformation.aspx%3ferror%3d15">here</a>.</h2>
</body></html>

--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

Please advise....

Hi All,

I have a fresh installation of W2K8 R2 x64. Since then i could not able to download any windows updates. i have read and follow the below thread discussion but still to problem is not resolve. can anyone please guide me how i can overcome this problem.

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/11c77493-7c8f-41ab-8ae2-8256a2cfc66f/

Regards,

Waqas Hanif

Update Services

Microsoft Corporation

Version: 3.2.7600.226

This is my wsus version, I have windows 7and 8 clients in domain, I can only search the updates for IE 10 in wsus but can't find the installer from WSUS.

Any Ideas?

Jason

Jason

The week of April 9th 2013 - from what the email Update Status Summaries can tell me, my numbers have been "off" for my machines... and which machines need updates.

We are running WSUS 3.2 - and running it not as apart of SCCM.  We are running Forefront protection on the computers - allowing the definitions to be updated through our WSUS servers. 

Before the week of April 9th, I might have 30 or so machines - out of the 2000+ that use our WSUS server, in need of updates on any given day - except for updates release days. Since that week, the majority of my machines always report that they need updates - usually a Forefront definition.

Crazy thing is... it ISN'T the LATEST definition they "need".  It is usually the next one back or an older one. 

For instance... right now... they are complaining about needing 1.151.433, and 1.151.444 and 1.151.459 are more recent. And this will change in a couple of hours when we get a new definition.

I have made no changes to my server.

Ideas?  Anyone?  Please?

I have an SBS 2008 server that I am unable to install WSUS 3.0 SP2 (KB972455) on. I have tried through WU as well as downloading the update and running it. I let it run for hours and nothing happened past the screen where it basically says it's starting the update and that "it may take some time".

It ran for about an hour from WU before I killed it and rebooted. I then downloaded the update to install manually. I let that run for 4 hours and finally killed it.

I don't see anything in the event logs that would tell me why this won't install. Anyone have any suggestions or ideas?

Jonathan

Jonathan

Hi guys

We played a lot with all the GPO for wsus but we still stuck on the notification message for each user to reboot to finish the installation. The only one thing we want is applying patches without interaction of the users and we know that each user will shut down the computer every evening anyway. After wsus installed the patches automatically, it should do just nothing until the user will shutdown the computer at the evening.

So our current policy is like that:

So how can we get rid of the notification to restart the computer? Another option would be to set the "Automatic updates" on 3 and the shutdown menue for each user would change to "install updates and shut down" but I read a lot it won't work for non administrators. Is it true?

Thx for any suggestions.

Hi,

all of our workstations are running IE8. this is a choice we had to make because our applicationdevelopers are a bit slow :)

So I created a computer group called IE9. This group has all the IE9 updates and the IE9 installation. This group holds 2 test computers.

The group called workstation holds al the workstations (DUH ;)) This group has all the IE8 fixes.

However all the workstations are complaining they need IE9. How can I get rid of this message? I understand they want IE9, but it is my choice to give them all IE8. With this issue I am always at 99% patches in stead of 100%

I am getting a WSUS installation failure for Windows server 2008 SP2 x64, showing an error 0x80070643. Doing some research from the WSUS update log, i found that a .net 3.5 Sp1 update had failed months ago. I used the MS .net cleanup utility to uninstall the .net 3.5 framework. I then rebooted the server, reinstalled the .net 3.5 sucessfully, updated it with all the security updates it needed, then retried the Sp2 install, with the same result. i have included the last part of the WSUS update log for review. Anyone have any ideas?

#############
2010-03-29 15:33:55:722  560 18cc AU ## START ##  AU: Install updates
2010-03-29 15:33:55:722  560 18cc AU #########
2010-03-29 15:33:55:722  560 18cc AU   # Initiating manual install
2010-03-29 15:33:55:722  560 18cc AU   # Approved updates = 1
2010-03-29 15:33:55:722  560 18cc AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {04D1B104-3AAF-4E1A-B0BA-C37242933E69}]
2010-03-29 15:33:55:722  560 1a74 Agent *************
2010-03-29 15:33:55:722  560 1a74 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
2010-03-29 15:33:55:722  560 1a74 Agent *********
2010-03-29 15:33:55:722  560 1a74 Agent   * Updates to install = 1
2010-03-29 15:33:55:722  560 1a74 Agent   *   Title = Windows Server 2008 Service Pack 2 Standalone x64-based Systems (KB948465) - English, French, German, Japanese, Spanish
2010-03-29 15:33:55:722  560 1a74 Agent   *   UpdateId = {56E25ED4-8D4A-4E8C-81D8-CC71983C58E0}.103
2010-03-29 15:33:55:722  560 1a74 Agent   *     Bundles 1 updates:
2010-03-29 15:33:55:722  560 18cc AU Getting featured update notifications.  fIncludeDismissed = true
2010-03-29 15:33:55:722  560 1a74 Agent   *       {45FF69C1-3C27-4A10-A617-BFB8C15C93A4}.103
2010-03-29 15:33:55:722  560 18cc AU No featured updates available.
2010-03-29 15:33:55:722  560 1a74 Agent WARNING: LoadLibrary failed for srclient.dll with hr:8007007e
2010-03-29 15:33:55:753  560 1a74 DnldMgr Preparing update for install, updateId = {45FF69C1-3C27-4A10-A617-BFB8C15C93A4}.103.
2010-03-29 15:33:59:310 5556 fb0 Misc ===========  Logging initialized (build: 7.4.7600.226, tz: -0700)  ===========
2010-03-29 15:33:59:310 5556 fb0 Misc   = Process: C:\Windows\system32\wuauclt.exe
2010-03-29 15:33:59:310 5556 fb0 Misc   = Module: C:\Windows\system32\wuaueng.dll
2010-03-29 15:33:59:310 5556 fb0 Handler :::::::::::::
2010-03-29 15:33:59:310 5556 fb0 Handler :: START ::  Handler: Command Line Install
2010-03-29 15:33:59:310 5556 fb0 Handler :::::::::
2010-03-29 15:33:59:310 5556 fb0 Handler   : Updates to install = 1
2010-03-29 15:33:59:981  560 1acc Report REPORT EVENT: {297262EA-C5FF-4830-9177-63C96EA103E7} 2010-03-29 15:33:54:973-0700 1 189 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions:  - Windows Server 2008 Service Pack 2 Standalone x64-based Systems (KB948465) - English, French, German, Japanese, Spanish
2010-03-29 15:33:59:981  560 1acc Report CWERReporter finishing event handling. (00000000)
2010-03-29 15:34:03:428 5556 fb0 Handler   : WARNING: Command line install completed. Return code = 0x800f0a05, Result = Failed, Reboot required = false
2010-03-29 15:34:03:428 5556 fb0 Handler   : WARNING: Exit code = 0x8024200B
2010-03-29 15:34:03:428  560 18c8 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {56E25ED4-8D4A-4E8C-81D8-CC71983C58E0}]
2010-03-29 15:34:03:428 5556 fb0 Handler :::::::::
2010-03-29 15:34:03:428  560 18c8 AU   # WARNING: Install failed, error = 0x80070643 / 0x800F0A05
2010-03-29 15:34:03:428 5556 fb0 Handler ::  END  ::  Handler: Command Line Install
2010-03-29 15:34:03:428 5556 fb0 Handler :::::::::::::