unknown
2010-03-08 13:59:57 UTC
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)
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)