Hi,
Have tried making a http repository for my ESX servers instead of SCP'ing the tgz-files to local drives - seems like the right thing to do.
Anyway I get a "Invalid repository at http://iis_servername/ESX-1271567/: HTTP Error 404: Not found"
I have tried both on a IIS6 & Apache ( Apache running on port 8000 ) server using : 'esxupdate -v 10 -r http://apache_servername:8000/esx/ESX-1271567 update' with very similar resluts.
What I have done :
\- testet the the file / folder structure beneath the http-server is equal to that on the ESX server, when running esxupdate with local files : OK
\- testet DNS client resolution from the ESX host : OK
\- test URL from my admin pc ( pointing at the .xml-file ) : OK
\- esxcfg-firewall stop : OK
I have read the 'esx3_esxupdate.pdf' ( a few times now 
) - but it could be a very basic thing that I am missing as I can not see my test setup differs from the ones described in the manual.
Can someone please help ?
/Bjarke
Any log entries in the Apache access or error logs?
Is that a trailing colon ':' at the end of the URL? Is it supposed to be there?
Just guessing at this point... 
Harold
Thanks for forcing me to check the Apache logs
So much esier to find a typo when the two lines are next to each other ....
Thx a bundle !!
Brgds.
Bjarke
IIS servers will inherently have an issue in that .info[/b] and .hdr[/b] file types are not natively registered MIME types. Try hitting these files from any web browser on your IIS server and you'll get a 404. (404.2 to be specific if you look at your IIS logs, you do that, right?).
The fix:
You must register .info and .hdr MIME types in the IIS configuration.
Here's an example screenshot showing .hdr as a registered MIME type. Register it as
application/octet-stream
. Now do the same for the .info file extension, restart IIS service, and you'll be good to go. Patch management bliss.
For more information on this issue, see: http://technet2.microsoft.com/WindowsServer/en/library/94a74f87-0021-45cd-bd90-e243bb6e55e11033.mspx...
