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

Windows 2016 with WSUS

November 19, 2016, 12:30 am
$
0
0

Clients can't connect to it.

Now, here's what happened.  My previous WSUS (win2k12r2) crashed hard.  No recovery.  So I figured now would probably be a good time to do a clean win2k16 install.  I had hardware glitches but all seemed cool once I got it working.  Clients could get back to their shared drives easily (in fact, most didn't even notice a difference).

But, the update history in WSUS was gone.  This is a new WSUS instance.  It installed just fine.  Set the products and classifications just fine.  Even ran the windows update on the local box.  It connected, downloaded and installed updates.

Now the clients, all win10 pro, can't connect.  I've gone through the powershell commands of stopping the service, deleting the C:\Windows\SoftwareDistribution\* -recuse -recursive (or something like that).  And they still can't connect.

Now, I can fire up the remote admin console for WSUS and connect to WSUS just fine to administrate it. 

The last time it failed, I went into the C:\Windows\SoftwareDistribution and found a file called ReportingEvents.log  Here are the contents:

{94510F55-9758-46BD-A40C-2B1B5706D2EC} 2016-11-19 01:08:02:119-0700 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
{698B6305-B93E-49C0-B3A8-BF15BB66FEC0} 2016-11-19 01:13:15:768-0700 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.

Also of note, The clients are all set via GPO.  It worked until the fresh install of WSUS on the fresh box.

The Windows Update Service startup is Manual (Trigger Start) and is currently started.

↧
Search

WSUS - Windows 2008 Standard and Enterprise servers will not check in to WSUS console

November 27, 2016, 2:51 pm
$
0
0

WSUS - Windows 2008 Standard and Enterprise servers will not check in to WSUS console - R2 servers checked in and downloaded WSUS updates properly

Last check in date couple of days ago

Error code in windows update log:

Warning: failed to filter search results, error = 0X8024000B


↧
↧

WSUS 2016 use on port 80

November 22, 2016, 1:40 am
$
0
0

Hi,

du you have a hint for me. I tried to replace my existing WSUS (2012R2) with Server 2016. Everything was working until i changed to port 80 (wsusutil usecustomwebsite false). After that clients will show up in the console but they dont report.

I also set up a clean test environment with DC (a win 7, 8.1, 10 and server 2012 R2 Clients) but even there it does not work after i chage the port to 80.

does someone know a fix for this ?

thanks

↧

WSUS Server Can't connect

November 28, 2016, 12:35 am
$
0
0

Dear team,

Few months before I create a WSUS server in our environment and it was working fine . Today morning when I check the server I cant connect the server .When I try to connect the  server using server name and port number 8530, it showing error like SQL is not working.But I check in service tab SQL server is running. In configuration time I am using select default SQL database.So I request that please help me. please provide your valuable advice.

↧

Changed settings under WSUS Console-options-Computers

November 15, 2016, 11:17 pm
$
0
0

Hello Guys,

We have WSUS server already deployed with computer settings "Use the update service console". In WSUS console, Under "All computers" options, there are all computers appearing which are domain joined which is OK.

Week ago we changed the settings from "Use the update service console" to option "Use group policy or registry settings". For this we also created OU for some specific computers and pushed GP to that OU only.

Now, when I look at "All computers", other then Group policy computers all other systems which were present previously are still there in WSUS console. I also have tried deleting computers which are not in that OU from WSUS console but those computers appears again.

Any solution?

Thanks

↧
↧

Windows 10 Anniversary Update (1607)

August 11, 2016, 6:39 am
$
0
0

Anyone can explain why Windows 10 1607 client can't download WSUS updates ?

WSUS is install on Windows Server 2012 R2 Server.

When a Windows 10 client detect a Windows 10 (1607 only) update on WSUS, client can't download every update ( Windows or other)

If there are only Office update everything works good.

↧

Using WSUS Powershell Module to find out Failed computers

November 28, 2016, 2:48 pm
$
0
0

I am trying to use WSUS Powershell module to find all servers that have failed status in WSUS for a specific Update Group. I see 26 servers in the console when I use that to check but when I use the PowerShell Module I get 187. I have tested this on multiple WSUS servers. They are 2012 R2 servers. This happens locally and with remote PowerShell access. Am I missing something?  here is the command I am using:

Get-WsusServer -Name contosowsus02 -PortNumber 8530|Get-WsusComputer -ComputerTargetGroups Kanary  -IncludedInstallationStates Failed

↧

Lots of "Quality Previews" automatically approving

