Downstream wsus server 3.2 not rollup to upstream wsus server 6.2 !!!

Hi,
We have recently upgraded upstream server to 6.2 (server 2012) but downstream server is on 3.2 (2008R2). The synchronization works well in downstream server,downstream server gets updates from upstream server and all the clients in downstream
server gets updates as well.
Problem is downstream server status in upstream server console says " not rolled up yet", through downstream server gets all updates from upstream server. Because of this, we are not getting reports from downstream server through upstream server.
The mode of downstream server also says" autonomous" which does not make sense as we have set up downstream server as replica.
we have followed up all instruction from Microsoft to upgrade upstream server. I am getting only one error below in the downstream server software distribution log . There is no error reported in upstream server IIS log.
UTC Error Wsusservice.3 Rollupagetn.wakeupworkierthereadproc Rollup failed. Error = The request failed with HTTP status 401 :unauthorized. at microsfot.updateservices.internal.reporting.rollup.rollupagetn.wakeupworkerthreadproc()
I have checked all IIS config in both servers, Anonymous Access
for the "WSUS Administration" virtual server has been enable.
Is that a version mismatch causing a problem?

Hi Lawrence,
Thanks for reply. I have already been to you your other post and already checked kb2734608, it's installed on the downstream server. The downstream WSUS version shows up 3.2.7600.256.
Both server getting a time from NTP servers, only 40 seconds time difference on downstream server which shouldn't be a big deal, I guess.
There is only one error below in the downstream server software distribution log .
UTC Error Wsusservice.3 Rollupagetn.wakeupworkerthereadproc Rollup failed. Error = The request failed with HTTP status 401 :unauthorized. at microsfot.updateservices.internal.reporting.rollup.rollupagent.wakeupworkerthreadproc()
The only error getting in event log for upstream server for port 8530 when I check wsus health.
Because port 8530 is blocked on downstream server and only port 80 and 443 is open up. I can see in the log that it's upstream server communicating with downstream server through port 80 successfully. No problem with this.
Problem is downstream server status in upstream server console says " not rolled up yet", through downstream
server gets all updates from upstream server. Because of this, we are not getting reports from downstream server through upstream server. The mode of downstream server also says" autonomous" which does not make sense as we have set up downstream server as
replica.

Similar Messages

Front End Server in pool not showing as possible registrar server

Hi All,
We have recently another server to our front end pool. At first we had only one server, and now we have added the second server to the pool.
However doing a get-csuserpoolinfo command we are getting these result
Get-CsUserPoolInfo sip:testuser2@domain
Identity                            :
testuser2@domain
PrimaryPoolFQDN                     : lyncpool.domain
BackupPoolFQDN                      :
UserServicesPoolFQDN                : lyncpool.domain
PrimaryPoolMachinesInPreferredOrder : {fe01.domain}
BackupPoolMachinesInPreferredOrder : {}
PrimaryPoolPrimaryRegistrar         : fe01.domain
PrimaryPoolBackupRegistrars         : {}
PrimaryPoolPrimaryUserService       : fe01.domain
PrimaryPoolBackupUserServices       : {}
BackupPoolPrimaryRegistrar          :
BackupPoolBackupRegistrars          : {}
BackupPoolPrimaryUserService        :
BackupPoolReplicaUserServices       : {}
Now we have fe02 deployed as well however this is not displayed for this testuser or any other user in our deployment. This is also causing the problem that if fe01 is not available the client will not automatically try to connect to fe02.
Thank you for your support!
Joseph

The Replica Instances for Routing Service does not add the second server fe01.domain, however for the other replicas the other server is added.
Get-CsPoolFabricState -PoolFqdn lyncpool.domain
Replica Instances for MCUFactory Service
    Address: fe01.domain - Primary: 6 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 6
Replica Instances for ConferenceDirectory Service
    Address: fe01.domain - Primary: 1 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 1
Replica Instances for Routing Service
    Address: fe01.domain - Primary: 7 Secondary: 0
        Local Groups: Primary: 7 Secondary: 0
        Remote Groups: Primary: 0 Secondary: 0
Replica Instances for LYSS Service
    Address: fe01.domain - Primary: 7 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 7
Global Service Count Summary:
Fqdn: fe01.domain - Primary: 21 Secondary: 0
Fqdn: fe02.domain - Primary: 0 Secondary: 14

SQL Server Analysis Services not showing in Services on Server on Central Admin

Hi All
We have a Sharepoint 2013 farm set up (2xApp, 2xWeb, 1xSQL) and we have a number of excel powerpivot workbooks deployed and refreshing.
This was all working fine, until recently when our Excel 2013 Tabular workbooks stopped refreshing manually. This had worked fine in the past, but now is giving the following error:
"An error occurred during an attempt to establish a connection to the external data source"
The first thing I wanted to check was that the "SQL Server Analysis Services" was started in Services on Server within Central Admin. However when i navigated to check this, I noticed that the service was no longer listed at all.
I checked the Analysis services for Powerpivot is running on the server and it is registered within Data Models on Excel services.
There was recently some Windows updates that were applied to the servers, but i'm pretty confident that the refresh was working after these, however i cant rule out 100%.
Hoping for any advice on what I can check/do here?
Thanks!

When i try to run that tool i actually get a strange error (we are running Enterprise Edition):
"PowerPivot for SharePoint 2013 Configuration is missing prerequisites: SharePoint 2013 Enterprise Edition is required.
For more information go to http://go.microsoft.com/fwlink/?LinkId=247828.
Please address the validation failures and try again."
Yes it looks like on the server hosting PowerPivot analysis server that a number of windows updates got applied. However
none look to be specifically about for SQL, and the 2 cumulative ones are for IE and Active X for Windows Server.

WSUS - "this computer has not reported status yet" Windows server 2003

I just did a successful installation of wsus 3.0 Sp2
I am able to see all the machines but the issue starts there
Each of the machine show this error " this computer has not reported status yet"
i have tried but hasnt manage to resolve this issue
kindly guide me on how i can resolve it
thx

