Go Back   TechArena Community > Technical Support > Computer Help > Windows XP > Windows Update
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



WSUS 3.0 SP1 - computers have not reported status yet

Windows Update


Reply
 
Thread Tools Search this Thread
  #31  
Old 07-10-2008
Bob
 
Posts: n/a
Re: WSUS 3.0 SP1 - computers have not reported status yet



"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> > I will un-install then re-install on the same server still to a custom port
> > not 80. Can you tell me if there is anything I should check after the
> > un-install, maybe check for any directories that may be left behind ?

>
> I'm not sure about this one. I think if the uninstall doesn't produce any error
> messages, anything that has been left behind shouldn't cause problems.
>
> > How about SP1 - good idea to install it, as I read about it causing problems ?

>
> I'd stick with it, at least for now. (I'm not sure you've got a choice, I don't
> recall offhand whether the RTM version is still available for download.)
>
> Harry.
>

Thanks again --- I will un-install/re-install Tuesday and hopefully (my
fingers are crossed), all will be ok this time. I will report back in 1 or 2
days.

Bob

Reply With Quote
  #32  
Old 07-10-2008
Bob
 
Posts: n/a
Re: WSUS 3.0 SP1 - computers have not reported status yet



"Bob" wrote:

>
>
> "Harry Johnston [MVP]" wrote:
>
> > Bob wrote:
> >
> > > I will un-install then re-install on the same server still to a custom port
> > > not 80. Can you tell me if there is anything I should check after the
> > > un-install, maybe check for any directories that may be left behind ?

> >
> > I'm not sure about this one. I think if the uninstall doesn't produce any error
> > messages, anything that has been left behind shouldn't cause problems.
> >
> > > How about SP1 - good idea to install it, as I read about it causing problems ?

> >
> > I'd stick with it, at least for now. (I'm not sure you've got a choice, I don't
> > recall offhand whether the RTM version is still available for download.)
> >
> > Harry.
> >

> Thanks again --- I will un-install/re-install Tuesday and hopefully (my
> fingers are crossed), all will be ok this time. I will report back in 1 or 2
> days.
>
> Bob
>


Ok - I'm back ---- I did the following ---

I downloaded WSUS 3 SP1 off the WSUS home page as the version i previously
had did not include SP1, I needed do download Sp1 seperately.

I uninstalled my previous version, removed all logs/downloads, etc... I
wanted a clean un-install.

Then I installed to a custom port 8530, after the install I went to IIS,
websites, WSUS Administration, opened it and I don't see "Selfupdate". I
remember previously that past articles said to install a new virtual
directory/label it Selfupdate. Must I create a new virtual directoty since
Selfupdate does not exist in IIS ?


Also -- I searched my volumes and there is no selfupdate.msi


I checked the following path and found ----


c:\program files\updateservices\selfupdate ---- inside the selfupdate folder
I have --
AU and WSUS3 folders, along with iuident.cab and wuident.cab


Can I be guided as to my status here, is there still a problem with no
selfupdate virtual directory, must i create one ?


Thanks for the help,
Bob

Reply With Quote
  #33  
Old 07-10-2008
Harry Johnston [MVP]
 
Posts: n/a
Re: WSUS 3.0 SP1 - computers have not reported status yet

Bob wrote:

> Then I installed to a custom port 8530, after the install I went to IIS,
> websites, WSUS Administration, opened it and I don't see "Selfupdate". I
> remember previously that past articles said to install a new virtual
> directory/label it Selfupdate. Must I create a new virtual directoty since
> Selfupdate does not exist in IIS ?


Yes. At least this time the folder it needs to point to is present.

> Also -- I searched my volumes and there is no selfupdate.msi


Is there a folder c:\Program Files\Update Services\Setup? That's where
Selfupdate.msi ought to be.

Harry.
Reply With Quote
  #34  
Old 09-10-2008
Bob
 
Posts: n/a
Re: WSUS 3.0 SP1 - computers have not reported status yet



"Harry Johnston [MVP]" wrote:

> Bob wrote:
>
> > I will un-install then re-install on the same server still to a custom port
> > not 80. Can you tell me if there is anything I should check after the
> > un-install, maybe check for any directories that may be left behind ?

>
> I'm not sure about this one. I think if the uninstall doesn't produce any error
> messages, anything that has been left behind shouldn't cause problems.
>
> > How about SP1 - good idea to install it, as I read about it causing problems ?

>
> I'd stick with it, at least for now. (I'm not sure you've got a choice, I don't
> recall offhand whether the RTM version is still available for download.)
>
> Harry.
>


Here is the latest as of Thursday October 9th ---

All of my desktops/servers have reported in to WSUS !, I even
released/installed updates from September on my test group and all is ok. But
------

