Re: WSUS Client not yet reported

I successfully uninstalled and reinstalled the Monitoring component, and
then installed R2. It seems that there were some folders that the
Administrators group did not have full access to; once I corrected that, I
could uninstalled/reinstall properly.

Now the client pc is no longer showing up in WSUS, so of course it's not
reporting. I will email you the MPS reports (server and client) and the
WindowsUpdate.log from the client.

Thanks for your continued help with this issue.

Corey

"Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Hjsnu9P%23HHA.4200@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Corey,

I am sorry for the delay due to the weekend.

I understand that following error message was received when trying to
install SBS 2003 R2:

!Error! WorkItemExecutor: Exception occured in DoWork() for work
item RunMSP: System.Exception: Unable to open product
{5546F70C-0437-44EE-A923-7C23E6EFF689}, MsiOpenProduct() returned 1605
at Setup_Util.SetupUtil.GetTargetPathOfProduct(String productCode,
String target)
at R2_SetupWizard.R2WI_RunMSP.get_MSIDefaultProperty()
at R2_SetupWizard.R2WI_RunMSP.DoWork(StringDictionary sd)

{5546F70C-0437-44EE-A923-7C23E6EFF689} is the UUID for SBS monitoring
component. This error can most likely be caused by two factors:

1. You tried to install R2 as a user that is not the built-in
Administrator.
2. The monitoring component on SBS server was corrupted.

At this point, I suggest you try following steps:

Step 1: Log on SBS by using the built-in Administrator
================================
We can use perform following steps to verify it:

1. Start-->Run, type cmd and click OK.
2. Run following command:

NET USER <USERNAME> /Domain

(Replace <USERNAME> with the user you are currently logged in with).

The built-in Administrator will show the following as the Comment:

"Built-In account for administering the computer/domain."

If it still cannot be installed, let's try following steps:

Step 2: Re-configure monitoring component:
===========================
1. Inset SBS 2003 SP1 installation CD3.
2. Run following command:

X:\sbs\monitor\monitoring.msi INSTDIR="C:\Program Files\Microsoft Windows
Small Business Server\Monitoring" IISDIR=c:\inetpub\Monitoring /L*v
c:\log.txt

Please replace the X with your CD drive letter.

After that, please try to install R2 again. If it fails again, I am afraid
we need to reinstall SBS monitoring component:

Step 3: Reinstall SBS monitoring component:
=============================
0. Make a full backup of the SBS 2003 server.

1. Temporarily uninstall your antivirus programs and disable all other
third party services.

2. Uninstall Monitoring using SBS integrated setup.

3. Remove the Microsoft SQL Data Engine (MSDE) component. To do so, follow
these steps:

a. Click "Start", point to "Control Panel", and then click "Add or Remove
Programs".

b. Click "Microsoft SQL Server Desktop Engine (SBSMONITORING)", and then
click "Remove".

c. When you are prompted about whether you want to remove Microsoft SQL
Server Desktop Engine (SBSMONITORING) from your computer, click "Yes".

d. Start Windows Explorer, and then locate and delete the following
folder:

Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING

e. Use Registry Editor to delete the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Monitoring
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMonitoring

4. Delete the Monitoring virtual directory from IIS.

5. Rename the C:\Inetpub\Monitoring folder

6. Reinstall Monitoring component using SBS integrated setup.

Then, let's try to install R2.

However, if the issue persists, please help me gather following
information:

1. Please send me the latest MPS report.
2. Please zip the entire C:\Program Files\Microsoft Integration\Windows
Small Business Server 2003\Logs folder and send it to
v-mzhuan@xxxxxxxxxxxxxx
3. Screenshots of the error messages you received.

