Re: WSUS Client not yet reported

Hi Corey,

Thank you for getting back.

After checking the log files, I found error 506 was encountered on the SBS
server.

It is most likely caused by an IIS error.

I suggest you try following steps and check if it helps:

Suggestion 1: Check IP restriction setting
=========================
1. Click Start, click Run, type inetmgr, and then click OK.
2. In the left pane, expand computer_name, and then expand Web Sites.
3. Right-click the WSUS Administration Web site, and then click Properties.
4. Click the Directory Security tab, and then click Edit in the IP address
and domain name restrictions area.
5. Click Granted access, and then click OK two times.

More information for your reference:

Error message when you visit the WSUS Administrator Web page: "One or more
Update Service components could not be contacted. Check your server status
and ensure that the Windows Server Update Service is running"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;920654

Suggestion 2: Check the IIS settings:
======================================
1. Configure the default Web site to listen on port 80.

2. Configure WSUS Administration to listen on port 8530

3. Please also verify the following settings:

The SelfUpdate virtual directory points to C:\Program Files\Update
Service\SelfUpdate.
The WSUSAdmin virtual directory should have security set to Integrated
Windows Authentication. Set all other virtual directories security to
Anonymous Access Enabled.
Please ensure SelfUpdate virtual directory under default web site is set
to require Integrated Windows Authentication.

For detailed information, please refer to following article:

The Microsoft Windows Server Update Services (WSUS) SelfUpdate service does
not send automatic updates
http://support.microsoft.com/default.aspx?scid=kb;EN-US;920659

Suggestion 3: Prepare a clean boot environment on both SBS server and the
client workstation:
===========================================================
1. Click Start and Click Run, and in the "Open" line, type in "MSCONFIG"
(without the quotation marks) and click OK.
2. Under the Service tab, check "Hide All Microsoft Services", and then
click "Disable All" button. In this way, we can disable all the services
which belong to third-party programs.
3. Under the Startup tab, click "Disable All" button.

4. Click OK.
5. Choose Yes to restart the computer.
6. Check "Don't show this message or launch the system configuration
utility when Windows starts".
7. Please check if the issue persists.

NOTE: We can check on Normal Startup in the General tab to roll back to
Normal Mode.

I hope the above information is helpful to you. However, if the issue
persists, please help me gather IIS log and Metabase to me for further
analysis, send to me: v-mzhuan@xxxxxxxxxxxxx with the subject in the
newsgroup:

1). Install MBExplorer by installing IIS 6 Resource Kit Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en
2). Once it is installed, access it from Start, Programs, IIS Resources,
Metabase Explorer.
3). In the left pane, right click ''LM'' (under your server computer name)
to choose ''Export to file'', and then save it as IIS.mbk.
4). Compress this mbk file and send it to me for analysis. Please let me
know the password if you set on this iis mbk file.

Please collect the IIS log on SBS Server so that I can perform further
research:

1). On the Serves, open IIS MMC, right click Default Web Site and then
click Properties.
2). Click Website tab and then check Enable logging.
3). Stop the Default Website and RENAME the existing IIS log files under
C:\WINDOWS\system32\LogFiles\W3SVC1.
4). Restart the Default Website and reproduce the problem, which will
generate new IIS log file with the exact error.
5). Wait for a while so that IIS Log can be synced. And then go to the
following folder on Exchange Server: C:\WINDOWS\system32\LogFiles\W3SVC1.
6). Send me the log files to my working email address
v-mzhuan@xxxxxxxxxxxxxx And please let me know the alias of the user who
encountered the issue.

Please try the above steps at your earliest convenience. If you have any
concern, please feel free to let me know.

