[Adam Bertram]

I am using the new Microsoft Update on all (~20) customers' servers and
have had no problem, but this one does not want to cooperate. It is a
SBS2K3 server. Whenever I try to search for updates, it gives me the error
message, "The website has encountered a problem and cannot display the page
you are trying to view. The options provided below might help you solve
the problem". Error Number [0x80072EE7].

I have learned that this error number isn't that prevalent and the only fix
I have seen thus far is something related to the hosts file or DNS. I have
checked the hosts file and nothing is in there except the localhost stuff
and DNS seems to be behaving correctly.

Any clues?

[Zeb Mullen [MSFT]]

Are these machines behind a Firewall?

--
Zeb Mullen
Microsoft Corporation
Windows Update Services

======================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================

"Adam Bertram" <abertram@idatatech.net> wrote in message
news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>I am using the new Microsoft Update on all (~20) customers' servers and
> have had no problem, but this one does not want to cooperate. It is a
> SBS2K3 server. Whenever I try to search for updates, it gives me the
> error
> message, "The website has encountered a problem and cannot display the
> page
> you are trying to view. The options provided below might help you solve
> the problem". Error Number [0x80072EE7].
>
> I have learned that this error number isn't that prevalent and the only
> fix
> I have seen thus far is something related to the hosts file or DNS. I
> have
> checked the hosts file and nothing is in there except the localhost stuff
> and DNS seems to be behaving correctly.
>
> Any clues?

[Adam Bertram]

"Zeb Mullen [MSFT]" <zebm@online.microsoft.com> wrote in
news:uqKL3HAeFHA.3712@TK2MSFTNGP12.phx.gbl:

> Are these machines behind a Firewall?
>

Yes, this is just 1 server and it is behind a firewall, however, all of the
other servers are also behind firewalls and they work just fine.

[Zeb Mullen [MSFT]]

Is this the only SBS server in the group or are there others?

--
Zeb Mullen
Microsoft Corporation
Windows Update Services

======================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================

"Adam Bertram" <abertram@idatatech.net> wrote in message
news:Xns967E63F8168D3abertramidatatechnet@207.46.248.16...
> "Zeb Mullen [MSFT]" <zebm@online.microsoft.com> wrote in
> news:uqKL3HAeFHA.3712@TK2MSFTNGP12.phx.gbl:
>
>> Are these machines behind a Firewall?
>>
>
> Yes, this is just 1 server and it is behind a firewall, however, all of
> the
> other servers are also behind firewalls and they work just fine.

[Danny Sanders]

Had the same problem, saw the same article, rem the local host and it
updated. The article talks about having windows update in the host file with
a bad IP address. The machines I worked with only had two entries and
nothing to do with windows update. By rem (ing) out those entries I was able
to update.
FYI
To rem an entry just put a "#" before the line.


hth
DDS W 2k MVP MCSE

"Adam Bertram" <abertram@idatatech.net> wrote in message
news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>I am using the new Microsoft Update on all (~20) customers' servers and
> have had no problem, but this one does not want to cooperate. It is a
> SBS2K3 server. Whenever I try to search for updates, it gives me the
> error
> message, "The website has encountered a problem and cannot display the
> page
> you are trying to view. The options provided below might help you solve
> the problem". Error Number [0x80072EE7].
>
> I have learned that this error number isn't that prevalent and the only
> fix
> I have seen thus far is something related to the hosts file or DNS. I
> have
> checked the hosts file and nothing is in there except the localhost stuff
> and DNS seems to be behaving correctly.
>
> Any clues?

[danska629]

what would you "rem" ?there seems to be nothing visible that I can attach a
"rem"
to, I am trying to download a windows update from their site and it
would'nt take,
what can I do ?

"Danny Sanders" wrote:

