Quantcast
Channel: WSUS forum
Viewing all 12874 articles
Browse latest View live
↧

Forcing Windows 10 upgrade to try again

October 9, 2019, 2:07 am
$
0
0

Hi,

I'm pushing out the Windows 10 1903 upgrade to our systems using WSUS (with GPO), which mostly seems to work.  However, some systems fail to install the upgrade - some for known reasons such as incompatible software, whereas others just randomly seem to fail.

If I visit a failed computer, more often than not, there is a 'Fix Issues' button or 'Try Again' button or 'Install Now' button and if i click them the computer then successfully updates with no further work required.

How can I get the computers to try again without requiring me to physically them to click these buttons or having to instruct users to do that?  I don't really want to deadline the upgrade as I'm delivering it in batches.

Thanks

↧
Search

WSUS server error: connection error

October 9, 2019, 4:57 am
$
0
0

hello all

please i need some help , WSUS server has this problem and i cant figure out the issue .

RESET SERVER NODE

i tried to restart the services without any result. 

↧
↧

Windows 10 1903 upgrades fail at 40% during client install?

October 10, 2019, 2:56 am
$
0
0

Hi,

We are running a WSUS Server on Windows 2012 R2. So far we haven't had any trouble with it but are no faced with an issue whereby the 1903 upgrade for Windows 10 fails during install when it gets to 40%. (All assets are standard towers / laptops with Windows 10 Pro OEM installed)

The Server is fully patched up-to date and as far as I can tell does have the required files downloaded.

The local and server event log shows this error;

wsustest.msad.internal
Feature update to Windows 10 (consumer editions), version 1903, en-gb x64
Event reported at 10/10/2019 10:34:
Installation Failure: Windows failed to install the following update with 
error 0xc1900208: Feature update to Windows 10 (consumer editions), version 1903, en-gb x64

I've investigated this as the issue points to an application installed being incompatible with the upgrade. To test this I created a new asset, installed Windows 10 1809 Pro and attempted to update. The asset successfully installed ALL available updates relating to its current version and early without issue, the only failure being the 1903 upgrade. This asset had nothing but Windows 10 1809 installed.

Checking again and something I missed the first time was that the clients were also showing the error below which occurs just prior to the one above;

wsustest.DOMAIN.internal
Feature update to Windows 10 (consumer editions), version 1903, en-gb x64
Event reported at 10/10/2019 10:33:
(Unable to Find Resource:) ReportingEvent.Client.181; Parameters: Feature update to Windows 10 (consumer editions), version 1903, en-gb x64

I've deleted and re-approved the required packages multiple times to no avail. I also made sure the MIME type eds was added to IIS and repeated the process but still no luck.

I've really tried everything out there that I can think of but the upgrade will just not go through.

Currently my only option to upgrade 100 assets is to manually use the 1903 ISO to upgrade them one by one. Any help with this would be gratefully appreciated.

Thanks,

Delta

↧

Error 80072EE2 while updating server from WSUS

October 10, 2019, 4:49 am
$
0
0

Hi,

I have made an update of the machine and after restarting there is problem with further updates. While updating server (Windows Server 2012R2) from WSUS i get error 80072EE2. First updates has been made without a problem. Any other machine is updating correctly - only one is having issues.

Port 8530 is open, I have deleted SoftwareDistribution folder,  used dism to restorehealth, registered again dlls (there is info that msxml.dll and initpki.dll failed to load, but the same is on others server which are working just fine).

Updating from internet is not an option.

WSUS server is working on Windows Server 2012 R2, version: 6.3.9600.18838




↧

WSUS on Server 2016 crashing when attempting to load synchronization history or update list

October 11, 2019, 6:04 am
$
0
0

Greetings TechNet.  I'm new to WSUS and I'm implementing a new WSUS structure in our organization comprised of a main WSUS at our main office, and downstream servers at all branch offices.  All WSUS deployments are on new or relatively new servers running 2016 standard.  For the sake of this post, I'll refer to one server in particular.  This server consists of 32 Core 2.1 GHz Family 6, Model 55 processor and 48 GB RAM. 

This is a problem I'm having on all my new downstream WSUS servers.  When attempting to load the update list it has synchronized, it crashes.  When attempting to load the synchronization history, it crashes.  It just can't do it.  Rebooting the server makes no difference.  Here are some other things I've done:

In IIS, under Advanced Settings for the Application Pool:

  • Change shutdown time to 600 seconds
  • Change "Service Unavailable" Response to TCPLevel
  • Change Private Memory Limit (KB) to 0

I'm at a loss for what to try next.  Would anyone happen to have any new ideas I can try?  I would sincerely appreciate any assistance.  Thank you!