November 16, 2016, 10:58 pm
$
0
0

My WSUS setup downloads a number of products/categories and approves them for install automatically.

This is intended.

But the last months there has been some "Quality Previews" which I understand is for tests. I am not interested in deploying these in our production setup.

How can I avoid automatically approval of these whithout changing the approval of all the other products/categories?

Regards, Lars.

↧
Search

Quite a few laptop in WSUS say 'Not reported yet'

November 28, 2016, 11:35 am
$
0
0

Hello,

I'm trying to make sure our Windows 2012R2 WSUS server has all our PC's and laptops listed under my OU groups in the Computers section of the WSUS manager.  It seems they are all in there, however many say 'Not reported yet'.  These are mainly new Windows 10 PC/laptops. At least show as Windows 10 devices now as I updated the server as before they said Vista.

There devices have bene on the network for a couple of weeks now and should of checked in, what is the issue do you think?

on previous OS's I could look in the c:\windows\Windowsupdae.log file for a clue, but that is gone on Windows 10.

Thanks

↧
↧

Windows update issue (KB3045313)

November 24, 2016, 8:22 am
$
0
0

Hi all,

I'm experiencing an issue when I try to install KB3045313. The server (OS Windows Server 2008 Standard SP2 Build 6002)  has this SQL server version installation : Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)

After the installation, the log content is below reported:

------------------------------------------------------------------------

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: SQLSERVER2008. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068052374
  Exit facility code:            1212
  Exit error code:               1642
  Exit message:                  The patch installer has failed to update the following instance: SQLSERVER2008. To determine the reason for failure, review the log files.
  Start time:                    2016-11-24 16:32:11
  End time:                      2016-11-24 16:39:53
  Requested action:              Patch
Instance SQLSERVER2008 overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068052374
  Exit facility code:            1212
  Exit error code:               1642
  Exit message:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Start time:                    2016-11-24 16:36:53
  End time:                      2016-11-24 16:39:48
  Requested action:              Patch
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20161124_163055\SQLSERVER2008\SqlWriter_Cpu64_1.log
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4042.0
Machine Properties:
  Machine name:                  MDAD2-LJ
  Machine processor count:       4
  OS version:                    Windows Server 2008
  OS service pack:               Service Pack 2
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No
Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  Sql Server 2008 R2   SQLSERVER2008        MSSQL10_50.SQLSERVER2008       Database Engine Services                 1033                 Express Edition      10.52.4000.0    No       
Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       2
  KBArticle:                     KB3045313
  KBArticleHyperlink:            http://support.microsoft.com/?kbid=3045313
  PatchType:                     GDR
  AssociatedHotfixBuild:         4339
  Platform:                      x64
  PatchLevel:                    10.52.4042.0
  ProductVersion:                10.52.4000.0
  GDRReservedRange:              10.50.1610.0:10.50.1700.0;10.50.2500.0:10.50.2699.0;10.50.4001.0:10.50.4250.0
  PackageName:                   SQLServer2008R2-KB3045313-x64.exe
  Installation location:         c:\059c6da1195fa72d1037d3da892c\x64\setup\
Updated product edition:
  Instance             Edition            
  SQLSERVER2008        EXPRESS            
User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  False
  CLUSTERPASSIVE:                False
  CONFIGURATIONFILE:            
  ENU:                           True
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  PASSPHRASE:                    *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  UIMODE:                        Normal
  X86:                           False
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20161124_163055\SystemConfigurationCheck_Report.htm
  

------------------------------------------------------------------------------------------------------------------------

Below the content of C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20161124_163055\SQLSERVER2008\SqlWriter_Cpu64_1.log file:

------------------------------------------------------------------------------------------------------------------------

=== Verbose logging started: 11/24/2016  16:39:16  Build type: SHIP UNICODE 4.05.6002.00  Calling process: c:\059c6da1195fa72d1037d3da892c\x64\setup100.exe ===
MSI (c) (F0:08) [16:39:16:368]: Resetting cached policy values
MSI (c) (F0:08) [16:39:16:368]: Machine policy value 'Debug' is 0
MSI (c) (F0:08) [16:39:16:368]: ******* RunEngine:
           ******* Product: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (F0:08) [16:39:16:368]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (F0:08) [16:39:16:368]: Grabbed execution mutex.