2013-06-26 14:20:36:633
644 478
AU ## END ## AU: Search for updates [CallId = {4E48EF51-0D7C-458A-A575-9BA1B4799175}]
2013-06-26 14:20:36:633
644 478
AU #############
2013-06-26 14:20:36:634
644 478
AU Successfully wrote event for AU health state:0
2013-06-26 14:20:36:634
644 478
AU AU setting next detection timeout to 2013-06-26 16:20:36
2013-06-26 14:20:36:634
644 478
AU Setting AU scheduled install time to 2013-06-27 00:00:00
2013-06-26 14:20:36:634
644 478
AU Successfully wrote event for AU health state:0
2013-06-26 14:20:36:634
644 478
AU Successfully wrote event for AU health state:0
2013-06-26 14:20:41:581
644 1338
Report REPORT EVENT: {8DFBD635-02A8-4773-9DF8-80880752189A}
2013-06-26 14:20:36:577+0300 1
148 101
{D67661EB-2423-451D-BF5D-13199E37DF28}
1 800b0001
SelfUpdate Failure
Software Synchronization Windows Update Client failed to detect with error 0x800b0001.
2013-06-26 14:20:41:621
644 1338
Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-06-26 14:20:41:621
644 1338
Report WER Report sent: 7.6.7600.256 0x800b0001 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2013-06-26 14:20:41:621
644 1338
Report CWERReporter finishing event handling. (00000000)
2013-06-26 14:22:41:605
644 1338
Report Uploading 1 events using cached cookie, reporting URL = http://NTKE01/ReportingWebService/ReportingWebService.asmx
2013-06-26 14:22:41:612
644 1338
Report Reporter successfully uploaded 1 events.
2013-06-26 15:25:02:219
644 13d0
AU Triggering AU detection through DetectNow API
2013-06-26 15:25:02:219
644 13d0
AU Triggering Online detection (non-interactive)
2013-06-26 15:25:02:220
644 718
AU #############
2013-06-26 15:25:02:220
644 718
AU ## START ## AU: Search for updates
2013-06-26 15:25:02:220
644 718
AU #########
2013-06-26 15:25:02:221
644 718
AU <<## SUBMITTED ## AU: Search for updates [CallId = {65FA8DBB-1567-45A0-8ECB-103EFAB1C0A3}]
2013-06-26 15:25:02:221
644 179c
Agent *************
2013-06-26 15:25:02:221
644 179c
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-06-26 15:25:02:221
644 179c
Agent *********
2013-06-26 15:25:02:221
644 179c
Agent * Online = Yes; Ignore download priority = No
2013-06-26 15:25:02:222
644 179c
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"
2013-06-26 15:25:02:222
644 179c
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-06-26 15:25:02:222
644 179c
Agent * Search Scope = {Machine}
2013-06-26 15:25:02:242
644 179c
Setup Checking for agent SelfUpdate
2013-06-26 15:25:02:242
644 179c
Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-06-26 15:25:06:522
644 179c
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-06-26 15:25:06:530
644 179c
Misc Microsoft signed: Yes
2013-06-26 15:25:06:533
644 179c
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-06-26 15:25:06:558
644 179c
Misc Microsoft signed: Yes
2013-06-26 15:25:08:643
644 179c
Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-06-26 15:25:08:647
644 179c
Misc Microsoft signed: Yes
2013-06-26 15:25:08:700
644 179c
Setup Determining whether a new setup handler needs to be downloaded
2013-06-26 15:25:08:700
644 179c
Setup SelfUpdate handler is not found. It will be downloaded
2013-06-26 15:25:08:700
644 179c
Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-06-26 15:25:09:376
644 179c
Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-06-26 15:25:09:376
644 179c
Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-06-26 15:25:09:388
644 179c
Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-06-26 15:25:09:388
644 179c
Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-06-26 15:25:09:406
644 179c
Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-06-26 15:25:09:406
644 179c
Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-06-26 15:25:09:466
644 179c
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-06-26 15:25:09:466
644 179c
PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://NTKE01/ClientWebService/client.asmx
2013-06-26 15:25:09:536
644 179c
PT WARNING: Cached cookie has expired or new PID is available
2013-06-26 15:25:09:536
644 179c
PT Initializing simple targeting cookie, clientId = 01f95362-b793-4a75-bc97-94e49f6b63aa, target group = , DNS name = pcke65.kenya
2013-06-26 15:25:09:536
644 179c
PT Server URL = http://NTKE01/SimpleAuthWebService/SimpleAuth.asmx
2013-06-26 15:25:17:456
644 179c
PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2013-06-26 15:25:17:456
644 179c
PT WARNING: SOAP Fault: 0x00012c
2013-06-26 15:25:17:457
644 179c
PT WARNING: faultstring:Fault occurred
2013-06-26 15:25:17:457
644 179c
PT WARNING: ErrorCode:ConfigChanged(2)
2013-06-26 15:25:17:457
644 179c
PT WARNING: Message:(null)
2013-06-26 15:25:17:457
644 179c
PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2013-06-26 15:25:17:457
644 179c
PT WARNING: ID:78fa31e8-8714-47b9-8ae3-182ecb2d9f74
2013-06-26 15:25:17:477
644 179c
PT WARNING: Cached cookie has expired or new PID is available
2013-06-26 15:25:17:477
644 179c
PT Initializing simple targeting cookie, clientId = 01f95362-b793-4a75-bc97-94e49f6b63aa, target group = , DNS name = pcke65.kenya
2013-06-26 15:25:17:477
644 179c
PT Server URL = http://NTKE01/SimpleAuthWebService/SimpleAuth.asmx
2013-06-26 15:27:50:499
644 718
AU AU received policy change subscription event
2013-06-26 15:31:23:807
644 13d0
AU Triggering AU detection through DetectNow API
2013-06-26 15:31:23:807
644 13d0
AU Piggybacking on an AU detection already in progress
2013-06-26 15:31:27:317
644 13d0
AU Triggering AU detection through DetectNow API
2013-06-26 15:31:27:317
644 13d0
AU Piggybacking on an AU detection already in progress
2013-06-26 15:36:56:942
644 179c
PT WARNING: SyncUpdates failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
2013-06-26 15:36:56:942
644 179c
PT WARNING: PTError: 0x8024400a
2013-06-26 15:36:56:942
644 179c
PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400a
2013-06-26 15:36:56:942
644 179c
PT WARNING: Sync of Updates: 0x8024400a
2013-06-26 15:36:56:942
644 179c
PT WARNING: SyncServerUpdatesInternal failed: 0x8024400a
2013-06-26 15:36:56:942
644 179c
Agent * WARNING: Failed to synchronize, error = 0x8024400A
2013-06-26 15:36:56:943
644 179c
Agent * WARNING: Exit code = 0x8024400A
2013-06-26 15:36:56:943
644 179c
Agent *********
2013-06-26 15:36:56:943
644 179c
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-06-26 15:36:56:943
644 179c
Agent *************
2013-06-26 15:36:56:943
644 179c
Agent WARNING: WU client failed Searching for update with error 0x8024400a
2013-06-26 15:36:56:959
644 8dc
AU >>## RESUMED ## AU: Search for updates [CallId = {65FA8DBB-1567-45A0-8ECB-103EFAB1C0A3}]
2013-06-26 15:36:56:959
644 8dc
AU # WARNING: Search callback failed, result = 0x8024400A
2013-06-26 15:36:56:959
644 8dc
AU # WARNING: Failed to find updates with error code 8024400A
2013-06-26 15:36:56:959
644 8dc
AU #########
2013-06-26 15:36:56:959
644 8dc
AU ## END ## AU: Search for updates [CallId = {65FA8DBB-1567-45A0-8ECB-103EFAB1C0A3}]
2013-06-26 15:36:56:959
644 8dc
AU #############
2013-06-26 15:36:56:959
644 8dc
AU Successfully wrote event for AU health state:0
2013-06-26 15:36:56:959
644 8dc
AU AU setting next detection timeout to 2013-06-26 17:36:56
2013-06-26 15:36:56:959
644 8dc
AU Setting AU scheduled install time to 2013-06-27 00:00:00
2013-06-26 15:36:56:959
644 8dc
AU Successfully wrote event for AU health state:0
2013-06-26 15:36:56:960
644 8dc
AU Successfully wrote event for AU health state:0
2013-06-26 15:37:01:943
644 179c
Report REPORT EVENT: {48D1738E-F97A-45A4-8AB5-ECBE8FBDDF8F}
2013-06-26 15:36:56:943+0300 1
148 101
{00000000-0000-0000-0000-000000000000}
0 8024400a
AutomaticUpdates Failure
Software Synchronization Windows Update Client failed to detect with error 0x8024400a.
2013-06-26 15:37:01:950
644 179c
Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-06-26 15:37:01:950
644 179c
Report WER Report sent: 7.6.7600.256 0x8024400a 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2013-06-26 15:37:01:951
644 179c
Report CWERReporter finishing event handling. (00000000)
2013-06-26 15:39:01:979
644 179c
PT WARNING: Cached cookie has expired or new PID is available
2013-06-26 15:39:01:979
644 179c
PT Initializing simple targeting cookie, clientId = 01f95362-b793-4a75-bc97-94e49f6b63aa, target group = , DNS name = pcke65.kenya
2013-06-26 15:39:01:979
644 179c
PT Server URL = http://NTKE01/SimpleAuthWebService/SimpleAuth.asmx
2013-06-26 15:39:02:302
644 179c
PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2013-06-26 15:39:02:302
644 179c
PT WARNING: SOAP Fault: 0x00012c
2013-06-26 15:39:02:302
644 179c
PT WARNING: faultstring:Fault occurred
2013-06-26 15:39:02:302
644 179c
PT WARNING: ErrorCode:ConfigChanged(2)
2013-06-26 15:39:02:302
644 179c
PT WARNING: Message:(null)
2013-06-26 15:39:02:302
644 179c
PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2013-06-26 15:39:02:302
644 179c
PT WARNING: ID:38d9b059-92f2-4248-9a71-be1e33841fcb
2013-06-26 15:39:02:311
644 179c
PT WARNING: Cached cookie has expired or new PID is available
2013-06-26 15:39:02:311
644 179c
PT Initializing simple targeting cookie, clientId = 01f95362-b793-4a75-bc97-94e49f6b63aa, target group = , DNS name = pcke65.kenya
2013-06-26 15:39:02:311
644 179c
PT Server URL =
AS you can see the log file is bigggggg..
pls advise

