Anybody else had any troubles getting it working I've got the folder in IIS set to allow directory browsing, but after AppUpdater.DownloadUpdate() is called, I get this error...
5/10/2004 6:02:47 PM: UPDATE FAILED with the following error message:
System.Net.WebException: The remote server returned an error: (501) Not Implemented.
at Microsoft.Samples.AppUpdater.AppDownloader.Download()
at Microsoft.Samples.AppUpdater.AppDownloader.RunThread()
What the heck does Not Implemented mean The files with the updated versions sits on a Windows Server 2003 box. Are there known issues with this Or am I maybe doing something wrong I've checked the UpdateUrl property and it is correct.
Thanks!

AppUpdater Not Working
NailSR
yves_teissier
If you open up IIS manager for the web server you should see a folder 'Web Service Extensions' if you click on that there should be a listing for WebDav that by default is set to prohibit. If you set this to allow it should work.
This may not always be the solution but it was in my case.
kaja
rw-ral
thanks for the post, btw
Fabio
Duncan R. Campbell
I tried everything on my downloading web server setting and directory security and still not able to get it work when the client application running outside our network. Are you aware of any possible security issues above the iis server I wonder if any network firewall could cause this problem. The exact error message I got is:
The auto-update of this application failed with the following error message:
Download of a new update from "http://www.mycompay.com/myapplication/1.2.00/" failed with the network error: the remote server returned a error:(501) Not Implemented.
Again, if my client user sitting inside of network, everything works fine.
thanks.
Pan
jschlade
After this it worked with no problems.
Ernie Morin
Dale Dufek
Any further idea/suggestion
Thanks a lot.
Pan
mbieweng
I have the same problem you experienced a month ago, so I bet you already know how to fix it.
I got the "The remote server returned an error: (501) Not Implemented." message only when the end user access from outside our network. If the end user is inside the network, everything works fine.
Would you help me out!
Thanks,
PAN
Pramod BNS
David Emigh
Kent Waldrop Fe08
Could it have anything to do with front page server extentions
ronks
Nestor N