My 2 Domain Controllers are not reporting in - when I go to my "servers"
group in WSUS their host names are there but no IP, OS is Windows 0.0, no
installed, and no last status report. They are the only two systems not
cooperating. Can i get some assistance as to why just those 2 D/C's are not
communicating with WSUS/how i can troubleshoot ?

Thank you,
Bob

Reply With Quote
  #35  
Old 31-10-2008
khanman22
 
Posts: n/a
Re: WSUS 3.0 SP1 - computers have not reported status yet

Hello all,

I have same problem. My WSUS server crashed, so I reinstalled it on a new
server and named that server the same as the old one. all my clients show up
after i brought the new server up, but 99% of them say "not reported yet".

"Bob" wrote:

>
>
> "PA Bear [MS MVP]" wrote:
>
> > Bob wrote:
> > >> "Harry Johnston [MVP]" wrote:
> > >>> Bob wrote:
> > >>>> All of the systems show ---- last report status - not yet reported.
> > >>>
> > >>> Let's start with the Client Diagnostics Tool:
> > >>>
> > >>> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
> > >>>
> > >>> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
> > >>>
> > >>> Run it on one of the affected clients and post the results. Then type
> > >>>
> > >>> wuauclt /detectnow
> > >>>
> > >>> on the same client, wait thirty minutes, then post the last fifty lines
> > >>> from WindowsUpdate.log.
> > >>>
> > > Here is the reply of the client diagnostic tool, which I ran on my
> > > desktop.
> > > I will now do the wuauclt/detectnow and post back in 30 minutes are
> > > requested.
> > >
> > > 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
> > > Wuaueng.dll version 7.1.6001.65 . . . . . . . . . . . . PASS
> > > This version is WSUS 2.0
> > >
> > > Checking AU Settings
> > > AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
> > > Option is from Policy settings
> > >
> > > Checking Proxy Configuration
> > > Checking for winhttp local machine Proxy settings . . . PASS
> > > Winhttp local machine access type
> > > <Direct Connection>
> > > Winhttp local machine Proxy. . . . . . . . . . NONE
> > > Winhttp local machine ProxyBypass. . . . . . . NONE
> > > Checking User IE Proxy settings . . . . . . . . . . . . PASS
> > > User IE Proxy. . . . . . . . . . . . . . . . . NONE
> > > User IE ProxyByPass. . . . . . . . . . . . . . NONE
> > > User IE AutoConfig URL Proxy . . . . . . . . . NONE
> > > User IE AutoDetect
> > > AutoDetect not in use
> > >
> > > Checking Connection to WSUS/SUS Server
> > > WUServer = http://intranet1:8530
> > > WUStatusServer = http://intranet1:8530
> > > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> > > Connection to server. . . . . . . . . . . . . . . . . . PASS
> > >
> > > WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
> > > &downloadBuffe
> > > r) failed with hr=0x80190194
> > >
> > > No Error description could be found

> >
> > <kibbitz>
> > 0x80244019 - SUS_E_PT_HTTP_STATUS_NOT_FOUND - Http status 404 - object not
> > found.
> >
> > Random Musings of Jeremy Jameson : WSUS Clients Failing with Error
> > 0x80244019 After Installing WSUS SP1:
> > http://blogs.msdn.com/jjameson/archi...-wsus-sp1.aspx
> >
> > Error 0x80244019 in WindowsUpdate.log - PatchAholic...The WSUS Blog!:
> > http://msmvps.com/blogs/athif/archiv...x80244019.aspx
> > </kibbitz>
> > --
> > ~PA Bear
> >
> >