↧
↧

Error 80244010 on some WSUS clients

October 11, 2019, 12:18 am
↧

Script does not check RebootRequired registry key correctly

October 14, 2019, 1:31 am
$
0
0

Hi,

I wrote a small PowerShell script which checks the registry key on remote computers and lists the status if reboot required key exists or not.

The scripts run without any error. But the results are not correct. Although some computers (for example ComputerA and ComputerE) have this key in registry the script lists all computers in OK status.

Here is the script:

$Computers = Get-Content "C:\myFolder\Computer.txt"
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" 

foreach ($Computer in $Computers) {
$Exists = Test-Path -Path "\\$Computer\$RegPath"
if ($Exists -eq $false)
{
 Write-Host -fore Green "OK on $Computer"
}
else
{
 Write-Host -fore Red "Reboot is required on $Computer"
}
}

The results:

OK on ComputerA
OK on ComputerB
OK on ComputerC
OK on ComputerD
OK on ComputerE

What is wrong in the script?

Best regards

Birdal

↧

No any of clients show in WSUS console even a single computer

October 18, 2019, 1:34 am
$
0
0

Hi Experts,

As i have configured a WSUS server in my lab environment. There are 2 DCs and two exchange servers and some windows 10 client computer in my setup. All are virtual machines. 

All the required policies are configured properly and and intranet servers is also defined with port 8530.  i have checked on all clients, policies are reflecting properly and registry settings are also fine.

But no any client\ server machine is showing in WSUS console.

I've read multiple articles but all in vain.

please suggest me a solution

Thanks in advance.

↧
Search

Workstations updating not reporting status

October 18, 2019, 1:39 am
$
0
0

Hi,

I have WSUS problem - some of the worksations are not reporting status. Updates are downloaded and installed but status is not reported, and in reports those stations are visible as "No status". About 50 from 1500 is affected, some is not reporting from more than a half year. I have changed "Private memory limit" to 0, deleted all superseded updates. On workstations deleted Softwaredistribution folder, registered dlls again, used those commands:

REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
Reg Delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
Reg Delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientValidation /f
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v LastWaitTimeout /f
REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v DetectionstartTime /f
Reg Delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v NextDetectionTime /f

wuauclt.exe /resetauthorization
wuauclt.exe /detectnow
wuauclt.exe /reportnow

It resolved problem in couple of stations but most of them are still not reporting, and right now I'm without ideas what could cause this. WSUS is on Windows Server 2012R2 version: 6.3.9600.18838

Stations are mostly Windows 10 with some Widnows 7.


↧
↧

Synchronization failes when "Windows 10" product is selected

October 18, 2019, 4:09 am
$
0
0

Hello all,

We set up a new SCCM server with includes WSUS on the same server for software updates.
We start having sync errors in de SCCM log wsyncmgr.log:

Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=<FQDN of my SCCM/WSUS server> SITE=<SITECODE> PID=3304 TID=7840 GMTDATE=vr okt 18 10:15:17.631 2019 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

and errors in de WSUS SoftwareDitribution.log:

2019-10-18 07:59:01.746 UTCInfoWsusService.29CatalogSyncAgentCore.UpdateSyncResultAndGenerateReportingEventCatalogSyncThreadProcess: report subscription USS internal error

2019-10-18 07:59:01.756 UTCInfoWsusService.20CatalogSyncAgent.SetSubscriptionStateWithRetryFiring event SyncFailToStart...

2019-10-18 07:59:01.762 UTCInfoWsusService.20CatalogSyncAgent.UpdateServerHealthStatusBasedOnErrorServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running


After some testing we figured out that we only have the issue when the product "Windows 10" or Windows 10 in combination with the category "Updates" is selected. So it seems the issue is related with updates for Windows 10. All other categories work fine and all categories including updates work fine when "Windows 10" is not selected as a product to sync.

We can reproduce the issue by enabling Windows 10 again as a product to sync and we get the same error messages.
The old SCCM server can sync without any issues and there are no network or firewall related limitations to the Microsoft Update Catalog.

OS version of the SCCM/WSUS server is Server 2019 and is a new install. 

Hopefully that someone can help to solve this issue. 

Can someone explain why we have this issue and what we can do about it?

↧

2016 client server not reporing to 2019 WSUS server

October 18, 2019, 5:53 am
$
0
0

Hi All,

 I have newly build 2019 server and installed WSUS service. 2016 client server not reporting to 2019 wsus server.

Note: All the Sever running in aws Cloud

2016 version is : 1607 (OS Build - 14393.3274)