> Had the same problem, saw the same article, rem the local host and it
> updated. The article talks about having windows update in the host file with
> a bad IP address. The machines I worked with only had two entries and
> nothing to do with windows update. By rem (ing) out those entries I was able
> to update.
> FYI
> To rem an entry just put a "#" before the line.
>
>
> hth
> DDS W 2k MVP MCSE
>
> "Adam Bertram" <abertram@idatatech.net> wrote in message
> news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
> >I am using the new Microsoft Update on all (~20) customers' servers and
> > have had no problem, but this one does not want to cooperate. It is a
> > SBS2K3 server. Whenever I try to search for updates, it gives me the
> > error
> > message, "The website has encountered a problem and cannot display the
> > page
> > you are trying to view. The options provided below might help you solve
> > the problem". Error Number [0x80072EE7].
> >
> > I have learned that this error number isn't that prevalent and the only
> > fix
> > I have seen thus far is something related to the hosts file or DNS. I
> > have
> > checked the hosts file and nothing is in there except the localhost stuff
> > and DNS seems to be behaving correctly.
> >
> > Any clues?
>
>
>

[Danny Sanders]

Rem *any* line that is not already rem (ed)

If there is an entry for local host rem that line, save, then test. You can
change it back and resave it later.

hth
DDS W 2k MVP MCSE

"danska629" <danska629@discussions.microsoft.com> wrote in message
news:A05DD23E-5DDF-4745-B895-8070820F208F@microsoft.com...
> what would you "rem" ?there seems to be nothing visible that I can attach
> a
> "rem"
> to, I am trying to download a windows update from their site and it
> would'nt take,
> what can I do ?
>
> "Danny Sanders" wrote:
>
>> Had the same problem, saw the same article, rem the local host and it
>> updated. The article talks about having windows update in the host file
>> with
>> a bad IP address. The machines I worked with only had two entries and
>> nothing to do with windows update. By rem (ing) out those entries I was
>> able
>> to update.
>> FYI
>> To rem an entry just put a "#" before the line.
>>
>>
>> hth
>> DDS W 2k MVP MCSE
>>
>> "Adam Bertram" <abertram@idatatech.net> wrote in message
>> news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>> >I am using the new Microsoft Update on all (~20) customers' servers and
>> > have had no problem, but this one does not want to cooperate. It is a
>> > SBS2K3 server. Whenever I try to search for updates, it gives me the
>> > error
>> > message, "The website has encountered a problem and cannot display the
>> > page
>> > you are trying to view. The options provided below might help you
>> > solve
>> > the problem". Error Number [0x80072EE7].
>> >
>> > I have learned that this error number isn't that prevalent and the only
>> > fix
>> > I have seen thus far is something related to the hosts file or DNS. I
>> > have
>> > checked the hosts file and nothing is in there except the localhost
>> > stuff
>> > and DNS seems to be behaving correctly.
>> >
>> > Any clues?
>>
>>
>>

[Adam Bertram]

"Danny Sanders" <Danny.Sanders@NO-SPAMcpcmed.org> wrote in
news:#m36wrAeFHA.688@TK2MSFTNGP14.phx.gbl:

> Had the same problem, saw the same article, rem the local host and it
> updated. The article talks about having windows update in the host
> file with a bad IP address. The machines I worked with only had two
> entries and nothing to do with windows update. By rem (ing) out those
> entries I was able to update.
> FYI
> To rem an entry just put a "#" before the line.
>
>
> hth
> DDS W 2k MVP MCSE
>
> "Adam Bertram" <abertram@idatatech.net> wrote in message
> news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>>I am using the new Microsoft Update on all (~20) customers' servers
>>and
>> have had no problem, but this one does not want to cooperate. It is
>> a SBS2K3 server. Whenever I try to search for updates, it gives me
>> the error
>> message, "The website has encountered a problem and cannot display
>> the page
>> you are trying to view. The options provided below might help you
>> solve the problem". Error Number [0x80072EE7].
>>
>> I have learned that this error number isn't that prevalent and the
>> only fix
>> I have seen thus far is something related to the hosts file or DNS.
>> I have
>> checked the hosts file and nothing is in there except the localhost
>> stuff and DNS seems to be behaving correctly.
>>
>> Any clues?
>
>

