SBS2003 R2 not reporting to WSUS 2

I've posted this in the SBS newsgroup with no response, so trying my
luck here.

My SBS 2003 R2 server is not reporting itself to WSUS (v2) (installed on
same physical machine) as of 5 days ago. I'm unsure why this has
happened (all workstations are happily reporting).

I attempted a wuauclt.exe /detectnow on the SBS machine to no avail.

The latest error in windowsupdate.log shows:

2010-03-08 13:26:42 932 960 Report REPORT EVENT:
{A40095DE-0BFF-494C-AD01-947CA12A5415} 2010-03-08 13:26:37-0000 1
148 101 {00000000-0000-0000-0000-000000000000} 0 80070057
AutomaticUpdates Failure Software Synchronization Error: Agent failed
detecting with reason: 0x80070057

Any ideas? I've rebooted also to no avail. There are updates pending on
the server that I've scheduled for the weekend... but this is what I
always do. Nothing else has changed on the server and no updates were
installed on the day WSUS was last able to talk to the machine (03/03/2010).

I found this on google, (http://inetexplorer.mvps.org/answers/63.html),
not that it's much use to me at least... maybe to someone else? We don't
use a proxy by the way....

0x80070057 -2147024809
ERROR_INVALID_PARAMENTER - E_INVALIDARG

One or more arguments are not valid error - Invalid proxy server name
was specified in the user’s IE settings and hence
WinhttpSetProxySettings call fails with E_INVALIDARG error. BITS puts
the job in TRANSIENT_ERROR with the same error code. For ex, if the
proxy server is set to http://foo/bar/proxy.pac, this error will be
seen. This error is also seen when credentials are supplied such that
scheme is not NTLM/Negotiate, but username/password is NULL, since that
is not valid (WinhttpSetCredentials fails with E_INVALIDARG. BITS 1.5
puts the job into ERROR state with BG_E_INVALID_RESPONSE in the above 2
cases, because of error code mapping E_INVALIDARG is always mapped to
(BG_E_INVALID_SERVER_RESPONSE)

"James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
news:%...

> I've posted this in the SBS newsgroup with no response, so trying my luck
> here.

Perhaps because you're asking about an ancient (and heavily customized)
version of WSUS that nobody wants to remember?


> My SBS 2003 R2 server is not reporting itself to WSUS (v2) (installed on
> same physical machine) as of 5 days ago. I'm unsure why this has happened
> (all workstations are happily reporting).

So == really == the first thing you need to do is uninstall WSUS v2 (using
uninstall "R2 Technologies"), and download WSUS3SP2 and follow the
instructions in the WSUS 3 =SP1= Step By Step Guide for installation on
Windows Server 2003.

But the first related question to your scenario would be this:
Are you running Premium Edition or Standard Edition.
If Premium, do you have ISA2004 installed on the SBS?
If Premium, do you have SQLServer installed on the SBS?

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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

If it helps, here is the entire windowsupdate.log from the moment I
forced status using /detectnow:

2010-03-08 14:12:24 932 d98 AU Triggering AU detection through
DetectNow API
2010-03-08 14:12:24 932 b8 AU #############
2010-03-08 14:12:24 932 b8 AU ## START ## AU: Search for updates
2010-03-08 14:12:24 932 b8 AU #########
2010-03-08 14:12:24 932 b8 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {BB0754A6-0E1F-4542-A26F-399CA50736D0}]
2010-03-08 14:12:24 932 4f8 Agent *************
2010-03-08 14:12:24 932 4f8 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2010-03-08 14:12:24 932 4f8 Agent *********
2010-03-08 14:12:24 932 4f8 Setup *********** Setup: Checking whether
self-update is required ***********
2010-03-08 14:12:24 932 4f8 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default \wusetup.inf
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2010-03-08 14:12:24 932 4f8 Setup * IsUpdateRequired = No
2010-03-08 14:12:29 932 4f8 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2010-03-08 14:12:29 932 4f8 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://SRV1:8530/ClientWebService/client.asmx
2010-03-08 14:12:29 932 4f8 PT Initializing simple targeting cookie,
clientId = d8d87e4b-9372-41ad-8171-a2b9baf94f03, target group = , DNS
name = srv1.berbankhomes.local
2010-03-08 14:12:29 932 4f8 PT Server URL =
http://SRV1:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate
Installable rule, updateId = {FFE143E3-B999-4C99-8D58-A15F82136FA7}.100,
error = 0x80004005
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate Installed
rule, updateId = {FFE143E3-B999-4C99-8D58-A15F82136FA7}.100, error =
0x80004005
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate
Installable rule, updateId = {0ED1CF98-2971-48EF-B50E-1E35ACDAC815}.100,
error = 0x80004005
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate Installed
rule, updateId = {0ED1CF98-2971-48EF-B50E-1E35ACDAC815}.100, error =
0x80004005
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate
Installable rule, updateId = {B97924A5-3203-495A-8EAC-5C3858713704}.101,
error = 0x8024E006
2010-03-08 14:12:33 932 4f8 Agent WARNING: Failed to evaluate Installed
rule, updateId = {B97924A5-3203-495A-8EAC-5C3858713704}.101, error =
0x8024E006
2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: Parse failed: error 0x80070057
2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: Parse failed with 0x80070057

2010-03-08 14:12:34 932 4f8 PT WARNING: Sync of Updates: 0x80070057
2010-03-08 14:12:34 932 4f8 Agent * WARNING: Failed to synchronize,
error = 0x80070057
2010-03-08 14:12:34 932 4f8 Agent * WARNING: Exit code = 0x80070057
2010-03-08 14:12:34 932 4f8 Agent *********
2010-03-08 14:12:34 932 4f8 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2010-03-08 14:12:34 932 4f8 Agent *************
2010-03-08 14:12:34 932 4f8 Agent WARNING: WU client failed Searching
for update with error 0x80070057
2010-03-08 14:12:34 932 4f8 AU >>## RESUMED ## AU: Search for updates
[CallId = {BB0754A6-0E1F-4542-A26F-399CA50736D0}]
2010-03-08 14:12:34 932 4f8 AU # WARNING: Search callback failed,
result = 0x80070057
2010-03-08 14:12:34 932 4f8 AU #########
2010-03-08 14:12:34 932 4f8 AU ## END ## AU: Search for updates
[CallId = {BB0754A6-0E1F-4542-A26F-399CA50736D0}]
2010-03-08 14:12:34 932 4f8 AU #############
2010-03-08 14:12:34 932 4f8 AU AU setting next detection timeout to
2010-03-08 15:03:53
2010-03-08 14:12:39 932 4f8 Report REPORT EVENT:
{FF134958-6061-4FF6-88B5-6101E3CA8E9B} 2010-03-08 14:12:34-0000 1
148 101 {00000000-0000-0000-0000-000000000000} 0 80070057
AutomaticUpdates Failure Software Synchronization Error: Agent failed
detecting with reason: 0x80070057

--

There are some odd things happening here:

2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: Parse failed: error 0x80070057
2010-03-08 14:12:34 932 4f8 EEHndlr FATAL: Parse failed with 0x80070057

Any ideas?

On 08/03/2010 14:13, Lawrence Garvin [MVP] wrote:
> "James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
> news:%...
>
>> I've posted this in the SBS newsgroup with no response, so trying my
>> luck here.
>
> Perhaps because you're asking about an ancient (and heavily customized)
> version of WSUS that nobody wants to remember?
>
>
>> My SBS 2003 R2 server is not reporting itself to WSUS (v2) (installed
>> on same physical machine) as of 5 days ago. I'm unsure why this has
>> happened (all workstations are happily reporting).
>
> So == really == the first thing you need to do is uninstall WSUS v2
> (using uninstall "R2 Technologies"), and download WSUS3SP2 and follow
> the instructions in the WSUS 3 =SP1= Step By Step Guide for installation
> on Windows Server 2003.
>
> But the first related question to your scenario would be this:
> Are you running Premium Edition or Standard Edition.
> If Premium, do you have ISA2004 installed on the SBS?
> If Premium, do you have SQLServer installed on the SBS?
>

Thanks for your response, appreciated.

To answer your question: this is an SBS "standard" install, so no ISA
and no full blown SQLServer.

As to the fact that this is an old version of WSUS, yes... agreed - but
client is still (and has never) unwilling to pay for my time to move to
v3 (he sees no benefit in upgrading, which I tend to agree with as this
WSUS only updates 5 clients. Also, there is a specific approach for
moving to V3 in SBS 2003).

However, the "uninstall v2 and install v3" approach seems like quite a
sledgehammer approach..., particularly knowing that for all other
clients, WSUS continues to function fine (or so it would appear) - so
would you not agree that the issue is on the SBS client side somewhere?

Lastly, if this is == really == the only way to solve this issue, then
I'll look into moving to v3 the "SBS way", but I'd like to try and
explore other avenues first (if they exist)...

If anyone else is sweating over this one, here's the fix - simple
really. The problem was on the client side.

I tried a lot of things: reregister DLLs, rename SoftwareDistribution
folder etc. none of them worked. It still kept coming back with error
0x80070057.

I then visited the windows update website, and it installed the latest
windows update agent.

After that, the next manual sync failed with a new error number:
WARNING: Exceeded max server round trips: 0x80244010

Google told me that this can occur if there are a fair number of updates
pending (19 in my case). Anyway, I let it run automatically and hey
presto, all is now solved and the status report has been generated.
Whether it was simply the new agent or a combination of that and the
other things I've done, I don't know...

I will now be moving to WSUS3, but thought I'd post this to close the
problem.

On 08/03/2010 13:59, James Hurrell wrote:
> I've posted this in the SBS newsgroup with no response, so trying my
> luck here.
>

"James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
news:...

> I then visited the windows update website, and it installed the latest
> windows update agent.

And, had you upgraded your WSUS anytime in the past two years, or more
notably to WSUS3Sp2 in Aug 2009, the latest WUAgent would have been
automatically installed for you at that time.

> Google told me that this can occur if there are a fair number of updates
> pending (19 in my case).

=19= is not what's meant by a "fair number".... more like "more than 80" is
what it means.. and *that* bug was fixed in WUAgent v7.2 (released July
2008)

> I will now be moving to WSUS3

This is Good! :-)


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