Rmi and classloader: some server instances can not find the class on server

Hi:
I want to migrate my rmi applications from JDK 1.1 to JDK1.2.2. It exists in the following environments:
- there is one authentication server and many application servers, all have binded in the main method
- dynamic loading of the server stubs and interfaces is not used; they are local on the client.
- security manager is enabled only on the server site and the policy file is created.
- all server classes, stubs and interfaces are in the same directory on server site
- the registry and the server are started as follows:
unsetenv CLASSPATH
rmiregistry 1103 &
setenv CLASSPATH ~usr/serverDir:~oracle/jdbc/lib/classes12.zip
java -Djava.rmi.server.codebase=file://~usr/serverDir/
-Djava.rmi.server.hostname=myHost -Djava.security.manager myServer
After starting the client, the rmi client connects to the server and the authentication request comes back with a list of applications.
When the user chooses one of them, the rmi sends the request to thatapplication (e.g., OMSRmiServer_Stub). The application could not find the other class on the sever directory: (the authenication server can find the same class)
java.lang.NoClassDefFoundError: JOMPrepStatement
at java.lang.Class.getFields0(Native Method)
at java.lang.Class.getFields0(Compiled Code)
at java.lang.Class.getDeclaredFields(Compiled Code)
at java.io.ObjectStreamClass$1.run(Compiled Code)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessController.doPrivileged(Compiled Code)
at java.io.ObjectStreamClass.<init>(Compiled Code)
at java.io.ObjectStreamClass.lookupInternal(Compiled Code)
at java.io.ObjectStreamClass.lookup(Compiled Code)
at java.io.ObjectStreamClass.lookupInternal(Compiled Code)
at java.io.ObjectStreamClass.lookup(Compiled Code)
at java.io.ObjectStreamClass.lookupInternal(Compiled Code)
at java.io.ObjectStreamClass.lookup(Compiled Code)
at java.io.ObjectStreamClass.lookupInternal(Compiled Code)
at java.io.ObjectOutputStream.writeObject(Compiled Code)
at sun.rmi.server.UnicastRef.marshalValue(UnicastRef.java:256)
at sun.rmi.server.UnicastRef.invoke(Compiled Code)
at OMSRmiServer_Stub.executeStringSetSelect(Unknown Source)
at OMSDeviceRmiClient.getStatusLOV(OMSDeviceRmiClient.java:196)
at OMSRmiClient.getStatusLOV(OMSRmiClient.java:76)
at OMSDevicePane.listenToTree(Compiled Code)
at OMSDeviceContextPane.initComponents(OMSDeviceContextPane.java:107)
at OMSFrame.jomInit(Compiled Code)
at JOMCountFrame.init(JOMCountFrame.java:190)
at JOMCountFrame.run(JOMCountFrame.java:253)
at java.lang.Thread.run(Thread.java:485)
Any help is appreciated.
- Mahan.