Interesting. I'll try that.

[Adam Bertram]

Adam Bertram <abertram@idatatech.net> wrote in
news:Xns967E8A2DA91A9abertramidatatechnet@207.46.248.16:

> "Danny Sanders" <Danny.Sanders@NO-SPAMcpcmed.org> wrote in
> news:#m36wrAeFHA.688@TK2MSFTNGP14.phx.gbl:
>
>> Had the same problem, saw the same article, rem the local host and it
>> updated. The article talks about having windows update in the host
>> file with a bad IP address. The machines I worked with only had two
>> entries and nothing to do with windows update. By rem (ing) out those
>> entries I was able to update.
>> FYI
>> To rem an entry just put a "#" before the line.
>>
>>
>> hth
>> DDS W 2k MVP MCSE
>>
>> "Adam Bertram" <abertram@idatatech.net> wrote in message
>> news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>>>I am using the new Microsoft Update on all (~20) customers' servers
>>>and
>>> have had no problem, but this one does not want to cooperate. It is
>>> a SBS2K3 server. Whenever I try to search for updates, it gives me
>>> the error
>>> message, "The website has encountered a problem and cannot display
>>> the page
>>> you are trying to view. The options provided below might help you
>>> solve the problem". Error Number [0x80072EE7].
>>>
>>> I have learned that this error number isn't that prevalent and the
>>> only fix
>>> I have seen thus far is something related to the hosts file or DNS.
>>> I have
>>> checked the hosts file and nothing is in there except the localhost
>>> stuff and DNS seems to be behaving correctly.
>>>
>>> Any clues?
>>
>>
>
> Interesting. I'll try that.
>

Well, it was a good try, I guess. The only entry in the hosts file was
127.0.0.0 localhost. I REMed it out and it didn't matter. :(

[Robert Aldwinckle]

"Adam Bertram" <abertram@idatatech.net> wrote in message news:Xns967E59F65194Aabertramidatatechnet@207.46.248.16...
>I am using the new Microsoft Update on all (~20) customers' servers and
> have had no problem, but this one does not want to cooperate. It is a
> SBS2K3 server. Whenever I try to search for updates, it gives me the error
> message, "The website has encountered a problem and cannot display the page
> you are trying to view. The options provided below might help you solve
> the problem". Error Number [0x80072EE7].
>
> I have learned that this error number isn't that prevalent and the only fix
> I have seen thus far is something related to the hosts file or DNS. I have
> checked the hosts file and nothing is in there except the localhost stuff
> and DNS seems to be behaving correctly.
>
> Any clues?


So, I guess you only searched on the KB?

Try searching with Google Groups or the web interface to newsgroups
too?

In fact, there are so many hits with such a variety of cases that you need
to give us more information.

http://groups-beta.google.com/groups?q=%2880072EE7+OR+0x80072EE7%29++%28MSFT+OR+MVP%29++group%3Amicrosoft.*

E.g. some cases which involved MSFT personnel apparently
were related to the fact that a proxy server was in the path.
If you have a proxy server try avoiding it and see if your symptom
changes.

Also, we don't know what version of WU you are using.
My understanding is that some other OS have lately started using
WUv5 or WUv6 instead of the WUv4 they used previously. In that
case a proxy server again could be the problem by not allowing
anonymous access for the services which the new update methods
use.

http://groups-beta.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/680ed1524a0b2097/f0d7c7c80da11568?q=ISA+BITS+account+author:aldwinckle+group:microsoft.public.windowsupdate&rnum=2#f0d7c7c80da11568


Finally, make sure that you are reporting the *first* error code from
your log for any given session, not the last. The last code is often
a summary code and this code apparently has been clarified in some
cases by preceding codes from the log.


HTH

Robert Aldwinckle
---