On 12/03/2010 20:49, Lawrence Garvin [MVP] wrote:
> "James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
> news:...
>
>> I then visited the windows update website, and it installed the latest
>> windows update agent.
>
> And, had you upgraded your WSUS anytime in the past two years, or more
> notably to WSUS3Sp2 in Aug 2009, the latest WUAgent would have been
> automatically installed for you at that time.

Hindsight is a great thing isn't it. I had no idea support for v2 had
expired.

>
>> Google told me that this can occur if there are a fair number of
>> updates pending (19 in my case).
>
> =19= is not what's meant by a "fair number".... more like "more than 80"
> is what it means.. and *that* bug was fixed in WUAgent v7.2 (released
> July 2008)

Not sure what bug you are talking about. I was talking about this:

http://blogs.technet.com/sus/archive...x80244010.aspx

It explained it well enough for me (and I obviously don't know much).

>
>> I will now be moving to WSUS3
>
> This is Good! :-)

Probably.

"James Hurrell" <> wrote in message
news:...
> On 12/03/2010 20:49, Lawrence Garvin [MVP] wrote:
>> "James Hurrell" <"j_a_hurrell at hotmail com"> wrote in message
>> news:...
>>
>>> I then visited the windows update website, and it installed the latest
>>> windows update agent.
>>
>> And, had you upgraded your WSUS anytime in the past two years, or more
>> notably to WSUS3Sp2 in Aug 2009, the latest WUAgent would have been
>> automatically installed for you at that time.
>
> Hindsight is a great thing isn't it. I had no idea support for v2 had
> expired.

Actually .. it hasn't, but the bugfixes and feature enhancements in the
newer versions of both WSUS and the WUA make it almost imperative to
upgrade.

> Not sure what bug you are talking about. I was talking about this:
>
> http://blogs.technet.com/sus/archive...x80244010.aspx

Ahhh.. yes.. I had forgotten about that quirk as well, but that's more
driven by the composite total of bytes contained in the entire session than
it is necessarily a specific number of updates. As the article notes, the
limit is 200 "trips", where each trip can hold up to 200k of data,
effectively limiting the total data transfer to 200 x 200k = ~40mb metadata
per session. Truly, though, 40mb of metadata is a LOT, and this issue was
not encountered that often, and typically only with systems that were at
downlevel service packs and/or not updated in several months.

>>> I will now be moving to WSUS3
>>
>> This is Good! :-)
>
> Probably.

Definitely!


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

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin