Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version 7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command prompt...) DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or becauseit has no enabled devices associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then restore the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...