[Hood99]

Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
applying this service pack we get the following error. [Error number:
0x80072F07] and this statement; "Windows Update has encountered an error and
cannot display the requested page. You may find the following resources
helpful in resolving the problem:" Any suggestions please...

[steve]

I am geting the same thing with an 0x800B0003 !!!!!

"Hood99" wrote:

> Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
> applying this service pack we get the following error. [Error number:
> 0x80072F07] and this statement; "Windows Update has encountered an error and
> cannot display the requested page. You may find the following resources
> helpful in resolving the problem:" Any suggestions please...

[Tim]

I am getting the same error on Windows 2003 Server (not Enterprise) just
received a new Server, loaded Server 2003 SP1 tio bring it up-to-date and now
unable to access windows Update

"steve" wrote:

> I am geting the same thing with an 0x800B0003 !!!!!
>
> "Hood99" wrote:
>
> > Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
> > applying this service pack we get the following error. [Error number:
> > 0x80072F07] and this statement; "Windows Update has encountered an error and
> > cannot display the requested page. You may find the following resources
> > helpful in resolving the problem:" Any suggestions please...

[Big Bad Bob]

"Hood99" wrote:

> Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
> applying this service pack we get the following error. [Error number:
> 0x80072F07] and this statement; "Windows Update has encountered an error and
> cannot display the requested page. You may find the following resources
> helpful in resolving the problem:" Any suggestions please...

[Big Bad Bob]

> Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
> applying this service pack we get the following error. [Error number:
> 0x80072F07] and this statement; "Windows Update has encountered an error and
> cannot display the requested page. You may find the following resources
> helpful in resolving the problem:" Any suggestions please...

(ignore previous empty post - I made an error)

I can't recall the exact error I was getting, but after applying SP1 to
Windows Server 2003 on a Pentium 1 (pre-MMX) machine (with 128M I might add)
the machine went into a 'boot loop'. It turned out that drive corruption
"happened" but I'm not convinced it was PRIOR to the update process. I think
the boot loop caused it. I went through several iterations, safe mode, VGA
mode, etc. and finally turned OFF auto-boot to see the error. No driver was
involved (I had a blue-screen display but no helpful info that I could see,
and only a single line of text) so I couldn't disable a driver to fix it.

This was a test machine so I booted server 2000 and did chkdsk /R on the 2k3
drive before continuing. There were no apparent bad sectors on the drive,
though a bootup chkdsk reported a number of problems with security
descriptors (so many that it overflowed the event log entry).

Following this I booted the install CD and went through several iterations.
Since I didn't know where the 'recovery diskette' was I simply used the 'R'
option before the license screen, but the machine went into a boot loop
again. Then I used the 'R' option after the license screen. This normally
fixes your OS so you can pick up where you left off, like an upgrade install.
Unfortunately, the machine went into a 'boot loop' again, this time getting
to the "Setup is recovering..." screen, then booting, then doing it again,
and again, and again.

So I ran setup ONE MORE TIME, choosing the same 'recovery' option as before
(after the license screen). THIS time I got to the 'CD KEY' screen and
completed the upgrade install. I'm installing the security patches (again)
from automatic updates, and hopefully the system will boot properly
afterwards.

SP1 does not show up in the 'help / about' screen for 'my computer'.
Apparently it was successfully uninstalled.