MSI (c) (F0:08) [16:39:16:368]: Cloaking enabled.
MSI (c) (F0:08) [16:39:16:368]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (F0:08) [16:39:16:368]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (78:B8) [16:39:16:384]: Running installation inside multi-package transaction {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
MSI (s) (78:B8) [16:39:16:384]: Grabbed execution mutex.
MSI (s) (78:D0) [16:39:16:399]: Resetting cached policy values
MSI (s) (78:D0) [16:39:16:399]: Machine policy value 'Debug' is 0
MSI (s) (78:D0) [16:39:16:399]: ******* RunEngine:
           ******* Product: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (78:D0) [16:39:16:399]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (78:D0) [16:39:16:399]: SRSetRestorePoint skipped for this transaction.
MSI (s) (78:D0) [16:39:16:399]: End dialog not enabled
MSI (s) (78:D0) [16:39:16:399]: Original package ==> c:\Windows\Installer\6a8b90.msi
MSI (s) (78:D0) [16:39:16:399]: Package we're running from ==> c:\Windows\Installer\6a8b90.msi
MSI (s) (78:D0) [16:39:16:415]: APPCOMPAT: looking for appcompat database entry with ProductCode '{288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}'.
MSI (s) (78:D0) [16:39:16:415]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (78:D0) [16:39:16:415]: MSCOREE not loaded loading copy from system32
MSI (s) (78:D0) [16:39:16:431]: File will have security applied from OpCode.
MSI (s) (78:D0) [16:39:16:431]: Original patch ==> c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp
MSI (s) (78:D0) [16:39:16:431]: Patch we're running from ==> c:\Windows\Installer\6ad19222.msp
MSI (s) (78:D0) [16:39:16:431]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp' against software restriction policy
MSI (s) (78:D0) [16:39:16:431]: SOFTWARE RESTRICTION POLICY: c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp has a digital signature
MSI (s) (78:D0) [16:39:46:508]: SOFTWARE RESTRICTION POLICY: c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (78:D0) [16:39:46:508]: SequencePatches starts. Product code: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}, Product version: 10.50.1600.1, Upgrade code: {E9031696-DD39-4C25-BAEB-425FF28279EA}, Product language 1033
MSI (s) (78:D0) [16:39:46:508]: PATCH SEQUENCER: verifying the applicability of QFE patch c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp against product code: {288D79EE-A2D1-42AF-9597-B0ADCC23A8ED}, product version: 10.50.1600.1, product language 1033 and upgrade code: {E9031696-DD39-4C25-BAEB-425FF28279EA}
MSI (s) (78:D0) [16:39:46:508]: PATCH SEQUENCER: QFE patch c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp is not applicable.
MSI (s) (78:D0) [16:39:46:508]: SequencePatches returns success.
MSI (s) (78:D0) [16:39:46:508]: Final Patch Application Order:
MSI (s) (78:D0) [16:39:46:508]: Other Patches:
MSI (s) (78:D0) [16:39:46:508]: Unknown\Absent: {8B9F68F5-8191-4F48-B6C5-4A98858642AF} - c:\059c6da1195fa72d1037d3da892c\1033_ENU_LP\x64\setup\x64\SqlWriter.msp
MSI (s) (78:D0) [16:39:46:508]: Product: Microsoft SQL Server VSS Writer - Update '{8B9F68F5-8191-4F48-B6C5-4A98858642AF}' could not be installed. Error code 1642. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20161124_163055\SQLSERVER2008\SqlWriter_Cpu64_1.log.
MSI (s) (78:D0) [16:39:46:508]: Windows Installer installed an update. Product Name: Microsoft SQL Server VSS Writer. Product Version: 10.50.1600.1. Product Language: 1033. Update Name: {8B9F68F5-8191-4F48-B6C5-4A98858642AF}. Installation success or error status: 1642.
MSI (s) (78:D0) [16:39:46:508]: Note: 1: 1708
MSI (s) (78:D0) [16:39:46:508]: Product: Microsoft SQL Server VSS Writer -- Installation failed.
MSI (s) (78:D0) [16:39:46:508]: Windows Installer installed the product. Product Name: Microsoft SQL Server VSS Writer. Product Version: 10.50.1600.1. Product Language: 1033. Installation success or error status: 1642.
MSI (s) (78:D0) [16:39:46:523]: Attempting to delete file c:\Windows\Installer\6ad19222.msp
MSI (s) (78:D0) [16:39:46:523]: MainEngineThread is returning 1642
MSI (s) (78:B8) [16:39:46:523]: No System Restore sequence number for this installation.
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
c:\Windows\Installer\6a8b90.msi
MSI (s) (78:B8) [16:39:46:523]: User policy value 'DisableRollback' is 0
MSI (s) (78:B8) [16:39:46:523]: Machine policy value 'DisableRollback' is 0
MSI (s) (78:B8) [16:39:46:523]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (78:B8) [16:39:46:523]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (78:B8) [16:39:46:523]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (78:B8) [16:39:46:523]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (78:B8) [16:39:46:523]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (78:B8) [16:39:46:523]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (78:B8) [16:39:46:523]: Restoring environment variables
MSI (c) (F0:08) [16:39:46:523]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (F0:08) [16:39:46:523]: MainEngineThread is returning 1642
=== Verbose logging stopped: 11/24/2016  16:39:46 ===