Best regards,

Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Corey" <czinn@xxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Re: WSUS Client not yet reported
| Date: Tue, 11 Sep 2007 16:47:43 -0400
| Organization: Posted via Supernews, http://www.supernews.com
| Message-ID: <13edvn5gemokc4d@xxxxxxxxxxxxxxxxxx>
| References: <13dri6oq3ojq1fa@xxxxxxxxxxxxxxxxxx>
<BxZI3757HHA.360@xxxxxxxxxxxxxxxxxxxxxx>
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| X-Complaints-To: abuse@xxxxxxxxxxxxx
| Lines: 346
| X-Original-Bytes: 14533
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out.
cwix.com!newsfeed.cwix.com!newsfeed.stueberl.de!ecngs!feeder.ecngs.de!212.10
1.4.254.MISMATCH!solnet.ch!solnet.ch!newspeer1.nwr.nac.net!border2.nntp.dca.
giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google
com!news3.google.com!sn-xt-sjc-05!sn-xt-sjc-09!sn-post-sjc-01!supernews.com
!corp.supernews.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:62281
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| See comments in line, marked with ***.
|
| Thanks.
|
| Corey
|
|
| "Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:BxZI3757HHA.360@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Hello Corey,
| >
| > Thank you for posting here.
| >
| > From your post, I understand that a client workstation is always in "not
| > reported status" in WSUS and following error message was found in
Windows
| > Update log:
| >
| > WARNING: DownloadFileInternal failed for http://
| > wsusserver:8530/selfupdate/wuident.cab: error 0x80190191
| > Setup FATAL: IsUpdateRequired failed with error 0x80244017
| >
| > The root cause can be at either the server side or the client side. Is
it
| > convenient for you to connect another client workstation to the SBS
| > server?
| > If yes, please check if it works with WSUS.
|
| ***At this point, I don't have another workstation to try in the test
| environment before deploying.
|
|
| > If it does not work either, the root cause should be on the server.
| >
| > Firstly I would like to confirm what version of WSUS is installed on the
| > SBS server. WSUS 2.0? WSUS 3.0? Or the embedded one in SBS R2?
|
|
| ***It is build 2.0.0.2620
|
|
| >
| > Based on the error, it appears the IUSR_xxx and IWAM_xxx account had
lost
| > the NTFS permission on the SBS folders.
| >
| > So to this issue, please try the following steps to verify the settings:
| >
| > A. Run the following script to reload selfupdate tree:
| > cscript "WSUSInstallationDriveLetter:\program files\update
| > services\setup\InstallSelfupdateOnPort80.vbs"
| >
| > For example:
| > cscript "C:\program files\update
| > services\setup\InstallSelfupdateOnPort80.vbs"
|
|
| ***I did this, as you indicated.
|
|
| > B: Since this is a SBS server, the SharePoint should be installed by
| > default, please follow these steps to configure the Default web site:
| >
| > 1. Grant Anonymous access (Anonymous Auth) to the Default Web site,
| > ClientWebService and Selfupdate virtual roots in IIS.
|
|
| ***This was already the case, but I checked. Currently, the Default
website
| is stopped, because it uses port 80, but so does SharePoint 3.0. However,
I
| tried stopping SharePoint and having the Default running, and that didn't
| make a difference.
|
|
| > 2. Exclude specific requests from being intercepted by the Windows
| > Sharepoint Services ISAPI DLL by doing the following:
| > a. Open the Windows Sharepoint Services Central Administration Site
(click
| > Start, point to Administrative Tools, and then click Sharepoint Central
| > Administration).
| > b. Click Virtual Server Configuration, and then click Configure Virtual
| > Server Settings.
| > c. Click Default Web Site.
| > d. Click Virtual Server Management, and then click Define managed paths.
| > e. In the Add a new pathbox, set the type to excluded path. Under Path,
| > type the following:
| > "/iuident.cab"
| > "/wutrack.bin"
| > "/clientwebservice"
| > "/Selfupdate"
|
|
| ***It is SharePoint 3.0 that is installed. I can not find the settings
you
| indicate.
|
|
| >
| > C. Open the IIS admin console, make sure the following site and virtual
| > folder had been set to "Allow Anonymous permission":
| >
| > ClientWebService, Content, DssAuthWebService, ReportingWebService,
| > Selfupdate, ServerSync, WebService, SimpleAuthWebService.
| >
|
| ***For the WSUS website, all of those have anonymous access enabled.
|
|
| > D. make sure the IUSR_xxx and IWAM_xxx account had the full control NTFS
| > permission on the following folder on the disk
| > "..\WSUS\WsusContent"
| > " ..Program Files\Update Services\"
|
|
| ***I made these changes, as indicated.
|
|
| > I hope the above information is helpful to you. However, if the issue
| > persists, please help me gather following information:
| >
| > 1. Please send me WindowsUpdate.log on the client workstation.
| >
|
| ***I sent the contents of this file in my previous post. See below.
|
|
| > 2. Please let me know if Microsoft Update still works on the client
| > workstation.
|
| ***Yes. I didn't download files to be updated, but it does recognize what
| needs to be updated.
|
| >
| > 3. Please download the MPS Report tool from the following link and run
it
| > on both the client workstation and the SBS server, then send the
generated
| > CAB file to my mailbox v-mzhuan@xxxxxxxxxxxxx for further investigation
so
| > that we can find what the root cause is:
| >
| >
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
| > 15706/MPSRPT_SUS.EXE
| >
|
| ***I've run this on both the server and client and will send to you
shortly.
|
|
| > For your information:
| >
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
| > 88B7-F9C79B7306C0&displaylang=en
| >
| > Please try the above steps at your earliest convenience. If you have any
| > concern, please feel free to let me know.
| >
| > Best regards,
| >
| > Manfred Zhuang(MSFT)
| > Microsoft Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > =====================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
| > the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
| > doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| > --------------------
| > | From: "Corey" <czinn@xxxxxxxxxxxx>
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Subject: WSUS Client not yet reported
| > | Date: Tue, 4 Sep 2007 17:06:57 -0400
| > | Organization: Posted via Supernews, http://www.supernews.com
| > | Message-ID: <13dri6oq3ojq1fa@xxxxxxxxxxxxxxxxxx>
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| > | X-RFC2646: Format=Flowed; Original
| > | X-Complaints-To: abuse@xxxxxxxxxxxxx
| > | Lines: 112
| > | Bytes: 6624
| > | X-Original-Bytes: 6581
| > | Path:
| >
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
| >
0.sul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca
| >
giganews.com!nntp.giganews.com!postnews.google.com!news3.google.com!sn-xt-s
| >
jc-05!sn-xt-sjc-10!sn-xt-sjc-06!sn-post-sjc-01!supernews.com!corp.supernews.
| > com!not-for-mail
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:60755
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | I had a previous issue with WSUS which was resolved, and I continued
the
| > | thread with a new issue, which probably wasn't a good idea. So I'm
| > starting
| > | a new thread for this issue.
| > |
| > | I have a SBS2003 set up with WSUS. Right now, I only have one client
pc
| > (XP
| > | Pro SP 2). It is showing up correctly in WSUS. However, it says "This
| > | computer has not reported status yet." I have checked the
| > WindowsUpdate.log
| > | on the client, which has the following (I replaced the actual server
| > name
| > | with "wsusserver' in the following log info):
| > |
| > | 2007-09-04 16:44:24:478 1772 7a4 AU #############
| > | 2007-09-04 16:44:24:478 1772 7a4 AU ## START ## AU: Search for
updates
| > | 2007-09-04 16:44:24:478 1772 7a4 AU #########
| > | 2007-09-04 16:44:24:488 1772 7a4 AU <<## SUBMITTED ## AU: Search for
| > updates
| > | [CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
| > | 2007-09-04 16:44:24:488 1772 76c Agent *************
| > | 2007-09-04 16:44:24:488 1772 76c Agent ** START ** Agent: Finding
| > updates
| > | [CallerId = AutomaticUpdates]
| > | 2007-09-04 16:44:24:488 1772 76c Agent *********
| > | 2007-09-04 16:44:24:488 1772 76c Agent * Online = Yes; Ignore
download
| > | priority = No
| > | 2007-09-04 16:44:24:488 1772 76c 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"
| > | 2007-09-04 16:44:24:488 1772 76c Agent * ServiceID =
| > | {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
| > | 2007-09-04 16:44:24:498 1772 76c Misc WARNING: WinHttp:
| > | SendRequestToServerForFileInformation failed with 0x80190191
| > | 2007-09-04 16:44:24:498 1772 76c Misc WARNING: WinHttp:
| > | ShouldFileBeDownloaded failed with 0x80190191
| > | 2007-09-04 16:44:24:508 1772 76c Misc WARNING: WinHttp:
| > | SendRequestToServerForFileInformation failed with 0x80190191
| > | 2007-09-04 16:44:24:508 1772 76c Misc WARNING: WinHttp:
| > | ShouldFileBeDownloaded failed with 0x80190191
| > | 2007-09-04 16:44:24:518 1772 76c Misc WARNING: WinHttp:
| > | SendRequestToServerForFileInformation failed with 0x80190191
| > | 2007-09-04 16:44:24:518 1772 76c Misc WARNING: WinHttp:
| > | ShouldFileBeDownloaded failed with 0x80190191
| > | 2007-09-04 16:44:24:548 1772 76c Misc WARNING: WinHttp:
| > | SendRequestToServerForFileInformation failed with 0x80190191
| > | 2007-09-04 16:44:24:548 1772 76c Misc WARNING: WinHttp:
| > | ShouldFileBeDownloaded failed with 0x80190191
| > | 2007-09-04 16:44:24:548 1772 76c Misc WARNING: DownloadFileInternal
| > failed
| > | for http://wsusserver:8530/selfupdate/wuident.cab: error 0x80190191
| > | 2007-09-04 16:44:24:548 1772 76c Setup FATAL: IsUpdateRequired failed
| > with
| > | error 0x80244017
| > | 2007-09-04 16:44:24:548 1772 76c Setup WARNING: SelfUpdate: Default
| > Service:
| > | IsUpdateRequired failed: 0x80244017
| > | 2007-09-04 16:44:24:548 1772 76c Setup WARNING: SelfUpdate: Default
| > Service:
| > | IsUpdateRequired failed, error = 0x80244017
| > | 2007-09-04 16:44:24:548 1772 76c Agent * WARNING: Skipping scan,
| > | self-update check returned 0x80244017
| > | 2007-09-04 16:44:25:964 1772 76c Agent * WARNING: Exit code =
| > 0x80244017
| > | 2007-09-04 16:44:25:964 1772 76c Agent *********
| > | 2007-09-04 16:44:25:964 1772 76c Agent ** END ** Agent: Finding
| > updates
| > | [CallerId = AutomaticUpdates]
| > | 2007-09-04 16:44:25:964 1772 76c Agent *************
| > | 2007-09-04 16:44:25:964 1772 76c Agent WARNING: WU client failed
| > Searching
| > | for update with error 0x80244017
| > | 2007-09-04 16:44:25:964 1772 fa0 AU >>## RESUMED ## AU: Search for
| > updates
| > | [CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
| > | 2007-09-04 16:44:25:964 1772 fa0 AU # WARNING: Search callback
failed,
| > | result = 0x80244017
| > | 2007-09-04 16:44:25:964 1772 fa0 AU # WARNING: Failed to find
updates
| > with
| > | error code 80244017
| > | 2007-09-04 16:44:25:964 1772 fa0 AU #########
| > | 2007-09-04 16:44:25:964 1772 fa0 AU ## END ## AU: Search for
updates
| > | [CallId = {A55F5062-D8F3-4C3A-ACF8-2F575CC7A0CE}]
| > | 2007-09-04 16:44:25:964 1772 fa0 AU #############
| > | 2007-09-04 16:44:25:964 1772 fa0 AU AU setting next detection timeout
to
| > | 2007-09-04 21:42:41
| > | 2007-09-04 16:44:29:558 1772 76c Report REPORT EVENT:
| > | {B1E8FC8D-ABB6-4361-AFD2-17C959716697} 2007-09-04 16:44:24:548-0400 1
| > 148
| > | 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244017 SelfUpdate
Failure
| > | Software Synchronization Windows Update Client failed to detect with
| > error
| > | 0x80244017.
| > | 2007-09-04 16:51:42:400 1772 76c PT WARNING: Cached cookie has
expired
| > or
| > | new PID is available
| > | 2007-09-04 16:51:42:400 1772 76c PT Initializing simple targeting
| > cookie,
| > | clientId = c970b7b1-a859-49c5-b930-a6a758067ede, target group =
| > Computers,
| > | DNS name = coreylaptop.makromed.local
| > | 2007-09-04 16:51:42:400 1772 76c PT Server URL =
| > | http://wsusserver:8530/SimpleAuthWebService/SimpleAuth.asmx
| > | 2007-09-04 16:51:42:500 1772 76c Report Uploading 1 events using
cached
| > | cookie, reporting URL =
| > | http://wsusserver:8530/ReportingWebService/ReportingWebService.asmx
| > | 2007-09-04 16:51:42:510 1772 76c Report Reporter successfully
uploaded 1
| > | events.
| > |
| > |
| > |
| > | I have searched this issue, and have tried several things to no avail:
| > | - I have typed in a browser window the path to wuident.cab, and
| > successfully
| > | got the download box, so it's not a rights issue there.
| > | - I verified that the WSUS Administration object in IIS has anonymous
| > access
| > | checked (as does the Selfupdate object under WSUS).
| > | - I have completely disabled the firewall on the client pc.
| > | - I have verified that the pc is not using a proxy (proxycfg yields
| > "direct
| > | access").
| > |
| > | Any other thoughts/suggestions? This is a new server that I'm setting
up
| > and
| > | will be deploying soon.
| > |
| > | Thanks!
| > |
| > | -Corey
| > |
| > |
| > |
| >
|
|
|

.