>
> I did setup a new virtual directory in WSUS in IIS, called it selfupdate,
> left the permission to the default - read, stopped/restarted IIS, ran wuauclt
> /detectnow and still did not work. Please see the log below --
>
> Thanks,
> Bob
>
>
> 2008-09-30 17:15:38:525 1088 e34 AU Triggering AU detection through
> DetectNow API
> 2008-09-30 17:15:38:525 1088 e34 AU Triggering Online detection
> (non-interactive)
> 2008-09-30 17:15:38:525 1088 168 AU #############
> 2008-09-30 17:15:38:525 1088 168 AU ## START ## AU: Search for updates
> 2008-09-30 17:15:38:525 1088 168 AU #########
> 2008-09-30 17:15:38:525 1088 168 AU <<## SUBMITTED ## AU: Search for updates
> [CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
> 2008-09-30 17:15:38:525 1088 130c Agent *************
> 2008-09-30 17:15:38:525 1088 130c Agent ** START ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2008-09-30 17:15:38:525 1088 130c Agent *********
> 2008-09-30 17:15:38:541 1088 130c Agent * Online = Yes; Ignore download
> priority = No
> 2008-09-30 17:15:38:541 1088 130c 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"
> 2008-09-30 17:15:38:541 1088 130c Agent * ServiceID =
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
> 2008-09-30 17:15:38:541 1088 130c Misc Validating signature for
> C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
> 2008-09-30 17:15:38:541 1088 130c Misc Microsoft signed: Yes
> 2008-09-30 17:15:38:556 1088 130c Misc WARNING: WinHttp:
> SendRequestToServerForFileInformation failed with 0x80190194
> 2008-09-30 17:15:38:556 1088 130c Misc WARNING: WinHttp:
> ShouldFileBeDownloaded failed with 0x80190194
> 2008-09-30 17:15:38:556 1088 130c Misc WARNING: DownloadFileInternal failed
> for http://intranet1:8530/selfupdate/wuident.cab: error 0x80190194
> 2008-09-30 17:15:38:556 1088 130c Setup FATAL: IsUpdateRequired failed with
> error 0x80244019
> 2008-09-30 17:15:38:556 1088 130c Setup WARNING: SelfUpdate: Default
> Service: IsUpdateRequired failed: 0x80244019
> 2008-09-30 17:15:38:556 1088 130c Setup WARNING: SelfUpdate: Default
> Service: IsUpdateRequired failed, error = 0x80244019
> 2008-09-30 17:15:38:556 1088 130c Agent * WARNING: Skipping scan,
> self-update check returned 0x80244019
> 2008-09-30 17:15:39:197 1088 130c Agent * WARNING: Exit code = 0x80244019
> 2008-09-30 17:15:39:197 1088 130c Agent *********
> 2008-09-30 17:15:39:197 1088 130c Agent ** END ** Agent: Finding updates
> [CallerId = AutomaticUpdates]
> 2008-09-30 17:15:39:197 1088 130c Agent *************
> 2008-09-30 17:15:39:197 1088 130c Agent WARNING: WU client failed Searching
> for update with error 0x80244019
> 2008-09-30 17:15:39:197 1088 107c AU >>## RESUMED ## AU: Search for
> updates [CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
> 2008-09-30 17:15:39:197 1088 107c AU # WARNING: Search callback failed,
> result = 0x80244019
> 2008-09-30 17:15:39:197 1088 107c AU # WARNING: Failed to find updates
> with error code 80244019
> 2008-09-30 17:15:39:197 1088 107c AU #########
> 2008-09-30 17:15:39:197 1088 107c AU ## END ## AU: Search for updates
> [CallId = {F4F88A9E-1B71-41E2-9DBF-4B8E5D178A04}]
> 2008-09-30 17:15:39:197 1088 107c AU #############
> 2008-09-30 17:15:39:197 1088 107c AU AU setting next detection timeout to
> 2008-10-01 02:15:39
> 2008-09-30 17:15:43:556 1088 130c Report REPORT EVENT:
> {37C62D47-0C99-4BEF-ABE6-9D2712BB8850} 2008-09-30
> 17:15:38:556-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80244019 SelfUpdate Failure Software
> Synchronization Windows Update Client failed to detect with error 0x80244019.
> 2008-09-30 17:25:58:353 1088 130c PT WARNING: Cached cookie has expired or
> new PID is available
> 2008-09-30 17:25:58:353 1088 130c PT Initializing simple targeting cookie,
> clientId = 1f86fbe4-b2fd-4ab9-89d2-0b217057c785, target group = TEST, DNS
> name = bobp.amalgamated.com
> 2008-09-30 17:25:58:353 1088 130c PT Server URL =
> http://intranet1:8530/SimpleAuthWebS...impleAuth.asmx
> 2008-09-30 17:25:58:384 1088 130c Report Uploading 1 events using cached
> cookie, reporting URL =
> http://intranet1:8530/ReportingWebSe...ebService.asmx
> 2008-09-30 17:25:58:384 1088 130c Report Reporter successfully uploaded 1
> events.
>

Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows XP > Windows Update
Tags: , , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "WSUS 3.0 SP1 - computers have not reported status yet"
Thread Thread Starter Forum Replies Last Post
Most WSUS clients show status 'Not yet reported' purvagarg Server Update Service 3 07-01-2014 09:47 AM
WSUS 3.0 client computers not populating WSUS console Hardik Active Directory 4 25-09-2009 01:05 PM
This Computer has not reported status yet bzumwalt99 Windows Update 34 19-08-2008 01:14 AM
clients not reporting status after updating WSUS 2 to WSUS 3.0 Dhananjay Server Update Service 4 17-07-2007 09:37 PM
WSUS 3.0 Many Updates with no status AngerEyes Server Update Service 4 11-05-2007 05:17 AM


All times are GMT +5.5. The time now is 03:07 PM.