Re: SBS 2003 will not update

Hi,

Thanks for that. I think things are fixed now. I was not aware that we had a
proxy server set up. When I used the proxycfg utility I found that we had a
proxy left over from when our ISP was BT. It was still pointing to the BT
server. I have now deleted thtis with "proxycfg -d" and all is OK.

Thanks for all your help.

Regards,

Vic
"MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx> wrote in message
news:Ow9uB4HAIHA.4592@xxxxxxxxxxxxxxxxxxxxxxx
Vic,

Did you register the files from a Command Prompt after stopping the AU
Service ? If yes ...
It has to be a proxy or firewall issue if the WUA is now updated to the
latest version. From http://support.microsoft.com/kb/317541 :

The Update Root Certificates component uses the WinHTTP API to
communicate with the Windows Update server. If your computer is behind a
proxy server, you may have to set the proxy settings by using the
Proxycfg.exe utility. To configure WinHTTP by using Proxycfg.exe, follow
these steps:

I'm not familiar with McAfee TPE nor Watchguard. Perhaps the files that
were updated are being blocked from accessing the update servers.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Vic Russell wrote:

Hi,

Somehow the files that I reported as being at version 374 have now been
updated. I have also re-registered all the files that you listed. I also
uninstalled the "Update Root Certificates" Windows component. Still no
luck with getting Windows updated. I still get error 0x80072EFD.

I have now re-installed "Update Root Certificates".

Our AV is McAfee Total Protection Enterprise. We have another system that
is set up exactly the same as far as I can see and that system (also
SBS2003 SP2) is fine.

Both systems are protected by Watchguard Fireboxes and are set up pretty
much the same (one is a few years older). In any case, nothing has
changed on the Firebox that corresponds with the updates starting to
fail.

Have you any more suggestions please?

Kind regards,

Vic
"MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx> wrote in message
news:uFA0kW7$HHA.5488@xxxxxxxxxxxxxxxxxxxxxxx

The following KB shows an App log error that is *almost* exactly same as
the one you posted, Vic -

Event ID 8 is logged in the Application log
http://support.microsoft.com/kb/317541

That should shed some light on the issue.
Is the installed AV different and/or is it configured differently on this
system ?
The files you posted that were not updated may be what's causing the
failure to communicate with the update servers making it appear as
thought it's a proxy issue.


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Vic Russell wrote:


Another clue. Our Application Log has loads of these errors:-

Event Type: Error
Event Source: crypt32
Event Category: None
Event ID: 8
Date: 25/09/2007
Time: 13:00:18
User: N/A
Computer: PI-109
Description:
Failed auto update retrieval of third-party root list sequence number
from:
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt>
with error: The specified server cannot perform the requested operation.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Regards,

Vic

"Vic Russell" <nospam@xxxxxxxxxx> wrote in message
news:uqdIuV0$HHA.4584@xxxxxxxxxxxxxxxxxxxxxxx


Hi,

Thanks for that. When I use IE7 to visit Windows Update I get the
0x80072EFD error.

I have checked the versions of the files you list andb wuapi, wups and
wups2 are stll at version V.7.0.6000.374 (all the rest are 381). I
suppose this may well be the problem but I cannot find how to get them
updated. I tried installing Microsoft Update as opposed to Windows
Update but to no avail - the same error occurs.

Anything else I can try? How do I update the old dll's?

Vic

"MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx> wrote in message
news:ugJM9yt$HHA.1188@xxxxxxxxxxxxxxxxxxxxxxx


Is the problematic server using Automatic Updates ?
Did you try using IE to visit Windows Update to see what the result
was?

0x80072EFD means that the system can not connect to the update
servers.
That might be because the Windows Update Agent/Client is stuck on the
previous version.
Check the Version of wuaueng.dll to see if it's now at V.7.0.6000.381
These files must also be at that Version level now -

cdm.dll
wuapi.dll
wuauclt.exe
wuaucpl.cpl
wuaueng.dll
wucltui.dll
wups.dll
wups2.dll
wuweb.dll

If they are, you may need to register these .dlls from a Command
Prompt, pressing Enter after each command, to restore connectivity to
the update servers

net stop wuauserv
regsvr32 wuapi.dll
regsvr32 wuaueng.dll
regsvr32 wucltui.dll
regsvr32 wups.dll
regsvr32 wups2.dll
regsvr32 wuweb.dll
net start wuauserv
exit

Reboot and see if that resolves the error.
IF all of the above files are still at V. 7.0.6000.374, then see if
using IE to visit WU gets the latest Version installed.

If the above is not the issue, then it's proxy config related:

How the Windows Update client determines which proxy server to use to
connect to the Windows Update Web site
http://support.microsoft.com/kb/900935


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Vic Russell wrote:



Hi,

Our network has an Small Business Server 2003 SP2 and this machine is
failing to get windows updates and reports Error 0x80072EFD

I have checked the Trusted sites and all the suggested ones have been
included. Another suggestion from the trobleshooter was to update the
Proxy/Firewall settings. Our firewall is an external box which is
common to the whole network and all the other machines (all XP) are
updating OK - it is just the SBS2003 machine.

We had this problem once before and I downloaded Windows 2003 SP2,
installed it and then updates worked OK - and now they have stopped
again. We have another seperate system (SBS2003 SP2 based) with a
watchguard firewall (same as here) and all is OK.

It would seem that the problem lies somewhere in the SBS2003 system.
Has anyone got any ideas?

Regards,

Vic





.

Relevant Pages

  • Re: SBS 2003 will not update
    ... Vic Russell wrote: ... I was not aware that we had a proxy server set up. ... When I used the proxycfg utility I found that we had a proxy left over from when our ISP was BT. ... When I use IE7 to visit Windows Update I get the 0x80072EFD error. ...
    (microsoft.public.windowsupdate)
  • Re: Vista, check for updates disabled, WU GPO not set, updates failing
    ... Either the proxy server or target server name can not be resolved. ... can add static IP entries for the Windows Update Web site or for the Microsoft Update Web site to your Hosts file. ... Sidebar shows stock tickers and weather (through proxy, using authentication). ...
    (microsoft.public.windowsupdate)
  • Re: ISA Server Problems, please help
    ... Based on the rules you have listed, SecureNAT clients should only be allowed ... The All access rule for SBS Internet Users ... Web Proxy and/or Firewall Client ... > header to the publishing server instead of the actual one. ...
    (microsoft.public.windows.server.sbs)
  • RE: 0x8024402C is driving me absolutely crazy!
    ... Workstations are running XP Pro SP2 with Winsock Proxy Client. ... Server is running NT4. ... Then I tried windows update again. ...
    (microsoft.public.windowsupdate)
  • RE: Simple ISA 2004 questions
    ... You'd better create a new GPO for IE proxy, ... Run "gpmc.msc" in SBS server, ... ISA Server 2004 Query can give you some help. ... In the Microsoft Internet Security and Acceleration Server 2004 console, ...
    (microsoft.public.windows.server.sbs)