soap Problem

I am having a problem that I cannot find a resolution on. I am getting the
exact error in my client logs most of the time (not every sync though) as the
one described here.
http://msmvps.com/blogs/athif/archiv...-0x00012c.aspx
My problem though is I do not have IIS 6.0 as I am running wsus30sp1 on a
Windows 2008 Sp2 box with IIS 7.0. My test clients seemed to be working but
the error has got me concerned before I start moving all production systems
over.
All test systems get the error, no cloned guids exist and all pass the
clientdiag utility. Any help would be greatly appreciated.

"Daniel V" <> wrote in message
news:326253DB-D1BB-4D13-BB2E-...
>I am having a problem that I cannot find a resolution on. I am getting the
> exact error in my client logs most of the time (not every sync though) as
> the
> one described here.
> http://msmvps.com/blogs/athif/archiv...-0x00012c.aspx
> My problem though is I do not have IIS 6.0 as I am running wsus30sp1 on a
> Windows 2008 Sp2 box with IIS 7.0.

THen your isue is not at all anything like the one described in that blog
post archive, sine that post was related to WSUS v2.

> My test clients seemed to be working but
> the error has got me concerned before I start moving all production
> systems
> over.
> All test systems get the error, no cloned guids exist and all pass the
> clientdiag utility. Any help would be greatly appreciated.

I would suggest posting the Client Diagnostic Tool output and and actual log
snippet showing the error in context, so we can evaluate your issue in a
contemporary mindset, rather than that of a three year old issue long since
resolved and eliminated from the product.

And, since this is a test system -- implying that it's a new/fresh
installation -- some background on the methodology used to setup your
Win2008/IIS7 system could also be helpful.





--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

I have also noticed in the change.log file on the WSUS server the following

2009-08-10 22:13:15.897 UTC Synchronization manually started
2009-08-10 22:13:18.632 UTC WSUS configuration has been changed
2009-08-10 22:13:23.008 UTC Downloading retried

It says "WSUS configuration has been changed" everytime the wsus server
performs a sync, even though no changes were made on the server settings.
Not sure if its related, but it matches the error in the client log about the
server-

SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error
code = 300, HTTP status code = 200

SOAP Fault: 0x00012c

faultstring:Fault occurred

ErrorCode:ConfigChanged(2)

"Daniel V" <> wrote in message
news:332F7921-A8B3-425D-938E-...
>I have also noticed in the change.log file on the WSUS server the following
>
> 2009-08-10 22:13:15.897 UTC Synchronization manually started
> 2009-08-10 22:13:18.632 UTC WSUS configuration has been changed
> 2009-08-10 22:13:23.008 UTC Downloading retried
>
> It says "WSUS configuration has been changed" everytime the wsus server
> performs a sync, even though no changes were made on the server settings.
> Not sure if its related, but it matches the error in the client log about
> the
> server-
>
> SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error
> code = 300, HTTP status code = 200
>
> SOAP Fault: 0x00012c
>
> faultstring:Fault occurred
>
> ErrorCode:ConfigChanged(2)
>
>


The client logs are totally unrelated and purely coincidental to the
change.log entries.

Unless you can associated a "WSUS configuration has changed" with every
manual synchronization, I'm inclined to think those entries are also
coincidental, and we should be looking to determine what *was* changed at
22:13:18 UTC.

The "Downloading retried" suggests that the server is having issues
obtaining metadata/content from microsoft.com. I'd suggest checking the
Application Event Log for additional details, as well as the status of the
BITS queue on the WSUS Server. (BITSADMIN /LIST /ALLUSERS /VERBOSE)

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Thank you for taking time out to assist me. The server is a new build on
windows 2008 sp2. I have enabled SSL for the client to server communication.
I did not setup wsus as a role, rather just enabled the IIS with the required
components based on the documentation from Microsoft. The only thing I
cannot get to work is putting in the remove custom error in the IIS config
that I have seen you recommend, it makes IIS unstartable, so I have not put
that in. The server is a replica of another server that does not use SSL. I
have broken the replication to see if the problem goes away and it doesnt.
The server uses a remote SQL on a 2008 instance that is on a SQL cluster.
(Nested triggers is on)

Here is the Client diag from one client
---------------------------------------------------------------------
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect in use