in jdk1.2.2 no need classes12.zip in class path.
just set CLASSPATH=.;
that is enough for solving ur problem
bye
raghu

Windows Server 2012 Essentials not listed in EasyStartup 3.8.1d for TS140

Recently purchased a TS140 (70A4 001RUS). Came factory installed RAID 1 with Windows Server 2012 Essentials pre-installed. Needed to reinstall, however:
- Windows Server 2012 Essentials does not show up in EasyStartup 3.8.1c DVD that came with server
- Downloaded latest EasyStartup 3.8.1d and created bootable DVD and ran with same result
- "Windows Server 2012" is listed (but not Essentials). Running this installation, it does not recognize the Windows Server 2012 Essentials External Recovery DVD that came with server. Continually asks to insert "Windows Server 2012" disk.
- "Windows Small Business Server 2011 Essentials" is listed (but not 2012 Essentials). Running this installation, it does not recognize the Windows Server 2012 Essentials External Recovery DVD that came with server. Continually asks to insert "Windows Small Business Server 2011 Essentials" disk.
- Have booted using UEFI, Legacy and Auto with no difference
- Ran lastest Firmware Updater v1.8.1013 - no updates listed as required
- Have updated BIOS to latest 70A
- Server will also not boot directly from Windows Server 2012 Essentials External Recovery DVD (dvd is set 1st in boot order in bios)
- Windows Server 2012 Essentials External Recovery DVD is readable on other machines - can copy to bootable USB key and run regular Windows installation on server (this is current workaround)
- using the above workaround, drivers must be installed manually.
- EasyStartup 3.8.1d Readme specificly lists Windows Server 2012 Essentials as supported on the TS140 in UEFI and Legacy mode here
As mentioned, the above workaround can work. However, this server may not always be maintained by myself and I would prefer the supplied software to acutally work properly for ease of use by others in the future.

I have several TS140s running WSE 2012 R2. Like you said, the easystart does not recognize properly the WSE R2 os, so I just did the basic from disc or USB install after I configured the boot drives or RAID1 array.
The main reason to load the easy start is for drivers, however WSE found and recognized all the hardware in the unit.

WSUS patch status information not rolling up from Downstream to Upstream

We have a Windows 2008 R2 WSUS server running WSUS 3.2.7600.274
We have a Downstream replica also Windows 2008 R2 WSUS server running WSUS 3.2.7600.274
At some stage the Patch Needed status stopped rolling up from the downstream to the upstream server. ie the needed/installed/error counts can all be seen on the downstream replica however on the upstream they all show as 0 and the updates with no status
is the total number of patches available.
After days of troubleshooting. We re-installed WSUS on both the upstream and downstream and let the agents report in again and the issue was resolved.
Less that 30 days later the issue has started occurring again. Needed counts are correct on the downstream replica however this is not replicating up to the upstream. New agents that report in show "no status" for all patches, and all agents
show 'no Status" for any new patches.
The downstream server has now been deleted from the upstreams "Downstream Servers" section, forcing all machines to be removed from the Upstream console and then re-sync the downstream again. Now all machines show no status for all patches.
The WSUS instances are at the same version.
The time is within 1 minute of each other on downstream and upstream.
the rollup reporting is enabled on the upstream.
Currently we have the support teams using the downstream for reporting and approving patches on the upstream. Not ideal.

Thanks for the reply Michael,
The SoftwareDistribution.log file on the downstream replica has the below quite regularly:
2015-04-08 21:37:30.215 UTC Warning w3wp.5 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=0c03abf0-abb8-4ca3-ad3b-d61960b7922e, ErrorCode=ConfigChanged, Message=, Client=d2acf1c9-c820-428c-8634-44c2e69272e6
2015-04-08 21:37:48.575 UTC Warning w3wp.6 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=e4110e63-2358-447c-b003-4596b60abee1, ErrorCode=ConfigChanged, Message=, Client=47e558c1-e57e-4948-829c-98eb99727321
2015-04-08 21:37:50.700 UTC Warning w3wp.6 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=434cd484-86dc-468a-a57a-e69cd9e869c2, ErrorCode=ConfigChanged, Message=, Client=6d4c52c5-0252-4260-b07c-15674cee68f3
2015-04-08 21:38:02.934 UTC Warning w3wp.7 SoapUtilities.CreateException ThrowException: actor = http://WSUSDOWNSTREAM:8530/ClientWebService/client.asmx, ID=423780bf-8957-4278-8af1-4520d241c683, ErrorCode=ConfigChanged, Message=, Client=6c3a8800-9261-487b-b79a-421f8d26cead

Enterprise Hotfix Rollup for Win7 and Server 2008 R2 via WSUS

I stumbled across the fact that Microsoft released a hotfix rollup for Win7 and Server 2008 R2 that contains 90 hotfixes
http://support.microsoft.com/kb/2775511/en-us
The articled I linked above talks about after installing 2775511 (the big hotfix rollup containing 90 hotfixes) it is also necessary to install three more hotfixes:
After this update is installed, you must install update 2732673 to fix a regression issue in the Rdbss.sys file
After this update is installed, you must install update 2728738 to fix a regression issue in the Profsvc.dll file
After this update is installed, you must install update 2878378 re-released on November 11, 2013 to fix a regression issue in the Advapi32.dll file
I have imported all four of these hotfixes into my WSUS server. Do I need to install 277551 first and then install the other three or can all four be approved and go out at once? I guess I am hung up on the language of "After this update is installed
.... ". I want to put all 4 of these on our Win7 machines as well as my 40+ WinServer 2008 R2 machines

I read somewhere that over half of the updates included in Win7 SP1 and WinServer 2008 R2 SP1 were originally released as hotfixes. This means Microsoft made the decision that a large number of hotfixes would benefit every user of these two OSs
I think your conclusion is flawed. The only thing that you can draw from the presented statistic, is that Microsoft determined that a significant percentage of updates originally released as hotfixes warranted the additional investment in regression testing
to subsequently release those hotfixes as updates.
The fact that they bundled these 90 hotfixes together leads me to the same conclusion.
In fact, exactly the opposite conclusion applies: What you have in this package is all the rest of the stuff that didn't make that cut. What you have in this package are still NOT-regression tested hotfixes, they've just been bundled up for easy deployment
(and note that three of them got further broken in the process of bundling), causing yet three more hotfixes to have to be released.
In fact I read the MS Team Blog about this big hotfix release and they say the same thing, all users of these OSs would benefit from the installation of this hotfix rollup, not just a subset of users.
I suspect there are a notable number of patch administrators and systems administrators who would disagree with that self-serving promotion. If, in fact, it's true that "all users" would benefit, then the product team should have invested the effort in properly
regression testing those hotfixes, and releasing them as REAL updates. They did not; ergo the *actual* value is less than claimed.
Of course the bugaboo here is the fact that three other individual hotfixes need to be installed after the big hotfix rollup is installed.
Exactly! (And those are just the attempted fixes that broke something. Who knows how many other "fixes" may still result in newly discovered "broken stuff" that was never broken in the first place.)
The second part of this question should revolve around an itemized review of the hotfixes contained in this rollup with one simple question asked for each:
Have we actually *experienced* the issue addressed by this hotfix.
Where hotfixes are concerned one very simple but important rule applies:
If it ain't broken, don't try to fix it!
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS 3.0 SP2 on Server 2008 R2 not working (no console or other access)

Hi,
In a brand new network with all 2008 R2 servers I setup WSUS. Initially I could not install the role from the Roles tool in Windows and had to install it from a downloaded file from Microsoft (which I later read is due to 2008 R2).
This ran fine for about 2 weeks, I had all the clients and workstations in groups, approving updates and installing them.. all tickety boo and then one day the console wont connect and I have not been able to get back into WSUS to do anything. I tried removing
and re-installing WSUS (both keeping the local database and then deleting it the second time) but nothing helps. My event log reports the following every 6 hours:
Event ID 13042 - Self-update is not working
Event ID 12002 - The reporting web service is not working
Event ID 12012 - The API Remoting Web Service is not working
Event ID 12032 - The Server Synchronization Web Service is not working
Event ID 12022 - The Client Web Service is not working
Event ID 12042 - The SimpleAuth Web Service is not working
Event ID 12052 - The DSS Authentication Web Service is not working
Some extra points based on what I have read:
The server DOES have .net 4.0 installed
WSUS has been removed and re-installed
All servers are 2008 R2
The server also runs Remote Desktop Services.. but aside from this is just a file and print server
Because this server (and the whole network) are brand new, standard practice is to run WSUS against the Microsoft update site and install all critical and optional updates and patches and etc..
While it was working, I can't recall installing anything that may have broken it, however typically Windows patches do not cause problems on our machines, so I do not pay too close attention to what gets installed.. Perhaps one of these updates broke WSUS?
Can anyone offer some suggestions for how to troubleshoot this and try get things moving again?
Thanks!

Hi,
> then one day the console wont connect and I have not been able to get back into WSUS to do anything.
Any error message when you launch WSUS console?
You mentioned you have Kaspersky Endpoint Security software installed on WSUS server, have you configured antivirus software to exclude WSUS content directory?
If you cannot access the WSUS console and a timeout error message appears, the CPU of the WSUS server may be at, or very close to, maximum utilization, which causes the database software to time out. If the database software times out, the WSUS console cannot
be displayed.
One way of inadvertently overtaxing your WSUS server is to have antivirus software monitor the WSUS content directory. During synchronization, the antivirus software can overload the CPU.
Please ignore WSUS content in your antivirus software and check the result.
For more information please refer to following MS articles:
Issues with the WSUS 3.0 SP2 Administration Console
http://technet.microsoft.com/en-us/library/dd939877(v=WS.10).aspx
The DSS Authentication Web Service is not working.
http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c901eb7b-7c20-4fb8-87dd-93f128ec8703
WSUS web services not working
http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/5b443a1c-01eb-4b73-ad06-03700032bec2
Lawrence
TechNet Community Support

Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

Hi,
The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
Below are the patches.
MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
all the 2008 server updates are set and marked to download.
Please help me out on fixing this.

So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

WSUS Windows 7 Client not connecting with WSUS SERVER 2012 R2 Error " 80072ee2"

Hi ,
I Have the Non- AD WSUS server 2012 R2 as WSUS server, and widnows 7 ent sp1 as WSUS Client , the server and client are in teh same ip range and able to ping both server from client and client from server, and both are in teh
same time zone(EST), But im getting the "80072ee2" when ever i tried to get the updates from client
Please help me on this
Thanks
Balaji K

