------------
Two brand new Server 2008 SP2 64 bit servers group policy configured to a
wsus 3.0 sp1 working fine for other 2003 servers and XP clients. Both 2008
servers fail to report and client diag gives;
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
The system cannot find the file specified.
Windowsupdate.log shows;
2009-07-02 10:11:25:770 316 afc AU #############
2009-07-02 10:11:25:770 316 afc AU ## START ## AU: Search for updates
2009-07-02 10:11:25:770 316 afc AU #########
2009-07-02 10:11:25:770 316 afc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {C5A31A1A-9835-43BA-B193-FD3F08FA787F}]
2009-07-02 10:11:25:770 316 d64 Agent *************
2009-07-02 10:11:25:770 316 d64 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-02 10:11:25:770 316 d64 Agent *********
2009-07-02 10:11:25:770 316 d64 Agent * Online = Yes; Ignore download
priority = No
2009-07-02 10:11:25:770 316 d64 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"
2009-07-02 10:11:25:770 316 d64 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-07-02 10:11:25:770 316 d64 Setup Checking for agent SelfUpdate
2009-07-02 10:11:25:770 316 d64 Setup Client version: Core: 7.0.6002.18005
Aux: 7.0.6002.18005
2009-07-02 10:11:25:770 316 d64 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2009-07-02 10:11:25:770 316 d64 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190193
2009-07-02 10:11:25:770 316 d64 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2009-07-02 10:11:25:770 316 d64 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190193
2009-07-02 10:11:25:786 316 d64 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2009-07-02 10:11:25:786 316 d64 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190193
2009-07-02 10:11:25:786 316 d64 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80190193
2009-07-02 10:11:25:786 316 d64 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80190193
2009-07-02 10:11:25:786 316 d64 Misc WARNING: DownloadFileInternal failed
for http://140.198.144.54/selfupdate/wuident.cab: error 0x80190193
2009-07-02 10:11:25:786 316 d64 Setup WARNING: SelfUpdate check failed to
download package information, error = 0x80244018
2009-07-02 10:11:25:786 316 d64 Setup FATAL: SelfUpdate check failed, err =
0x80244018
2009-07-02 10:11:25:786 316 d64 Agent * WARNING: Skipping scan,
self-update check returned 0x80244018
2009-07-02 10:11:26:004 316 d64 Agent * WARNING: Exit code = 0x80244018
2009-07-02 10:11:26:004 316 d64 Agent *********
2009-07-02 10:11:26:004 316 d64 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-07-02 10:11:26:004 316 d64 Agent *************
2009-07-02 10:11:26:004 316 d64 Agent WARNING: WU client failed Searching
for update with error 0x80244018
2009-07-02 10:11:26:004 316 ff4 AU >>## RESUMED ## AU: Search for updates
[CallId = {C5A31A1A-9835-43BA-B193-FD3F08FA787F}]
2009-07-02 10:11:26:004 316 ff4 AU # WARNING: Search callback failed,
result = 0x80244018
2009-07-02 10:11:26:004 316 ff4 AU # WARNING: Failed to find updates with
error code 80244018
2009-07-02 10:11:26:004 316 ff4 AU #########
2009-07-02 10:11:26:004 316 ff4 AU ## END ## AU: Search for updates
[CallId = {C5A31A1A-9835-43BA-B193-FD3F08FA787F}]
2009-07-02 10:11:26:004 316 ff4 AU #############
--
/kj
> Need suggestions for the following;
>
> ------------
>
> Two brand new Server 2008 SP2 64 bit servers group policy configured to a
> wsus 3.0 sp1 working fine for other 2003 servers and XP clients. Both 2008
> servers fail to report and client diag gives;
> 2009-07-02 10:11:25:786 316 d64 Misc WARNING: DownloadFileInternal failed
> for http://140.198.144.54/selfupdate/wuident.cab: error 0x80190193
Have you configured the Windows 2008 firewall to permit egress for HTTP
(port 80)?
--
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 Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Turned it off completely with no change Lawrence. I can run a portquery to
check connectivity as they are on different subnets and while there
shouldn't be any external firewall restrictions, it wouldn't surprise me.
May not be able to check this until next week.
--
/kj
> I can run a portquery to check connectivity as they are on different
> subnets and while there shouldn't be any external firewall restrictions,
> it wouldn't surprise me.
We definitely need to explore this "different subnets" scenario. If they're
on different subnets then something has to be routing traffic between those
two subnets. Whatever it is, make sure it also does not have any
restrictions on HTTP(S) traffic.
> May not be able to check this until next week.
No problem. I'm here when you can get to it.
Sorry for the delay Lawrence. I finnaly got around to verify it. Ping,
portqry, and telnet confirm basic connectivity and TCP port 80 to the WSUS
server. One of these 2008 servers is running server core but the clientdiag
provides the same details.
----
querying...
TCP port 80 (http service): LISTENING
--
/kj
> Sorry for the delay Lawrence. I finnaly got around to verify it. Ping,
> portqry, and telnet confirm basic connectivity and TCP port 80 to the WSUS
> server. One of these 2008 servers is running server core but the
> clientdiag provides the same details.
Okay... first thing to clear up... I missed an important diagnostic point in
your original post:
> Two brand new Server 2008 SP2 64 bit servers group policy configured to a
> wsus 3.0 sp1 working fine for other 2003 servers and XP clients. Both 2008
> servers fail to report and client diag gives;
The Client Diagnostic Tool is a 32-bit only tool. The error you received on
these two servers:
> GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
is a manifestation of attempting to run this 32-bit tool on a 64-bit system.
Of course, I did focus on the WindowsUpdate.log errors, not the CDT error,
so our interest in identifying the cause of the HTTP 403 errors in the
logfile is still our primary interest.
> Ping, portqry, and telnet confirm basic connectivity and TCP port 80
> to the WSUS server. One of these 2008 servers is running server core
The other thing we need to keep in mind is that the WUAgent uses WinHTTP, so
many standard diagnostic methodologies may not show up issues exclusive to
WinHTTP.
Let's see what we get from the WinHTTP proxy configuration on the machine:
Please run this command: NETSH WINHTTP SHOW PROXY
Ah, good to know. (any expectation of a 64 bit version someday soon?)
> Of course, I did focus on the WindowsUpdate.log errors, not the CDT
> error, so our interest in identifying the cause of the HTTP 403
> errors in the logfile is still our primary interest.
>
>> Ping, portqry, and telnet confirm basic connectivity and TCP port 80
>> to the WSUS server. One of these 2008 servers is running server core
>
> The other thing we need to keep in mind is that the WUAgent uses
> WinHTTP, so many standard diagnostic methodologies may not show up
> issues exclusive to WinHTTP.
>
> Let's see what we get from the WinHTTP proxy configuration on the
> machine:
> Please run this command: NETSH WINHTTP SHOW PROXY
results below.
--
C:\Windows>NETSH WINHTTP SHOW PROXY
Current WinHTTP proxy settings:
Direct access (no proxy server).
--
/kj
>>> GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
>>
>> is a manifestation of attempting to run this 32-bit tool on a 64-bit
>> system.
>
> Ah, good to know. (any expectation of a 64 bit version someday soon?)
I've suggested to TPTB that the tool needs to be distributed in a 64-bit
version.
We'll see . . .
>> Let's see what we get from the WinHTTP proxy configuration on the
>> machine:
>> Please run this command: NETSH WINHTTP SHOW PROXY
>
> results below.
>
> --
>
> C:\Windows>NETSH WINHTTP SHOW PROXY
>
> Current WinHTTP proxy settings:
>
> Direct access (no proxy server).
Okay.. so the machine (WinHTTP) is not configured to use a proxy server.
Have we confirmed that there are *no* proxy or proxy-like devices sitting
between this machine and the WSUS Server?
If you attempt to do a detection from this machine, what is logged in the
IIS logs of the WSUS Server?
I don't see much, but then logging is at default level. (This is from one of
the trouble children but seems to be consistent with the rest)
--------
2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
2009-06-29 22:43:32 W3SVC1 140.198.144.54 GET /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 0
2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
2009-06-29 22:43:32 W3SVC1 140.198.144.54 GET /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 0
2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
2009-06-29 22:43:32 W3SVC1 140.198.144.54 GET /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 0
2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
2009-06-29 22:43:32 W3SVC1 140.198.144.54 GET /selfupdate/wuident.cab
0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 0
--
/kj
> I don't see much, but then logging is at default level. (This is from one
> of the trouble children but seems to be consistent with the rest)
It's enough! :-)
> 2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
> 0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
Specifically, an HTTP 403.6 error... caused by a blocked IP source address.
See http://support.microsoft.com/kb/248043 for more information.
>"kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
>news:ORhZCvBA...@TK2MSFTNGP02.phx.gbl...
>
>>>> GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
>>>
>>> is a manifestation of attempting to run this 32-bit tool on a 64-bit
>>> system.
>>
>> Ah, good to know. (any expectation of a 64 bit version someday soon?)
>
>I've suggested to TPTB that the tool needs to be distributed in a 64-bit
>version.
>
>We'll see . . .
>
And hopefully updates from WSUS 2 only.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
>"kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
>news:ufK35cCA...@TK2MSFTNGP02.phx.gbl...
>
>> I don't see much, but then logging is at default level. (This is from one
>> of the trouble children but seems to be consistent with the rest)
>
>It's enough! :-)
>
>> 2009-06-29 22:43:32 W3SVC1 140.198.144.54 HEAD /selfupdate/wuident.cab
>> 0906292244 80 - 10.198.144.5 Windows-Update-Agent 403 6 64
>
>Specifically, an HTTP 403.6 error... caused by a blocked IP source address.
>
>See http://support.microsoft.com/kb/248043 for more information.
Ah! Not allowing Localhost access to IIS maybe only the specific host IP.
That seems to be it. Waiting for them to report back. Thanks Lawrence.
Is there a connect bug / feedback for clientdiag x64? I'd be happy to vote
on it or open one.
--
/kj
> Is there a connect bug / feedback for clientdiag x64? I'd be happy to vote
> on it or open one.
There is not, to my knowledge.
I'm lobbying directly to the WSUS/WUA product team for two updates in the
product.
[1] 64-bit compilation
[2] updated awareness of the v7 WUAgent
Opening an issue in the WSUS3SP2 Connect Site, though, can't hurt.
>>> Ah, good to know. (any expectation of a 64 bit version someday soon?)
>>I've suggested to TPTB that the tool needs to be distributed in a 64-bit
>>version.
>>
>>We'll see . . .
> And hopefully updates from WSUS 2 only.
Yes... v7.x WUAgent awareness was the #2 item on my list of needed
'updates'.
Problem children in another subnet are begining to report up now - Thanks
for the help
64bit clientdiag 'suggestion' submitted;
FeedbackID=473579
Thanks again Lawrence.
--
/kj
I hope I filed it on the right connect page;
https://connect.microsoft.com/site/sitehome.aspx?SiteID=110
Under feedback and if you scroll down a ways you should see the submissions.
This is a little different than other connect product pages.
I think this will take you there direct.
https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=473579&SiteID=110
>
>
>
> On Thu, 9 Jul 2009 14:00:13 -0700, "kj [SBS MVP]"
> <Kevin...@SPAMFREE.gmail.com> wrote:
>
>> Lawrence Garvin [MVP] wrote:
>>> "kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
>>> news:%23B6jiIL...@TK2MSFTNGP05.phx.gbl...
>>>
>>>> Is there a connect bug / feedback for clientdiag x64? I'd be happy
>>>> to vote on it or open one.
>>>
>>> There is not, to my knowledge.
>>>
>>> I'm lobbying directly to the WSUS/WUA product team for two updates
>>> in the product.
>>>
>>> [1] 64-bit compilation
>>> [2] updated awareness of the v7 WUAgent
>>>
>>> Opening an issue in the WSUS3SP2 Connect Site, though, can't hurt.
>>
>> Problem children in another subnet are begining to report up now -
>> Thanks for the help
>>
>> 64bit clientdiag 'suggestion' submitted;
>>
>> FeedbackID=473579
>>
>> Thanks again Lawrence.
--
/kj
>Dave Mills wrote:
>> What am I missing on Connect. I thought I would vote for this but
>> although I can download WSUS 3 RC2 when I click "Feedback" I just get
>> taken to the Welcome page.
>
>I hope I filed it on the right connect page;
>https://connect.microsoft.com/site/sitehome.aspx?SiteID=110
>
>Under feedback and if you scroll down a ways you should see the submissions.
>This is a little different than other connect product pages.
Ta, It did not occur to me that the feedback page would be identical to the home
page except for the white space followed by the actual feedback stuff. Not a
brilliant page design in my opinion.
Supporting comment added but I don't see any voting system in the feedback page,
is this done via "rating"
>
>I think this will take you there direct.
>https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=473579&SiteID=110
>
>
>>
>>
>>
>> On Thu, 9 Jul 2009 14:00:13 -0700, "kj [SBS MVP]"
>> <Kevin...@SPAMFREE.gmail.com> wrote:
>>
>>> Lawrence Garvin [MVP] wrote:
>>>> "kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
>>>> news:%23B6jiIL...@TK2MSFTNGP05.phx.gbl...
>>>>
>>>>> Is there a connect bug / feedback for clientdiag x64? I'd be happy
>>>>> to vote on it or open one.
>>>>
>>>> There is not, to my knowledge.
>>>>
>>>> I'm lobbying directly to the WSUS/WUA product team for two updates
>>>> in the product.
>>>>
>>>> [1] 64-bit compilation
>>>> [2] updated awareness of the v7 WUAgent
>>>>
>>>> Opening an issue in the WSUS3SP2 Connect Site, though, can't hurt.
>>>
>>> Problem children in another subnet are begining to report up now -
>>> Thanks for the help
>>>
>>> 64bit clientdiag 'suggestion' submitted;
>>>
>>> FeedbackID=473579
>>>
>>> Thanks again Lawrence.
--
It surprises me how many variances there are with the different product
groups and their connect pages.
I believe only the rating and validations are available for this
'suggestion' at present. Thanks for adding the comment.
>
>>
>> I think this will take you there direct.
>> https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=473579&SiteID=110
>>
>>
>>>
>>>
>>>
>>> On Thu, 9 Jul 2009 14:00:13 -0700, "kj [SBS MVP]"
>>> <Kevin...@SPAMFREE.gmail.com> wrote:
>>>
>>>> Lawrence Garvin [MVP] wrote:
>>>>> "kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
>>>>> news:%23B6jiIL...@TK2MSFTNGP05.phx.gbl...
>>>>>
>>>>>> Is there a connect bug / feedback for clientdiag x64? I'd be
>>>>>> happy to vote on it or open one.
>>>>>
>>>>> There is not, to my knowledge.
>>>>>
>>>>> I'm lobbying directly to the WSUS/WUA product team for two updates
>>>>> in the product.
>>>>>
>>>>> [1] 64-bit compilation
>>>>> [2] updated awareness of the v7 WUAgent
>>>>>
>>>>> Opening an issue in the WSUS3SP2 Connect Site, though, can't hurt.
>>>>
>>>> Problem children in another subnet are begining to report up now -
>>>> Thanks for the help
>>>>
>>>> 64bit clientdiag 'suggestion' submitted;
>>>>
>>>> FeedbackID=473579
>>>>
>>>> Thanks again Lawrence.
--
/kj
Did u get any 64 bit clientdiag.exe tool which can be run in windows 2008
64 bit os ???
"Kalpesh" wrote:
>
Not yet... and no indication that one will be produced.
--
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/profile/Lawrence.Garvin
Did you check http://support.microsoft.com/kb/910336 ?
Cheers!
--
augusto alvarez | it consultant
MSP - MCTS - MCITP DBA
http://blog.augustoalvarez.com.ar/
"kj [SBS MVP]" <Kevin...@SPAMFREE.gmail.com> wrote in message
news:#F3qVe1#JHA....@TK2MSFTNGP02.phx.gbl...