Checking Connection to WSUS/SUS Server
WUServer = https://pm2.mycompany.com
WUStatusServer = https://pm2.mycompany.com
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
------------------------------------------------------------------------------
Here is a windowsupdate.log file from a client
#############
2009-08-10 03:44:40:365 1220 dc4 AU ## START ## AU: Search for updates
2009-08-10 03:44:40:365 1220 dc4 AU #########
2009-08-10 03:44:40:365 1220 dc4 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {5894776D-FDA0-498A-AF1D-38E2F316F77D}]
2009-08-10 03:44:40:365 1220 b7c Agent *************
2009-08-10 03:44:40:365 1220 b7c Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-08-10 03:44:40:365 1220 b7c Agent *********
2009-08-10 03:44:40:365 1220 b7c Agent * Online = Yes; Ignore download
priority = No
2009-08-10 03:44:40:365 1220 b7c Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-08-10 03:44:40:365 1220 b7c Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-08-10 03:44:40:365 1220 b7c Agent * Search Scope = {Machine}
2009-08-10 03:44:40:365 1220 b7c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-08-10 03:44:40:396 1220 b7c Misc Microsoft signed: Yes
2009-08-10 03:44:40:505 1220 b7c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wuident.cab:
2009-08-10 03:44:40:521 1220 b7c Misc Microsoft signed: Yes
2009-08-10 03:44:40:599 1220 b7c Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.cab:
2009-08-10 03:44:40:615 1220 b7c Misc Microsoft signed: Yes
2009-08-10 03:44:40:615 1220 b7c Setup *********** Setup: Checking whether
self-update is required ***********
2009-08-10 03:44:40:615 1220 b7c Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wsus3setup.inf
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.784, required version
= 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.2.6001.784, required version
= 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.2.6001.784, required
version = 7.1.6001.65
2009-08-10 03:44:40:646 1220 b7c Setup * IsUpdateRequired = No
2009-08-10 03:44:43:021 1220 b7c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2009-08-10 03:44:43:021 1220 b7c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://pm2.mycompany.com/ClientWebService/client.asmx
2009-08-10 03:44:43:662 1220 b7c PT WARNING: Cached cookie has expired or
new PID is available
2009-08-10 03:44:43:662 1220 b7c PT Initializing simple targeting cookie,
clientId = a6cb26fb-ec8f-4256-815a-2e7cf7ca03e2, target group = , DNS name =
ird-sectest.mycompany.com
2009-08-10 03:44:43:662 1220 b7c PT Server URL =
https://pm2.mycompany.com/SimpleAuth...impleAuth.asmx
2009-08-10 03:44:44:099 1220 b7c PT WARNING: GetCookie failure, error =
0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
200
2009-08-10 03:44:44:099 1220 b7c PT WARNING: SOAP Fault: 0x00012c
2009-08-10 03:44:44:099 1220 b7c PT WARNING: faultstring:Fault occurred
2009-08-10 03:44:44:099 1220 b7c PT WARNING: ErrorCode:ConfigChanged(2)
2009-08-10 03:44:44:099 1220 b7c PT WARNING: Messagenull)
2009-08-10 03:44:44:099 1220 b7c PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2009-08-10 03:44:44:099 1220 b7c PT WARNING:
ID:4243fe68-cd28-456a-bb97-64deb272bfb2
2009-08-10 03:44:44:162 1220 b7c PT WARNING: Cached cookie has expired or
new PID is available
2009-08-10 03:44:44:162 1220 b7c PT Initializing simple targeting cookie,
clientId = a6cb26fb-ec8f-4256-815a-2e7cf7ca03e2, target group = , DNS name =
ird-sectest.mycompany.com
2009-08-10 03:44:44:162 1220 b7c PT Server URL =
https://pm2.mycompany.com/SimpleAuth...impleAuth.asmx
2009-08-10 03:44:48:537 1220 b7c PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
2009-08-10 03:44:48:537 1220 b7c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
https://pm2.mycompany.com/ClientWebService/client.asmx
2009-08-10 03:44:49:928 1220 b7c Agent * Found 0 updates and 48 categories
in search; evaluated appl. rules of 496 out of 689 deployed entities
2009-08-10 03:44:49:943 1220 b7c Agent *********
2009-08-10 03:44:49:959 1220 b7c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-08-10 03:44:49:959 1220 b7c Agent *************
2009-08-10 03:44:49:959 1220 700 AU >>## RESUMED ## AU: Search for updates
[CallId = {5894776D-FDA0-498A-AF1D-38E2F316F77D}]
2009-08-10 03:44:49:959 1220 700 AU # 0 updates detected
2009-08-10 03:44:49:990 1220 700 AU #########
2009-08-10 03:44:49:990 1220 700 AU ## END ## AU: Search for updates
[CallId = {5894776D-FDA0-498A-AF1D-38E2F316F77D}]
2009-08-10 03:44:49:990 1220 700 AU #############
2009-08-10 03:44:49:990 1220 700 AU AU setting next detection timeout to
2009-08-10 12:16:16
2009-08-10 03:44:49:990 1220 700 AU Setting AU scheduled install time to
2009-08-10 20:00:00
2009-08-10 03:44:54:943 1220 b7c Report REPORT EVENT:
{03E98FB6-5279-4BE0-9E4D-CB8C4E4962D5} 2009-08-10
03:44:49:943-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2009-08-10 03:44:54:943 1220 b7c Report REPORT EVENT:
{4E6654FD-B0AC-4BB5-BFC9-C743275BD0CB} 2009-08-10
03:44:49:943-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2009-08-10 03:50:00:246 1220 b7c Report Uploading 2 events using cached
cookie, reporting URL =
https://pm2.mycompany.com/ReportingW...ebService.asmx
2009-08-10 03:50:03:293 1220 b7c Report Reporter successfully uploaded 2
events.