Record the system time of the Windows 7 client.
Reboot the Windows 7 client.
Run this command from a command prompt: wuauclt /resetauthorization /detectnow.
Wait =30= minutes.
Post the entries from the WindowsUpdate.log starting at the time recorded in Step #1.
I have noted the time at 12:06 am and reboot the machine. and at 12:27 i have Run this command from a
command prompt: wuauclt /resetauthorization /detectnow. and taken the the logs from 11 am to 1 pm
2015-02-03 12:15:26:002
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:15:26:002
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:15:26:002
956 f84
PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2015-02-03 12:15:26:002
956 f84
PT + Caller provided credentials = No
2015-02-03 12:15:26:002
956 f84
PT + Impersonate flags = 0
2015-02-03 12:15:26:002
956 f84
PT + Possible authorization schemes used =
2015-02-03 12:15:26:002
956 f84
PT WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2015-02-03 12:15:26:002
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:15:26:002
956 f84
PT WARNING: GetConfig_WithRecovery failed: 0x80072ee2
2015-02-03 12:15:26:002
956 f84
PT WARNING: RefreshConfig failed: 0x80072ee2
2015-02-03 12:15:26:002
956 f84
PT WARNING: RefreshPTState failed: 0x80072ee2
2015-02-03 12:15:26:002
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:15:26:002
956 f84
Report WARNING: Reporter failed to upload events with hr = 80072ee2.
2015-02-03 12:27:05:651
956 ca8
AU Triggering AU detection through DetectNow API
2015-02-03 12:27:05:651
956 ca8
AU Triggering Online detection (non-interactive)
2015-02-03 12:27:05:652
956 930
AU #############
2015-02-03 12:27:05:652
956 930
AU ## START ## AU: Search for updates
2015-02-03 12:27:05:652
956 930
AU #########
2015-02-03 12:27:05:654
956 930
AU <<## SUBMITTED ## AU: Search for updates [CallId = {710EE50A-0397-4DC8-B33B-B97410B73C00}]
2015-02-03 12:27:05:654
956 f84
Agent *************
2015-02-03 12:27:05:654
956 f84
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-02-03 12:27:05:654
956 f84
Agent *********
2015-02-03 12:27:05:654
956 f84
Agent * Online = Yes; Ignore download priority = No
2015-02-03 12:27:05:654
956 f84
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"
2015-02-03 12:27:05:654
956 f84
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-02-03 12:27:05:654
956 f84
Agent * Search Scope = {Machine}
2015-02-03 12:27:05:678
956 f84
Setup Checking for agent SelfUpdate
2015-02-03 12:27:05:678
956 f84
Setup Client version: Core: 7.5.7601.17514 Aux: 7.5.7601.17514
2015-02-03 12:27:29:233
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:27:29:233
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:27:29:233
956 f84
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://135.155.61.172:8530/selfupdate/wuident.cab>. error 0x80072ee2
2015-02-03 12:27:29:234
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2015-02-03 12:27:29:234
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2015-02-03 12:27:29:234
956 f84
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2015-02-03 12:27:52:795
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:27:52:795
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:27:52:795
956 f84
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://135.155.61.172:8530/selfupdate/wuident.cab>. error 0x80072ee2
2015-02-03 12:27:52:796
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2015-02-03 12:27:52:796
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2015-02-03 12:27:52:796
956 f84
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2015-02-03 12:28:16:363
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:28:16:363
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:28:16:364
956 f84
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://135.155.61.172:8530/selfupdate/wuident.cab>. error 0x80072ee2
2015-02-03 12:28:16:364
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2015-02-03 12:28:16:364
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2015-02-03 12:28:16:364
956 f84
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2015-02-03 12:28:39:920
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:28:39:920
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:28:39:920
956 f84
Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://135.155.61.172:8530/selfupdate/wuident.cab>. error 0x80072ee2
2015-02-03 12:28:39:921
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2015-02-03 12:28:39:921
956 f84
Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2015-02-03 12:28:39:921
956 f84
Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2015-02-03 12:28:39:921
956 f84
Misc WARNING: DownloadFileInternal failed for http://135.155.61.172:8530/selfupdate/wuident.cab: error 0x80072ee2
2015-02-03 12:28:39:921
956 f84
Setup WARNING: SelfUpdate check failed to download package information, error = 0x80072EE2
2015-02-03 12:28:39:921
956 f84
Setup FATAL: SelfUpdate check failed, err = 0x80072EE2
2015-02-03 12:28:39:922
956 f84
Agent * WARNING: Skipping scan, self-update check returned 0x80072EE2
2015-02-03 12:28:39:923
956 f84
Agent * WARNING: Exit code = 0x80072EE2
2015-02-03 12:28:39:923
956 f84
Agent *********
2015-02-03 12:28:39:923
956 f84
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2015-02-03 12:28:39:923
956 f84
Agent *************
2015-02-03 12:28:39:923
956 f84
Agent WARNING: WU client failed Searching for update with error 0x80072ee2
2015-02-03 12:28:39:924
956 fec
AU >>## RESUMED ## AU: Search for updates [CallId = {710EE50A-0397-4DC8-B33B-B97410B73C00}]
2015-02-03 12:28:39:924
956 fec
AU # WARNING: Search callback failed, result = 0x80072EE2
2015-02-03 12:28:39:924
956 fec
AU # WARNING: Failed to find updates with error code 80072EE2
2015-02-03 12:28:39:924
956 fec
AU #########
2015-02-03 12:28:39:924
956 fec
AU ## END ## AU: Search for updates [CallId = {710EE50A-0397-4DC8-B33B-B97410B73C00}]
2015-02-03 12:28:39:924
956 fec
AU #############
2015-02-03 12:28:39:925
956 fec
AU Successfully wrote event for AU health state:0
2015-02-03 12:28:39:925
956 fec
AU AU setting next detection timeout to 2015-02-03 21:23:35
2015-02-03 12:28:39:926
956 fec
AU Successfully wrote event for AU health state:0
2015-02-03 12:28:39:928
956 fec
AU Successfully wrote event for AU health state:0
2015-02-03 12:29:03:495
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:29:03:495
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:29:03:496
956 f84
PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2015-02-03 12:29:03:496
956 f84
PT + Caller provided credentials = No
2015-02-03 12:29:03:496
956 f84
PT + Impersonate flags = 0
2015-02-03 12:29:03:496
956 f84
PT + Possible authorization schemes used =
2015-02-03 12:29:03:496
956 f84
PT WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2015-02-03 12:29:03:496
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:29:03:496
956 f84
PT WARNING: GetConfig_WithRecovery failed: 0x80072ee2
2015-02-03 12:29:03:496
956 f84
PT WARNING: RefreshConfig failed: 0x80072ee2
2015-02-03 12:29:03:496
956 f84
PT WARNING: RefreshPTState failed: 0x80072ee2
2015-02-03 12:29:03:496
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:29:03:496
956 f84
Report WARNING: Reporter failed to upload events with hr = 80072ee2.
2015-02-03 12:29:03:496
956 f84
Report REPORT EVENT: {B6636CDB-B0BF-4CDE-BEB3-D49C1CEC258F}
2015-02-03 12:28:39:921-0800 1
148 101
{D67661EB-2423-451D-BF5D-13199E37DF28}
1 80072ee2
SelfUpdate Failure
Software Synchronization Windows Update Client failed to detect with error 0x80072ee2.
2015-02-03 12:29:03:510
956 f84
Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2015-02-03 12:29:03:510
956 f84
Report WER Report sent: 7.5.7601.17514 0x80072ee2 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2015-02-03 12:29:03:510
956 f84
Report CWERReporter finishing event handling. (00000000)
2015-02-03 12:29:27:075
956 f84
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:29:27:075
956 f84
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:29:27:075
956 f84
PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2015-02-03 12:29:27:075
956 f84
PT + Caller provided credentials = No
2015-02-03 12:29:27:075
956 f84
PT + Impersonate flags = 0
2015-02-03 12:29:27:075
956 f84
PT + Possible authorization schemes used =
2015-02-03 12:29:27:075
956 f84
PT WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2015-02-03 12:29:27:075
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:29:27:076
956 f84
PT WARNING: GetConfig_WithRecovery failed: 0x80072ee2
2015-02-03 12:29:27:076
956 f84
PT WARNING: RefreshConfig failed: 0x80072ee2
2015-02-03 12:29:27:076
956 f84
PT WARNING: RefreshPTState failed: 0x80072ee2
2015-02-03 12:29:27:076
956 f84
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:29:27:076
956 f84
Report WARNING: Reporter failed to upload events with hr = 80072ee2.
2015-02-03 12:53:05:793
956 930
AU AU received policy change subscription event
2015-02-03 12:58:26:707
956 8fc
Misc WARNING: Send failed with hr = 80072ee2.
2015-02-03 12:58:26:707
956 8fc
Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-02-03 12:58:26:708
956 8fc
PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2015-02-03 12:58:26:708
956 8fc
PT + Caller provided credentials = No
2015-02-03 12:58:26:708
956 8fc
PT + Impersonate flags = 0
2015-02-03 12:58:26:708
956 8fc
PT + Possible authorization schemes used =
2015-02-03 12:58:26:708
956 8fc
PT WARNING: GetConfig failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2015-02-03 12:58:26:708
956 8fc
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:58:26:708
956 8fc
PT WARNING: GetConfig_WithRecovery failed: 0x80072ee2
2015-02-03 12:58:26:708
956 8fc
PT WARNING: RefreshConfig failed: 0x80072ee2
2015-02-03 12:58:26:708
956 8fc
PT WARNING: RefreshPTState failed: 0x80072ee2
2015-02-03 12:58:26:708
956 8fc
PT WARNING: PTError: 0x80072ee2
2015-02-03 12:58:26:708
956 8fc
Report WARNING: Reporter failed to upload events with hr = 80072ee2.

