Another Reason Why Project Server Blows

The project server here at work hasn’t been connecting to our internal WSUS server, and I noticed that it was missing a few security patches.  Since WSUS wasn’t working, I decided to visit Windows Update.  HA, well that doesn’t work either.  So I open up the %systemroot%WindowsUpdate.log and find the following error.

WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
WARNING: DownloadFileInternal failed for error 0x80190191
* WARNING: Failed to synchronize, error = 0x80244017
WARNING: WU client failed Searching for update with error 0x80244017
>>— RESUMED —COMAPI: Search [ClientId = WindowsUpdate]
– Updates found = 0
– WARNING: Exit code = 0x00000000, Result code = 0x80244017
— END — COMAPI: Search [ClientId = WindowsUpdate]
WARNING: Operation failed due to earlier error, hr=80244017
FATAL: Unable to complete asynchronous search. (hr=80244017)

Doing a quick search on the error code on Google brings me to a lot of pages about proxy settings.  However, I’m not running a proxy server anywhere, and I’m not running ICF on the project server either.  What is going on?!

Then I see a link about project server with this error.

I now know that project server uses a proxy server with WSS.  How stupid can that be?  Well, basically, I added our local WSUS server to the bypass list.  I also did it for *, but that still doesn’t seem to be allowing me to hit Windows Update.  Oh well, at least it can update from someplace.