2019 Version : 1809 (Os Build - 17763.776)

 2019 WSUS version - 10.0.17763.1

I have added WSUS server ip in gpedit.msc and did gpupdate /force. after that changes are populated to regedit. I have tried below cmd but not working

net stop wuauserv
net start wuauserv
wuauclt.exe /resetauthorization /detectnow
wuauclt.exe /detectnow /reportnow
wuauclt.exe /updatenow
usoclient startscan
==================================

net stop bits
net stop wuauserv
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

================================================================

is there any KB need to install 2019 wsus server or 2016 client sever

kindly help me to solve this issue.

Thanks.
↧

WSUS can't download kb4022730: File cert verification failure

October 18, 2019, 7:04 am
$
0
0

I have WSUS v.6.3.9600.18838 working on Windows Server 2012 R2.

After each synchronization, errors appear in the program log when checking the certificate of the update file kb4022730. I looked through the log for a month and I see no other errors. Please help solve the problem.

Full text of errors:

10032 The server cannot download some updates.

364 Error downloading content file.
       Reason: File cert verification failure.
       Source file:  /c/msdownload/update/software/secu/2017/06/windows10.0-kb4022730-x86_749a5a7af3ac36a1ff014171f2b21eb38fc224f4.cab

       Destination file: C:\Program Files\Update Services\LogFiles\WSusTemp\749A5A7AF3AC36A1FF014171F2B21EB38FC224F4.cab

Content of SoftwareDistribution.log:

2019-10-18 10:49:14.198 UTCInfoWsusService.39ContentSyncAgent.WakeUpWorkerThreadProcContentSyncAgent found no more Jobs, going to Sleep for BITS Notifications
2019-10-18 10:49:25.328 UTCInfow3wp.97ThreadEntryTimerQueue.FireNextTimers
2019-10-18 10:49:25.329 UTCInfow3wp.97ServerImplementation.UpdateCacheDatabase change occured; check if we need to update cache.
2019-10-18 10:49:43.891 UTCInfoWsusService.39ContentSyncAgent.ProcessBITSNotificationQueueContentSyncAgent recieved Transferred Event for Item: 446bd91c-91a4-4c6b-8266-e429c3b3402a
2019-10-18 10:49:43.892 UTCInfoWsusService.39ContentSyncAgent.ContentSyncSPFireStateMachineEventContentSyncAgent firing Event: FileDownloaded for Item: 446bd91c-91a4-4c6b-8266-e429c3b3402a
2019-10-18 10:49:43.977 UTCInfoWsusService.39ContentSyncAgent.VerifyCRCfilelocalpath is C:\Program Files\Update Services\LogFiles\WSusTemp\F8CC3C3282C9D0EFF5C59AE004BD468D037A0B23.cab, additionalHash is F661FB69CA3508CD7A689BFDC98A3E70F8F0552AD3E824FAEC28FC918EB29414
2019-10-18 10:49:44.057 UTCInfoWsusService.39ContentSyncAgent.VerifyCRCcalculated sha1 hash is F8CC3C3282C9D0EFF5C59AE004BD468D037A0B23
2019-10-18 10:49:44.058 UTCInfoWsusService.39ContentSyncAgent.VerifyCRCmatched sha1 hash
2019-10-18 10:49:44.206 UTCInfoWsusService.39ContentSyncAgent.VerifyCRCcalculated sha2 sha256 hash is F661FB69CA3508CD7A689BFDC98A3E70F8F0552AD3E824FAEC28FC918EB29414
2019-10-18 10:49:44.420 UTCInfoWsusService.39CabUtilities.CheckCertificateSignatureFile cert verification failed for C:\Program Files\Update Services\LogFiles\WSusTemp\F8CC3C3282C9D0EFF5C59AE004BD468D037A0B23.cab with 2148204801
2019-10-18 10:49:44.425 UTCWarningWsusService.39ContentSyncAgent.ProcessBITSNotificationQueueInvalid file deleted: C:\Program Files\Update Services\LogFiles\WSusTemp\F8CC3C3282C9D0EFF5C59AE004BD468D037A0B23.cab
2019-10-18 10:49:44.426 UTCInfoWsusService.39ContentSyncAgent.ContentSyncSPFireStateMachineEventContentSyncAgent firing Event: FileVerificationFailed for Item: 446bd91c-91a4-4c6b-8266-e429c3b3402a

↧

Laptops and VMs failing to upgrade to 1903 via WSUS

October 18, 2019, 7:46 am
$
0
0

Hello.  I have a mix of physical laptops and VMs failing updates via WSUS.  I've looked through the log files but am having a hard time making any sense of them.  Would someone please take a look and tell me if anything stands out to you?  Thanks!