Will not download from upstream server

Hi, I wonder if anyone can help please. We have downstream server which is set to synch with an upstream server managed by a 3rd party organisation. We can connect and see new updates needed to be downloaded via our WSUS GUI, we can approve these updates
and then the download indicator just stays a 0%. When we dig around, and look at the BITS jobs they are all trying to download from the Microsoft update site (on the web), not the configured upstream server. All the settings have been checked our end and all
seem good. We have even bitten the bullet and removed the whole of our local WSUS (including DB), and re-installed and pointed back to the upstream WSUS server, but get the same response i.e. BITS tries to go off to the Microsoft Download site. Anyone had
this before please? Any help would be good. Before anyone asks, we are in a location where we do not have Internet access for a number of reasons, but the upstream server does. Thanks very much.
Phil

We have downstream server which is set to synch with an upstream server managed by a 3rd party organisation.
This is always problematic from a technology standpoint. It's also arguably a violation of the WSUS EULA, unless that "3rd party organization" has a Service Provider Licensing Agreement allowing them to provide WSUS services to other licensees.
We can connect and see new updates needed to be downloaded via our WSUS GUI, we can approve these updates and then the download indicator just stays a 0%. When we dig around, and look at the BITS jobs they are all trying to download from the Microsoft
update site (on the web), not the configured upstream server.
As Daniel JiSun notes, you hold the configuration option for this behavior. Reconfigure your WSUS server to download from the USS, not Microsoft. But you've said this is configured correctly, which leaves us with one other possibility: If the USS does not
maintain a local content store, then there's no way you can get files from the USS if it doesn't have them, and your server will be forced to download them from Microsoft. Have you checked with your provider to ensure they're providing the files?
Before anyone asks, we are in a location where we do not have Internet access for a number of reasons, but the upstream server does.
Hmmmm...
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Update Rollup 7 for Exchange Server 2010 Service Pack 3 (KB2961522)

This rollups will not install and has caused multiple issues on the Windows SBS 2011.
The issues are as follows:
All Exchange and related services were stopped and had to be manually restarted.
The update fails for multiple reasons, changes every time.
I am no longer able to perform ANY updates without some sort of error code.
All Domain client computers now report Security Status as Critical, Servers as not available.
DNS does not appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Running BPA shows no major issues
I can no longer run the WSUS server cleanup. I get a Connection Error and have to reset the node, but it soon fails again.
Shared folders may take quite a bit of time to open.
Any help would be greatly appreciated. I do have an open ticket with Microsoft and although this is rated critical I am not getting any resolution. The only thing that MS support managed to do was bring the server down for an additional day and corrupt my
EDB files so that they had to be rebuilt.

Hi,
à
All Exchange and related services were stopped and had to be manually restarted.
While the update was installed, it will automatically stop Exchange and IIS services. You may need to restart
manually.
àThe update fails
for multiple reasons, changes every time.
à
I am no longer able to perform ANY updates without some sort of error code.
Would you please let me know any of those
update-failed reasons? Meanwhile, please let me know some error code that you can get when can’t perform updates. Meanwhile, please refer to installation suggestions and tips in following article when install this update rollup.
Exchange
2010 SP3 Update Rollup 7 released and installation tips
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
àAll Domain client
computers now report Security Status as Critical, Servers as not available.
àDNS does not
appear to be properly, many internet requests from domain PC's stop with "Fix connection problems" error page.
Please check if ping the SBS server successfully from the problematic client computer via server name and ip
address. In the SBS 2011, can you access
internet successfully? In addition, please select a client computer as a test machine, re-join it to the SBS network, then check if Security Status still report as Critical. Please also run Fix my network wizard in SBS console. Any find?
Meanwhile, please refer to following article and check if can help you to
repair Windows Server Update Services.
Repair Windows Server Update Services
By the way, did you have a good backup for the server?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Upstream WSUS Server and Sync