-------------------------------------------------------------------------------------------------------------------------------------------------------

Can you help me to fix the issue please ?

↧

Windows 10 Anniversary Update (1607) - Not Applicable

August 22, 2016, 8:01 am
$
0
0

*** Asked to move this from the Windows 10 Forum,  Re-Posted here ***

We have Windows 10 Enterprise 1511 deployed to several machines in our organization for production testing with some users.   On August 16th I see that the 1607 Anniversary Update hit my WSUS server.   (e.g.  "Feature update to Windows 10 Enterprise, version 1607, en-us")

Environmental Notes:

  1. WSUS is running on Windows 2012 R2
  2. Patched WSUS to allow ESDs to installed and manual settings have been performed per KB3159706
  3. Patched WSUS with KB3095113
  4. All other patches were found and able to install on my Windows 10 1511 machines
  5. Tried deleting all updates from WSUS and re-syncing / downloading.
  6. Reset the Windows 10 1511 machines windows update client.   (e.g.  Delete SoftwareDistribution folder)

Unfortunately the all the versions of the anniversary upgrades are showing as Not Applicable to my machines.   Is there something I am doing wrong?   I don't want to have to manually update all of these machines.

Eric S.

↧

Datastore.edb file and Network Traffic

November 28, 2016, 9:52 pm
$
0
0

hey all, 

we are a global company with over 400 remote site with absolute rubbish WAN connection, im talking 1-2Mbps to sites with 10 clients.

we use 1E Nomad to manage all software deployments and Patching and that's working great.

the only issue i have is the datastore.edb file, it is causing network congestion on richter scale.

if i was to add an extra product or 2 right now that will cripple the business and i cant find a product out there that can manage WSUS traffic.

it there a way i can manage that file??

much appreciated.

↧

WSUS Cleanup wizard keeps crashing/timing out, result: Reset Server Node

November 22, 2016, 5:21 am
$
0
0

Hi all,

Everytime I try to run the cleanup wizard WSUS crashes and I need to press Reset Server Node to get it up again.

The server  is a replica server. I tried everything, I am on the newest version as far as I know. I also ran the WsusDBMaintenance script multiple times and I tried to run the wizard from powershell by a script; but that also timed out/crashes WSUS. The wizard seems to crash on these two catagories:

- Unused updates

- Expired updates

When i run it for the other catagories it runs fine and actually finishes the process.

I am on version 3.2.7600.274. OS is Server 2008 R2. I hope someone can come up with a solution...

Best regards,

Dylan


↧
↧

Domain admin seeing "Managed by your systems administrator"

November 28, 2016, 5:58 am
$
0
0

We have a new domain admin doing manual updates from WSUS after patch Tuesday and when he goes to the Windows Update gui on server 2012 R2 he sees 

You receive updates: Managed by your systems administrator

There is no option for Check for Updates or Install updates. Oddly, this is only on member servers. He is able to update Domain Controllers. The GPO settings on the servers and domain conrtrollers are identical.

Windows Components/Windows Update
PolicySettingComment


Enabled
Configure automatic updating:3 - Auto download and notify for install
The following settings are only required and applicable if 4 is selected.
Install during automatic maintenance 
Scheduled install day: 1 - Every Sunday
Scheduled install time:03:00
Install updates for other Microsoft products 
PolicySettingComment
Set the intranet update service for detecting updates:http://wsusserver:8530
Set the intranet statistics server:http://wsusserver:8530

I do see I can modify the NoWindowsUpdate from 1 to 0 in the User hive which fixes it but I really don't want to do this on 50+ servers.

What can cause this behavior? I don't see anything in gpresults /h that points me to the culprit. Any easy way to resolve?


↧

Error Code 80244010 in windows 7 Professional SP1

November 29, 2016, 3:28 am
$
0
0