https://www.mediafire.com/file/55r2b1pbssiy9y0/setuperr.log/file

https://www.mediafire.com/file/t3rs6a3qgato4ih/setupact.log/file

↧
↧

Install WSUS console on Windows 10 computer

October 12, 2017, 9:19 am
$
0
0

I have setup WSUS on a Windows Server 2016 Standard system.  I has been up an running for 6 months.  My question is if I can install the management console for it on a Windows 10 desktop system on my desk to that I don't have to remote desktop into the server every time I want to check on the update rollout?  I did this years ago when I had used a Windows 2003 server and a Windows XP desktop computer but wasn't sure if it could still be done and if it is where to get the console installer to install it on a Windows 10 system.

Thanks,

Brent

↧

Windows Server 2016 Updating from Windows Server 2012 R2 WSUS Faling

October 18, 2019, 10:58 am
$
0
0

Hi Guys,

I am running a WSUS Server on Windows Server 2012 R2. I have a few Server 2012 Servers updating from fine without any issues. I have just deployed a new Windows Server 2016 Server into the Environment. I configured my new server to look for updates from the WSUS but it keeps failing to connect to update service. I decided as I didn't have the time to investigate the possibility of Firewall issues I would leave it to update directly from Windows Update. 

I have now managed to rule out Firewall issues, but the Windows Server 2016 Server continues to fail to connect to the WSUS Server. 

Has anyone else run into this issue? I have found a few posts on forums with links to KB's which are not applicable to my server as they are already installed (Server 2012 R2).

Any pointers would be excellent.

Regards,

TPark IT Technician

↧
Search

WSUS 3.0SP2 Content file download failed. Reason: File cert verification failure

June 18, 2019, 11:22 pm
$
0
0

Hi,

We have a problem wtih an Upstream WSUS 3.0SP2 on Windows server 2008 Enterprise SP2.

Since june 12, several Updates approved for Windows 7 or for Windows 8.1 or IE 11 are not downloaded by our Upstream.

On this Upstream, I have test a donwload of update with Interner Explorer and the same Proxy server and its OK.

Any suggestions please ? 

UPstream server version  : 3.2.7600.307 (hotfix KB2720211 + KB2828185 + KB4484071)

In SoftwareDistribution.log, an exemple of download failed :

2019-06-19 03:43:43.647 UTCInfoWsusService.22ContentSyncAgent.ProcessBITSNotificationQueueContentSyncAgent recieved Transferred Event for Item: d0777547-6cfb-4f12-aed1-91ec38d56e33
2019-06-19 03:43:43.647 UTCInfoWsusService.22ContentSyncAgent.ContentSyncSPFireStateMachineEventContentSyncAgent firing Event: FileDownloaded for Item: d0777547-6cfb-4f12-aed1-91ec38d56e33
2019-06-19 03:43:43.694 UTCErrorWsusService.22ContentSyncAgent.ProcessBITSNotificationQueueDownloaded file e:\DATA\WSUS\WsusContent\E3\A2CB0FBB26057B1C0815E92687C838E14B7A03E3.cab caught exception at VerifyFile: System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.VerifyCRC(String fileLocalPath, String additionalHash)
   at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.VerifyFile(String fileLocalPath, String additionalHash)
   at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.ProcessBITSNotificationQueue()

=== Pre-bind state information ===
LOG: User = NT AUTHORITY\NETWORK SERVICE
LOG: DisplayName = System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 (Fully-specified)
LOG: Appbase = file:///C:/Program Files/Update Services/Service/bin/
LOG: Initial PrivatePath = NULL
Calling assembly : Microsoft.UpdateServices.ContentSyncAgent, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Update Services\Service\bin\WsusService.exe.Config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
LOG: The same bind was seen before, and was failed with hr = 0x80070002.

   at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.ProcessBITSNotificationQueue()
   at Microsoft.UpdateServices.ServerSync.ContentSyncAgent.WakeUpWorkerThreadProc()
   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()
