I installed Project Server 2003 on a Windows 2000 & Windows 2003 server.
I used Windows Update service to apply all patches and critical updates prior to the installation of Project Server 2003.
The day following the installation the event viewer on both servers showed Windows Update service failures. The error message on is the same on both servers. (Project Server 2003 functions fine)
WINDOWS UPDATE error:
"We encountered the error code 0x80072EEF and the requested page can not be displayed while accessing the Windows Update website. "
The failure was first recorded in the event Viewer the day following installation of Microsoft Project Server 2003. Prior to this Microsoft Updates functioned properly.
Another server on the same sub-net updates properly using Windows Update, ruling out a firewall issue within the enterprise. (This server did not have Microsoft Project Server 2003 installed)
Microsoft Office Updates functions properly on the 2 affected servers.
Actions:
I have added all varieties of the updates.microsoft.com to the trusted server entries, I have verified that the Host file contains only a localhost entry. I have flushed DNS and loaded a clean host file using nbtstat R command. I have reinstalled iesetup.exe, I upgraded to IE 7.0 w/o success. I uninstall the IE 7.0 beta. I have installed WindowsServer2003-KB912945
-x86-enu.e
xe and reregistered all the .dll files specified in the documentation.
Window Update Tech Support used livemeeting to take control of the 2003 server. They basically performed all the procedcures I had already tried. When they were unsuccessful in solving the problem they referred me to Microsoft's $240/incident tech support. My client an urban school district does not have a budget for such an expenditure.
I suspect the problem may be caused by a certificate issue, resulting from the Project 2003 installation. None of the three support reps in the Windows Update division was able to answer the question; Does Windows Update services require a certificate?
Can anyone help me with this problem - Microsoft has booted on this problem that I strongly suspect this is a result of bug in their installation code.
Michelle Fenn