I have this issue windows can not search for new updates with error 80244010 in nearly all the clients in my company all clients here are windows 7 SP1 Professional and the update agent is 

7.6.7600.320 and the server is windows server 2012 R2 and wsus version is 6.3.9600

 Please Guys any help will be much appreciated 

↧
Search

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.

↧

WSUS Error on Post Install after a re-installation - Problem Event Name:CLR20r3

February 9, 2015, 11:13 am
$
0
0

I installed WSUS with database on Windows 2012 but I was having a lot of problem with the client update so I decided to uninstall and deleted all files and database that the uninstaller process left behind. Now after the re-installation I cannot longer configure. The post installation configuration is failing and when I run the MMC it crash.

Problem signature:


  Problem Event Name: CLR20r3

  Problem Signature 01: mmc.exe

  Problem Signature 02: 6.2.9200.16496

  Problem Signature 03: 50ece2e8

  Problem Signature 04: System

Problem Signature 05: 4.0.30319.34239

  Problem Signature 06: 53e4531e

  Problem Signature 07: 400d

  Problem Signature 08: 3b8

  Problem Signature 09: System.ComponentModel.Win32

  OS Version: 6.2.9200.2.0.0.272.7

  Locale ID: 1033

  Additional Information 1: b376

  Additional Information 2: b376ba95bedbd518328ed0407772d20c

  Additional Information 3: 91a9

  Additional Information 4: 91a9ab76fe896e538a815116de500eff

On Application Event log shows:

Application: mmc.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ComponentModel.Win32Exception

Stack:

   at System.Diagnostics.Process.StartWithCreateProcess(System.Diagnostics.ProcessStartInfo)

   at Microsoft.UpdateServices.UI.SnapIn.Dialogs.PostInstallDialog.RunPostInstall(System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

****************************************************

And

Faulting application name: mmc.exe, version: 6.2.9200.16496, time stamp: 0x50ece2e8

Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8

Exception code: 0xe0434352

Fault offset: 0x0000000000047b8c

Faulting process id: 0x102c

Faulting application start time: 0x01d0449ba772f3ff

Faulting application path: C:\Windows\system32\mmc.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: ecd5ae80-b08e-11e4-9415-001ec9fd678e

Faulting package full name:

Faulting package-relative application ID:

*************************************************************

I have tried uninstalling, restarting the server and installing back but I'm getting the same result.

Thank you.

↧
↧

Windows\SoftwareDistribution Folder Cleanup Automation

August 22, 2011, 11:45 am
$
0
0

Hi -

I have a number of machines with a bloated Windows\SoftwareDistribution folder.  I usually address this by:

  1. Stopping the Automatic Updates service.
  2. Deleting the Windows\SoftwareDistribution folder.
  3. Restarting the Automatic Updates service.

I'm considering using a computer startup script to perform this task automatically.  Does anyone have a more elegant method of automating this task?

Thanks in advance for your input.

↧

WeakSha1ThirdPartyFlags and WeakSha1ThirdPartyAfterTime registry keys removed by latest windows updates KB3123479

November 18, 2016, 2:14 am
$
0
0

Hello,

The latest windows updates remove the following registry keys from the path below:

HKLM\Software\Microsoft\Cryptography\OID\Encoding Type 0\CertDllCreateCertificateChainEngine\Config\Default\

WeakSha1ThirdPartyFlags

WeakSha1ThirdPartyAfterTime

Nessus scans now show the device has a risk which it didn’t have before the latest updates.

I have confirmed on a test machine that the keys existed before the updates, but disappeared after the reboot and KB3123479 will not install on the machine as it says it is already installed.

Can someone please advise if this is expected behaviour or a problem with the latest batch of updates?

Many thanks
↧

Consuming too much virtual memory

November 29, 2016, 5:19 pm
$
0
0

I have a WSUS with WID installed.  I installed the SQL Management Studio.  I set the Min memory to 2 GB and the Max memory setting to 6GB.  The OS (Windows Server 2012R2) has 15GB physical memory installed and the paging file can use up to 24 GB.  The WSUS downstream to me cannot synchronize with me and my server is failing to synchronize with the upstream source.  The error message I receive is "out of memory" essentially.  The connection between my WSUS console the database keeps dropping frequently.  I look at Task Manager Details pane and the SQLserver process is using almost all the virtual memory on the box.  No matter what I do nothing seem to correct the problem.

How can I prevent the WID from consuming all the virtual memory?  Should I just give up and install SQL Express?

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