Re: Error number: 0x8007045A
From: Martin Church (MartinChurch_at_discussions.microsoft.com)
Date: 09/17/04
- Next message: SMI: "RE: Windows Update getting error"
- Previous message: Tony Vaughan: "RE: Error 0x8007045A - Have MS Closed for Business??"
- In reply to: Tony Vaughan: "Re: Error number: 0x8007045A"
- Next in thread: Tony Vaughan: "Re: Error number: 0x8007045A"
- Reply: Tony Vaughan: "Re: Error number: 0x8007045A"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 06:37:09 -0700
That's what I have discovered so far. I remember something at a technet
event where they said a server could be setup to require all client
workstations to meet certain requirements. this could also include the same
time. but this is only a guess.
"Tony Vaughan" wrote:
> Hi Martin
>
> Have I got this right? Are you saying that if you sync your workstation with
> an internet time server, rather that your SBS 2003 server, Windows Update 5
> works? Otherwise, you get the 0x8007045A.
>
> What on earth could time have to do with windows update?
>
> Interesting though.
>
> Tony
>
> "Martin Church" wrote:
>
> > I have been doing some further testing, and I think I have found the problem.
> > But not the solution. The problem is time sync. I took one of my laptops
> > off the network domain and let it auto etect the correct time from the time
> > server in windows. The program ran fine. Now I have to figure out how to
> > sync the time between my client stations, my SBS 2003 Server and Microsoft
> > Udate server.
> >
> > Any suggestions.
> >
> > "Tony Vaughan" wrote:
> >
> > > Hi Torgeir
> > >
> > > Would you please send me your e-mail address and I'll send you the same log
> > > file I sent to Danial Chow.
> > >
> > > My e-mail address is tony.vaughan@safehelp.com.
> > >
> > > I look forward to hearing from you.
> > >
> > > Tony
> > >
> > > "Torgeir Bakken (MVP)" wrote:
> > >
> > > > Tony Vaughan wrote:
> > > >
> > > > > Hi Torgeir
> > > > >
> > > > > It seems to me that their is a common factor in many of the messages
> > > > > reporting this error, namely SBS 2003.
> > > > >
> > > > > I've tried all the remedies you have suggested without reward.
> > > > >
> > > > > This leads me to wonder what SBS 2003 is doing when a client machine tries
> > > > > to access Windows Update.
> > > > >
> > > > > I suggest that, in order to maintain your credibility, you refrain from
> > > > > recommending the registration solution or the XML Parser solution, because
> > > > > they have absolutely no effect on this problem.
> > > > >
> > > > > I sympathise with your position, because there are many people affected by
> > > > > this bug and they are angry as am I. So please pass up the line how serious
> > > > > this problem is.
> > > > Hi
> > > >
> > > > Yes, I see some SBS references on some of the posts, so you might
> > > > very well be right on that one.
> > > >
> > > > As far as I can find out, Wayne Morgan is the only one that have been
> > > > able to fix the error (by renaming wu*.dll and wu*.exe to get the WU
> > > > controls reloaded), but that didn't work for you, so it might be two
> > > > different causes for this problem.
> > > >
> > > >
> > > > Lets hope Daniel Chow [MSFT] can find out something from your
> > > > WindowsUpdate.log :-)
> > > >
> > > > Could you please send the WindowsUpdate.log file to me also, as well
> > > > as %windir%\SoftwareDistribution\ReportingEvents.log, so I can have
> > > > a look at them, and it is also good to have it for future reference
> > > > (remove -spam before sending).
> > > >
> > > >
> > > > --
> > > > torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> > > > Administration scripting examples and an ONLINE version of
> > > > the 1328 page Scripting Guide:
> > > > http://www.microsoft.com/technet/scriptcenter/default.mspx
> > > >
- Next message: SMI: "RE: Windows Update getting error"
- Previous message: Tony Vaughan: "RE: Error 0x8007045A - Have MS Closed for Business??"
- In reply to: Tony Vaughan: "Re: Error number: 0x8007045A"
- Next in thread: Tony Vaughan: "Re: Error number: 0x8007045A"
- Reply: Tony Vaughan: "Re: Error number: 0x8007045A"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|