I will not be installing SP1 on this computer until this issue is properly
resolved. I suspect it may be due to the use of MMX instructions (or
similar) in the updated binaries. However, it's my understanding that a
pre-MMX Pentium 1 is still on the hardware compatibility list. [simply
removing my box from the list wouldn't be a very smart move, either]

[Robert Aldwinckle]

"Big Bad Bob" <BigBadBob@discussions.microsoft.com> wrote in message
news:2AC91F53-8BBE-4926-89E0-F2CF32CDF5A1@microsoft.com...
>> Windows 2003 server enterprise SP1 have applied to a Dell 1750. After
>> applying this service pack we get the following error. [Error number:
>> 0x80072F07] and this statement; "Windows Update has encountered an error and
>> cannot display the requested page. You may find the following resources
>> helpful in resolving the problem:" Any suggestions please...
>
> (ignore previous empty post - I made an error)
>
> I can't recall the exact error I was getting, but after applying SP1 to
> Windows Server 2003 on a Pentium 1 (pre-MMX) machine (with 128M I might add)
> the machine went into a 'boot loop'. It turned out that drive corruption
> "happened" but I'm not convinced it was PRIOR to the update process. I think
> the boot loop caused it. I went through several iterations, safe mode, VGA
> mode, etc. and finally turned OFF auto-boot to see the error. No driver was
> involved (I had a blue-screen display but no helpful info that I could see,
> and only a single line of text) so I couldn't disable a driver to fix it.


FWIW I had a similar experience on XPsp2 last weekend.
What was your "drive corruption"? Mine was flipping the partition labels somehow.
Obviously making booting those partitions successfully impossible. I'm still not sure if it's safe
to just relabel them the way they were so I just created a new partition and reinstalled there.

Looks as if you already do have an alternate system to boot to enable you to diagnose
what is happening on the system which won't boot? Then have you tried looking at the
last changed files during the boot? I found a setuperr.log that way which I think gives
a clue about the cause of the initial error. Also, you may be able to get into failing partition's
event log. (*.evt) (eventvwr told me mine were corrupted.)


>
> This was a test machine so I booted server 2000 and did chkdsk /R on the 2k3
> drive before continuing. There were no apparent bad sectors on the drive,
> though a bootup chkdsk reported a number of problems with security
> descriptors (so many that it overflowed the event log entry).

I also had to do a defrag. The partition was badly fragmented. So much so that
I think that setup was having a hard time with the pagefile. (E.g. I was getting a tiny
message box which flashed so quickly it was barely readable which was saying something
about resources. Anyway I deleted the pagefile to assist the defrag and let setup create
its own but it created a stupidly small one and in an unexpected partition. I eventually figured
out how to get it to resize and move it where I wanted by using a Load Hive command with
RegEdit and editing its pagingfiles value. (This was before I noticed the partition table
problem.) Etc. <Ugh./>


>
> Following this I booted the install CD and went through several iterations.
> Since I didn't know where the 'recovery diskette' was I simply used the 'R'
> option before the license screen, but the machine went into a boot loop
> again. Then I used the 'R' option after the license screen. This normally
> fixes your OS so you can pick up where you left off, like an upgrade install.
> Unfortunately, the machine went into a 'boot loop' again, this time getting
> to the "Setup is recovering..." screen, then booting, then doing it again,
> and again, and again.

I doubt that setup recovers well at all from multiple iterations.
It looks like more a case of recognizing that the user is trying it again,
crossing fingers and plunging on again blindly, oblivious of any
additional corruption it may cause.

My problem was that I couldn't figure out how to get out of that loop
into a normal boot menu. I only figured it out after trying to Repair
a perfectly good partition and having it get corrupted too.
FYI the trick I discovered (too late) is to wait for the prompt for the
CD menu to just be taken away but before the autoboot for the Repair
is starting and press "any key" then. I would say you have less than
a second to take that action.


>
> So I ran setup ONE MORE TIME, choosing the same 'recovery' option as before
> (after the license screen). THIS time I got to the 'CD KEY' screen and
> completed the upgrade install.

Wow. So much better luck than I had. Good work.


> I'm installing the security patches (again)
> from automatic updates, and hopefully the system will boot properly
> afterwards.
>
> SP1 does not show up in the 'help / about' screen for 'my computer'.
> Apparently it was successfully uninstalled.
>
> I will not be installing SP1 on this computer until this issue is properly
> resolved. I suspect it may be due to the use of MMX instructions (or
> similar) in the updated binaries. However, it's my understanding that a
> pre-MMX Pentium 1 is still on the hardware compatibility list. [simply
> removing my box from the list wouldn't be a very smart move, either]

How can we tell? It seems that the only complete diagnostic capability that
Microsoft provide for problems with setup is to hook it up to another system
running a debugger.

I am not impressed. If Microsoft had given me one of its "surveys"
while this fiasco was occurring I would have been giving it my lowest
rating ever.


FWIW

Robert Aldwinckle
---