Your time and effort spent are appreciated.

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: Fri, 14 Sep 2007 14:30:03 -0400
| Organization: Posted via Supernews, http://www.supernews.com
| Message-ID: <13elkohd1hhg07e@xxxxxxxxxxxxxxxxxx>
| References: <13dri6oq3ojq1fa@xxxxxxxxxxxxxxxxxx>
<BxZI3757HHA.360@xxxxxxxxxxxxxxxxxxxxxx>
<13edvn5gemokc4d@xxxxxxxxxxxxxxxxxx>
<CHzW8oT9HHA.5604@xxxxxxxxxxxxxxxxxxxxxx>
<13eg2k82t6ot21f@xxxxxxxxxxxxxxxxxx>
<mk9390g9HHA.5532@xxxxxxxxxxxxxxxxxxxxxx>
<13ej5qtta9llr05@xxxxxxxxxxxxxxxxxx>
<0x2WEco9HHA.5204@xxxxxxxxxxxxxxxxxxxxxx>
| 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: 1122
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
0.sul.t-online.de!t-online.de!newsfeed.freenet.de!feeder.news-service.com!fe
eder1.cambrium.nl!feed.tweaknews.nl!138.199.65.86.MISMATCH!sn-xt-ams-06!sn-x
t-ams-03!sn-ams!sn-feed-ams-02!sn-post-ams-01!sn-post-sjc-02!sn-post-sjc-01!
supernews.com!corp.supernews.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:63092
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| The companyweb appears to be working (there may be a rights issue, but
| that's separate and I'll deal with that). I got to the point of
uninstalling
| R2 and then in the process of reinstalling. During the install, it said
| there was an error and to check the log for more details. Here is an
excerpt
| from the R2_Setup.log file:
|
| !Error! WorkItemExecutor: Exception occured in DoWork() for work
| item RunMSP: System.Exception: Unable to open product
| {5546F70C-0437-44EE-A923-7C23E6EFF689}, MsiOpenProduct() returned 1605
| at Setup_Util.SetupUtil.GetTargetPathOfProduct(String productCode,
String
| target)
| at R2_SetupWizard.R2WI_RunMSP.get_MSIDefaultProperty()
| at R2_SetupWizard.R2WI_RunMSP.DoWork(StringDictionary sd)
|
|
| Thoughts on this?
|
| Thanks.
|
|
| Corey
|
|
| "Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in message
| news:0x2WEco9HHA.5204@xxxxxxxxxxxxxxxxxxxxxxxxx
| > Hello Corey,
| >
| > Thank you for reply.
| >
| > I understand that you uninstalled WSS 3.0 and reinstalled Intranet
| > component.
| >
| > However, now companyweb cannot be accessed. I don't think it is
related
to
| > the WSUS issue.
| >
| > To ensure WSS 2.0 is interact. I suggest you refer to following
article
to
| > reinstall SharePoint and companyweb:
| >
| > 829114 How to remove and how to install the Windows Small Business
Server
| > 2003 SharePoint Services Companyweb Web site
| > http://support.microsoft.com/?id=829114
| >
| > After that, please check if companyweb works.
| >
| > If yes, then let's focus on the WSUS issue:
| >
| > Based on current situation, I suggest you reinstall WSUS to see if it
| > works.
| >
| > The process can be time-consuming. Your time and effort will be
| > appreciated.
| >
| > For detailed steps, please follow the steps below:
| >
| > 1. Open Add/remove programs.
| > 2. Remove Windows Small Business Server 2003 R2.
| > 3. From IIS Manager, ensure following Virtual Directories are deleted:
| >
| > Selfupdate and UpdateServices under Default web site.
| >
| > Following directories under WSUS Administration:
| >
| > - ClientWebService
| > - Content
| > - DssAuthWebService
| > - ReportingWebService
| > - SelfUpdate
| > - ServerSyncWebService
| > - SimpleAuthebService
| > - WSUSAdmin
| >
| > 4. From IIS Manager, deleted the WSUSPool application pool
| > 5. Deleted the SUSDB database (C:\WSUS folder)
| > 6. Renamed %Program Files\Update Services folder
| > 7. Removed HKLM\Software\Microsoft\Update Services\ registry key and
| > subkeys
| > 8. Removed HKLM\System\CCS\Services\Update Services\ registry key and
| > subkeys
| > 9. Also ensured the following regkeys were not present:
| >
| > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft
Windows
| > Server Update Services Service Pack 1
| > HKLM\SYSTEM\CurrentControlSet\Services\WSUS: Client Web Service
| > HKLM\SYSTEM\CurrentControlSet\Services\WSUS: Client Web Service
Methods
| > HKLM\SYSTEM\CurrentControlSet\Services\WSUS: Reporting Web Service
| > HKLM\SYSTEM\CurrentControlSet\Services\WSUS: Server Web Methods
| > HKLM\SYSTEM\CurrentControlSet\Services\WSUS: Server Web Service
| > HKLM\SYSTEM\CurrentControlSet\Services\WsusService
| >
| > 10. Rebooted server
| >
| > 11. Insert SBS 2003 R2 CD 6 to reinstall Windows Small Business Server
R2.
| >
| > After that, please check the situation in a clean boot environment.
| >
| > 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: Thu, 13 Sep 2007 16:03:02 -0400
| > | Organization: Posted via Supernews, http://www.supernews.com
| > | Message-ID: <13ej5qtta9llr05@xxxxxxxxxxxxxxxxxx>
| > | References: <13dri6oq3ojq1fa@xxxxxxxxxxxxxxxxxx>
| > <BxZI3757HHA.360@xxxxxxxxxxxxxxxxxxxxxx>
| > <13edvn5gemokc4d@xxxxxxxxxxxxxxxxxx>
| > <CHzW8oT9HHA.5604@xxxxxxxxxxxxxxxxxxxxxx>
| > <13eg2k82t6ot21f@xxxxxxxxxxxxxxxxxx>
| > <mk9390g9HHA.5532@xxxxxxxxxxxxxxxxxxxxxx>
| > | 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: 821
| > | Path:
| >
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!news-out.
| >
cwix.com!newsfeed.cwix.com!newsfeed.stueberl.de!newsfeed.kamp.net!newsfeed.k
| >
amp.net!newsfeed.freenet.de!news.albasani.net!news.ecp.fr!club-internet.fr!f
| >
eedme-small.clubint.net!grolier!sn-xt-sjc-03!sn-xt-sjc-07!sn-post-sjc-01!sup
| > ernews.com!corp.supernews.com!not-for-mail
| > | Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.sbs:62805
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | All right. So I uninstalled WSS 3.0. I even went to the point of
| > removing
| > | "Intranet" from the SBS installation, then reinstalling it (had a
couple
| > | issues with that, but did eventually get through it). So now I'm
back
to
| > | having the web sites of "Default Web Site", "Microsoft SharePoint
| > | Administration", "WSUS Administration", "companyweb", and
"SharePoint
| > | Central Administration". So I decided to see if the companyweb is
| > working
| > | correctly. I can get to the default (http://servername), however, if
I
| > click
| > | on the "My Company's Internal Web Site" page, I first get prompted
to
| > log
| > | in. If I enter my normal username/password, it just again prompts me
to
| > | login. If I enter the administrator username/password, I get a page
that
| > | says, "Cannot complete this action. Please try again." Is this
related
| > to
| > | what I'm seeing and preventing the updates? What steps can I take to
| > resolve
| > | this?
| > |
| > | Also, I will email you the most recent entries from the
| > WindowsUpdate.log
| > of
| > | the client, as the messages are a bit different.
| > |
| > | Thanks for your continued help.
| > |
| > | Corey
| > |
| > |
| > | "Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in
message
| > | news:mk9390g9HHA.5532@xxxxxxxxxxxxxxxxxxxxxxxxx
| > | > Hello Corey,
| > | >
| > | > Thank you for taking time to reply.
| > | >
| > | > I would like to explain that to make WSUS work, SelfUpdate virtual
| > | > directory must be in a web site that listens to port 80. In SBS
R2,
| > | > selfupdate virtual directory is installed in WSS 2.0 Default web
site
| > by
| > | > defatul. It means default web site must be started if we want WSUS
to
| > | > work.
| > | >
| > | > In addition, since many SBS services depend on SharePoint 2.0, we
| > don't
| > | > recommend stopping SharePoint 2.0 default web site.
| > | >
| > | > I would like to confirm how did you install WSS 3.0 on the SBS
server?
| > | >
| > | > Please understand that we need to install WSS 3.0 side-by-side
with
| > | > Windows
| > | > SharePoint Services 2.0
| > | >
| > | > To resolve the problem thoroughly, I think we'd better reinstall
WSS
| > 3.0
| > | > first.
| > | >
| > | > Please remove WSS 3.0 and then refer to following article to
reinstall
| > it:
| > | >
| > | > Installing Windows SharePoint Services 3.0 on a Server Running
Windows
| > | > Small Business Server 2003
| > | >
| >
http://www.microsoft.com/downloads/details.aspx?FamilyID=0daafc81-efff-4f5b-
| > | > a28a-8265f1e99f5b&displaylang=en
| > | >
| > | > I am sorry for the inconvenience that you may experience.
| > | >
| > | > 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: Wed, 12 Sep 2007 11:49:39 -0400
| > | > | Organization: Posted via Supernews, http://www.supernews.com
| > | > | Message-ID: <13eg2k82t6ot21f@xxxxxxxxxxxxxxxxxx>
| > | > | References: <13dri6oq3ojq1fa@xxxxxxxxxxxxxxxxxx>
| > | > <BxZI3757HHA.360@xxxxxxxxxxxxxxxxxxxxxx>
| > | > <13edvn5gemokc4d@xxxxxxxxxxxxxxxxxx>
| > | > <CHzW8oT9HHA.5604@xxxxxxxxxxxxxxxxxxxxxx>
| > | > | 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: 605
| > | > | Path:
| > | >
| >
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!news-out.
| > | >
| >
cwix.com!newsfeed.cwix.com!newsfeed.stueberl.de!newsfeed.kamp.net!newsfeed.k
| > | >
| >
amp.net!81.171.88.16.MISMATCH!eweka.nl!hq-usenetpeers.eweka.nl!proxad.net!fe
| > | >
| >
eder1-1.proxad.net!club-internet.fr!feedme-small.clubint.net!grolier!sn-xt-s
| > | >
| >
jc-03!sn-xt-sjc-07!sn-post-sjc-01!supernews.com!corp.supernews.com!not-for-m
| > | > ail
| > | > | Xref: TK2MSFTNGHUB02.phx.gbl
| > microsoft.public.windows.server.sbs:62464
| > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > | > |
| > | > | Thanks for the suggestions. Here are my responses:
| > | > |
| > | > | Suggestion 1:
| > | > | It was already set to Granted access.
| > | > |
| > | > | Suggestion 2:
| > | > | Those were the ports already, and the path was correct. I
verified
| > the
| > | > | security settings as well.
| > | > |
| > | > | Suggestion 3:
| > | > | I did as you indicated. The client still fails to report.
However,
| > the
| > | > code
| > | > | in the WindowsUpdate.log file is now 0x800710dd. What does this
code
| > | > mean?
| > | > |
| > | > | I will hold off on the logging, as I don't want to continue to
| > download
| > | > and
| > | > | install a bunch of exploratory applications. I will point out
again
| > that
| > | > the
| > | > | Default Web Site is already stopped, since it listens on the
same
| > port
| > | > as
| > | > | SharePoint. However, I did try stopping SharePoint and having
the
| > | > Default
| > | > | Web Site running, and still got the same issue.
| > | > |
| > | > | Thanks.
| > | > |
| > | > | Corey
| > | > |
| > | > |
| > | > | "Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in
| > message
| > | > | news:CHzW8oT9HHA.5604@xxxxxxxxxxxxxxxxxxxxxxxxx
| > | > | > 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
| > | > | > | > |
| > | > | > | > |
| > | > | > | > |
| > | > | > | >
| > | > | > |
| > | > | > |
| > | > | > |
| > | > | >
| > | > |
| > | > |
| > | > |
| > | >
| > |
| > |
| > |
| >
|
|
|



.