Hello,
Environment : 1. Server 2008 R2 Main Upstream server, hosts update content locally, SQL DB on another system.
2. 2 - Server 2008 R2 downstream servers, host update and sql content locally.
We had our Main Upstream WSUS server crash after applying KB2734608-x64 on a Server 2008 R2 box. Our database resides on a different SQL server on the same domain. When we tried to launch the WSUS interface the mmc console
it would crash. ( MMC has detected an error in a snap in and will unload it. was the error). Looked at the logs and it seems like it could not connect to the database. Anyways after trying many fixes, i decided to re-install WSUS until it got to the point
where it would not allow me to re-install got errors in the log of " InstallWsus: MWUS installation failed ( error 0x80070643: fatal error during installation with other ones like CInstallDriver and CSetupDriver:.....blah blah). I was messing with the
back end database and accidentally deleted it, so i had to restore the latest backup from a month ago ( we typically back on a weekly basis with incrementals, but our backups where failing and we didn't know of this because of a complicated situation
with our client..anyways). My question is once i get the WSUS connected backup what can i expect from the downstream servers in terms of Synchronization? I am assuming initially we will have re approve all updates on the upstream server, before the downstream
server successfully sync? I know i have to recycle the WSUS application pool and reset the update content, anything else? Also any advice on installing that patch? We initially tried to install it because some clients were not reporting into the console properly.
( I know we are on a downward spiral here, any help is appreciated. Will probably end up rebuilding the VM from scratch re-installing WSUS )
Server 2008 - MCITP, Server 2012 - MCSA

Because you had previously attempted the installation of KB2734608 on the WSUS server, it's likely that the database schema has already been modified, making it impossible to connect a downlevel WSUS server to that database. It's unfortunate that you uninstalled
WSUS (probably not necessary and notably complicates the situation), but c'est la vie.
Of course, apparently all that is also irrelevant since you also trashed the back-end database and restored it, so now that database does not have the schema mods imposed by KB2734608.
So, once you get this new WSUS server installed to the restored database, the downstream servers (where I presume you have not yet installed KB2734608 since this update must be installed from the top down) will just keep on truckin'. The only updates you'll
need to approve are the ones that were approved since the last database backup (which hopefully was after you approved this month's Patch Tuesday updates, otherwise you'll likely have a fair amount of work to be done).
Successful synchronization is not a function of the state of the approvals on the upstream server, but if there are any updates NotApproved on the upstream server that were previously approved, a replica server will lose those approvals and client systems
won't get the update until it is (re)approved, the replica resynchronized, and the client performs another detection to (re)find that (new) approval.
I don't know where the "recycle the app pool and reset the update content" stuff is coming from. You're installing a new front-end WSUS server onto an existing database that's already functional. No other actions are required.
As regards successfully installing KB2734608, I suggest thoroughly reading the KB article for starters... TWICE!
First requirement of successfulling installing this update is having a healthy
WSUS server. Not sure why your particular installation failed (installation failures of KB2734608 are pretty rare, as opposed to those encountered by KB2720211), but they're almost always related to existing dysfunctions within the WSUS server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Multiple WSUS servers behaving as if the are a single server.

Hi
I’ve just setup two WSUS servers running on Server 2012 R2.
Server1 is the upstream server synching with Windows Update.
Server2 is the downstream server synching with Server1 and having the replica setting turned off.
Server1 is to download and save the updates locally. Server2 is to tell computers to download approved updates from Windows Update.
The servers aren’t set up for NLB.
Group Policies have been setup, based on location to determine whether a computer gets directed to Server1 or Server2.
Computers are successfully communicating with both servers.
The problem I’m having is that any configuration change I make on one server also applies to the other.
For Example: On Server2, when I change the Source to point to Server1, Server1 also changes
its Source to be Server1, thereby making Server1 to be a downstream server of itself. When I change Server1 to point back to Windows Update, Server2 also changes its Source back to Windows Update.
This behaviour occurs regardless of the setting I’m changing.
I looked over the forums and found something I thought could the problem (http://social.technet.microsoft.com/Forums/en-US/2fb00066-7c8a-4f45-9c68-a3b0f86ffaa4/not-able-to-download-updates-on-client-after-migration-win2012-to-win2012-r2?forum=winserverwsus).
I went through the steps suggested and found the WSUS ServerIDs on both servers were the same and so I changed the GUID on Server2. However, even
this change was replicated to Server1.
It’s as if the servers are behaving as if they’re the same server.
Any help or suggestions would be greatly appreciated.

I’ve just setup two WSUS servers running on Server 2012 R2.
Server1 is the upstream server synching with Windows Update.
Server2 is the downstream server synching with Server1 and having the replica setting turned off.
Proceeding on the presumption that the downstream server is configured as an
autonomous server. (Which is quite unusual these days, thus I make note of the presumption.)
Server1 is to download and save the updates locally. Server2 is to tell computers to download approved updates from Windows Update.
Quite a convoluted deployment strategy, and probably totally unnecessary. Certainly it's contributing to the problem. But continuing on....
Computers are successfully communicating with both servers.
The problem I’m having is that any configuration change I make on one server also applies to the other.
The ONLY way I know for this to happen at this scale with an autonomous downstream server is that you've configured BOTH servers to use the SAME database.
Might I suggest... all things considered above... that you go READ the
WSUS Deployment Guide, cover-to-cover, then come back and redesign your architecture and install ONE WSUS server from scratch.
One additional note. I do grasp your intent to use the downstream server as a no-CONTENT server... but the conventional methodology for this is with that server in the DMZ to serve VPN clients, and configured as a REPLICA server. I'm really curious what
purpose is being served by having both types of servers on the same LAN. (And I'm assuming they're on the same LAN since you were able to successfully configure the SAME database for both servers.)
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Downstream wsus server 3.2 not rollup to upstream wsus server 6.2 !!!

Similar Messages

Maybe you are looking for