2019-06-19 03:43:43.694 UTCWarningWsusService.22ContentSyncAgent.ProcessBITSNotificationQueueInvalid file deleted: e:\DATA\WSUS\WsusContent\E3\A2CB0FBB26057B1C0815E92687C838E14B7A03E3.cab
2019-06-19 03:43:43.694 UTCInfoWsusService.22ContentSyncAgent.ContentSyncSPFireStateMachineEventContentSyncAgent firing Event: FileVerificationFailed for Item: d0777547-6cfb-4f12-aed1-91ec38d56e33
2019-06-19 03:43:43.694 UTCInfoWsusService.22EventLogEventReporter.ReportEventEventId=364,Type=Error,Category=Synchronization,Message=Content file download failed. Reason: File cert verification failure. Source File: /c/msdownload/update/software/updt/2019/06/windows8.1-kb4502567-x86_a2cb0fbb26057b1c0815e92687c838e14b7a03e3.cab Destination File: e:\DATA\WSUS\WsusContent\E3\A2CB0FBB26057B1C0815E92687C838E14B7A03E3.cab.
2019-06-19 03:43:43.710 UTCInfoWsusService.22ContentSyncAgent.WakeUpWorkerThreadProcContentSyncAgent found no more Jobs, thread exitting
2019-06-19 03:43:43.710 UTCInfoWsusService.22EventLogEventReporter.ReportEventEventId=363,Type=Information,Category=Synchronization,Message=Content synchronization succeeded.

↧

Windows 10 Pro Not Reporting to WSUS

October 7, 2019, 12:02 pm
$
0
0
I have WSUS on Windows 2016 in domain environment. All Windows 2016 and Windows 10 LTSB clients are reporting to WSUS server but Windows 10 Pro is not reporting to WSUS server. Is there any know issue with Windows 10 Pro?
↧
↧

Windows 8.1 and windows 10 client not report wsus server configured windows 2012 R2

October 19, 2019, 2:30 am
$
0
0
Windows 8.1 and windows 10 client not report wsus server configured  windows 2012 R2
↧

Locally Published Packages failing to download from WSUS 0x80d02002

July 24, 2018, 1:52 pm
$
0
0

I'm continually getting the "0x80d02002" error when attempting to download locally published packages from WSUS. All computer are running Windows 10, but some are on 1511, 1803, and everywhere in between. This started happening a few months ago, but not sure what, if anything changed to cause this to happen.

It appears that most other updates complete the download, but the rest of the updates eventually seem to fail due to the packages failing.

Server is WS 2012 R2 for reference. The packages are mostly small software like Adobe, Java, etc., all seem to time out and fail with this error.

The usual delete SoftwareDistribution and Catroot2 folders has not worked.

↧

Getting past WSUS Cleanup Wizard time out, removing unnecessary updates.

August 1, 2014, 8:10 am
$
0
0

Standard problem with WSUS Cleanup Wizard timing out without removing any unnecessary updates. SBS2K8. WSUS 3. 6000+ unnecessary updates awaiting approval. Huge database. Unresponsive SQL server. Lot of people have this problem:
http://social.technet.microsoft.com/Forums/en-US/9724778f-c1a0-4d24-82e4-8b2d054257d6/wsus-hangs-on-cleanup-wizard-for-unused-updates-then-disconnects-from-console?forum=winserverwsus

Drives are regularly defragged in the background. Not gonna shut down the server and have down time just to fix this.

Tried the reindexing script from
http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx
, (don't copy the command line, it has weird characters in it, just type it in manually.) and it completes but it didn't improve anything.

Found this:
http://wsus.codeplex.com/releases/view/17612
and it also times out.

Found this comment:
For anyone who is getting Timeout Expired with obsolete updates. I have a solution! Use server name : "
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
" to connect with SQL managment studio. Once connected manually run "
exec spGetObsoleteUpdatesToCleanup
". This will return a list of obsolete ID's. For each one run "
exec spDeleteUpdate @localUpdateID=000000
", where 000000 is the ID. For myself I found the first ID in the list took a full 37 minutes to delete and then after that I could run the cleanup through the GUI as per usual.

by jjdacl on Apr 23 at 12:55 PM 

Found that you actually need to do:
USE SUSDB
GO
exec spGetObsoleteUpdatesToCleanup

And to connect in the first place, I had to hit Options, and select named pipe from the middle pull down. 

First delete took 6 minutes and memory has spiked up to almost 15GB in use out of 16GB physical. But the WSUS console (Update Services) still shows the same number of old updates. Failure? I don't think so: I'm running the cleanup wizard again and so far it isn't timing out... It has run over night, and has made some progress; the bar has moved perhaps 5%. 

So... My take is that the SQL server causes this problem when there is to much data, because the indexes are poorly designed (not because the indexes need to be re-indexed) causing the first query to time out, which causes the cleanup to fail. Once you get past that first deletion, and have everything loaded into memory, the cleanup tool can stay connected long enough to delete each unneeded update.

Next step will be to find a command line method, such as:
http://wsus.codeplex.com/releases/view/17612
and put it into the task scheduler like Microsoft should have done at the beginning to keep this from getting out of hand.

P.S. Lawrence Garvin, please do NOT reply to this; I have no need of your arrogance.

↧
Viewing all 12874 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>