------------------------------------------------
I have also noticed in the change.log file on the WSUS server the following

2009-08-10 22:13:15.897 UTC Synchronization manually started
2009-08-10 22:13:18.632 UTC WSUS configuration has been changed
2009-08-10 22:13:23.008 UTC Downloading retried

It says "WSUS configuration has been changed" everytime the wsus server
performs a sync, even though no changes were made on the server settings.
Not sure if its related, but it matches the error in the client log about
and makes me suspect it.

Daniel V wrote:

> I am having a problem that I cannot find a resolution on. I am getting the
> exact error in my client logs most of the time (not every sync though) as the
> one described here.
> http://msmvps.com/blogs/athif/archiv...-0x00012c.aspx
> My problem though is I do not have IIS 6.0 as I am running wsus30sp1 on a
> Windows 2008 Sp2 box with IIS 7.0. My test clients seemed to be working but
> the error has got me concerned before I start moving all production systems
> over.
> All test systems get the error, no cloned guids exist and all pass the
> clientdiag utility. Any help would be greatly appreciated.

I've seen this warning now and then and it doesn't seem to cause any actual
problems. However, I've never seen it happen this frequently, and I'm not sure
of the significance of that.

Harry.

"Daniel V" <> wrote in message
news:1B7505E6-E6D3-416F-913E-...


C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.784

Just a quick pass.. I'm on my wayout the door, I'll take a deepr look later
tonight.. but this build is interesting for the WUAgent...

the v7.2.6001.784 was a very short-lived build, ultimately superceded by
v7.2.6001.788.

For the sake of testing, could you please download the latest
WindowsUpdateAgent30...exe from microsoft.com, and update this client to the
'788' build?



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Daniel V" <> wrote in message
news:1B7505E6-E6D3-416F-913E-...

> I have enabled SSL for the client to server communication.

It would be better to *disable* SSL for client-to-server communications
until after you've established functional client-to-server communications on
a basic connection. Once that connection is working, then add SSL to the
mix. At that point, if something fails, you can be reasonably certain that
the SSL configuration is responsible. At this point, it's just one more
(unnecessary) possible cause to consider.

> I did not setup wsus as a role, rather just enabled the IIS with the
> required
> components based on the documentation from Microsoft. The only thing I
> cannot get to work is putting in the remove custom error in the IIS config
> that I have seen you recommend, it makes IIS unstartable, so I have not
> put
> that in.

This is not critical. The change just ensures that the CustomErrorModule is
*not* included in the package. Since there's no ADD directive in the XML,
it's not there anyway. The REMOVE directive is just to ensure that any
previous ADD actually does get undone.

> The server is a replica of another server that does not use SSL.

This could be useful information -- that it's a *replica* -- not that it
does, or does not, use SSL. (My recommendation to remove the SSL still
stands until we isolate the cause of the errors -- which, btw, at this point
has a strong probability of being caused specifically by the SSL
configuration!)

> The server uses a remote SQL on a 2008 instance that is on a SQL cluster.
> (Nested triggers is on)

Thank you.

> Here is the Client diag from one client

> Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS

> Here is a windowsupdate.log file from a client
> 2009-08-10 03:44:40:630 1220 b7c Setup Update NOT required for
> C:\WINDOWS\system32\cdm.dll: target version = 7.2.6001.784

It occurred to me after I wrote the previously reply (in a hurry), that
these two items may be from *different* clients (which would explain the
difference in WUAgent versions). It would be most useful if all diagnostics
came from the same system. And, as noted, for any clients which have the
v7.2.6001.784 client installed -- it would be recommended to find a way to
get them updated to the v7.2.6001.788 WUAgent -- which is the current
released version.

Aside from the question of the WUAgent version, and the resolution of the
0x802440dd/SOAP 0x12c errors, I also note that the client log posted
demonstrates a client that apparently does not have an assigned target
group, and thus is detecting =zero= approved updates for installation.

> 2009-08-10 03:44:44:162 1220 b7c PT Initializing simple targeting cookie,
> clientId = a6cb26fb-ec8f-4256-815a-2e7cf7ca03e2,
> target group = ,
> DNS name = ird-sectest.mycompany.com
>
> 2009-08-10 03:44:49:928 1220 b7c Agent * Found 0 updates and 48
> categories
> in search; evaluated appl. rules of 496 out of 689 deployed entities




--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Unless you can associated a "WSUS configuration has changed" with every
manual synchronization, I'm inclined to think those entries are also
coincidental, and we should be looking to determine what *was* changed at
22:13:18 UTC."

I do ge the WSUS configuration has changed everytime the server performs a
sync.

I disabled SSL and the errors persisted exactly as before. I did test all
machines though and they did get todays patches and reported in normally.
Just to better understand, when a replica machine checks in with its master
would it be normal to see "Configuration chage" ever time it syncs? I
currently have the replica sync every few hours and I am wondering if this is
normal if its due to the amount of times I sync to the master that I am
getting the error.