My download Site is using the file protocol specified as follows:
file://///x:/newbas/updates/%file%
There are approximately 20 machines that have access to a shared server drive mapped as "X". All machines are running Windows 7 Pro. All machines are configured the same way. The updates work fine on about 10 of the machines. The updates fail on the other 10 with the following message:
Error trying to save file: Error downloading "file://///x:/newbas/updates/newbas.build2488.to.build2488.1.wyu":Could not find a part of the path 'x:\newbas\updates\newbas.build2488.to.build2488.1.wyu'.
I opened a browser on one of the machines where the download failed and pointed the URL to:
file://///x:/newbas/updates/newbas.build2488.to.build2488.1.wyu
The file downloaded just fine. I tried changing the number of "/"s after "file:" from 5 to 3 (file:///) and the download still failed with the same message. I did notice that some of the browsers are more sensitive to the number of forward slashes after "file:". Chrome doesn't seem to care. Firefox works with 3 and fails with 5. Internet Explorer works with 4 or 3.
How can the same process work on 10 machines and fail on another 10 machines where all 20 machines are pointing to the same download files? What should I be looking at to correct the problem on these machines?
Bob
First of all, that URL format is incorrect. There should only be 3 forward slashes after "file:" (e.g. file:///x:/your/path/to/updates.wyu)
Next, the problem is likely that the failing machines don't have access to the "x" network drive, and/or it's not mounted on the computer.
I tried changing the URL format to 3 forward slashes "file:///x:" and it still fails. All of the failed machines have access to the "X" drive. My application doesn't run on these machines unless the "X" drive is available. I indicated that I entered "file://///x:/newbas/updates/newbas.build2488.to.build2488.1.wyu": in the URL on one of the failed machines and the file successfully downloaded. I also tried "file:///x:/newbas/updates/newbas.build2488.to.build2488.1.wyu" as the URL and it successfully downloaded. As I said, all 20 machines are setup the same way and all share the same "X" drive.
Bob
Mapped network drives are user specific, so if the app is running under a different identity than the user that created the mapped drive letter (x:) it won't work. wyUpdate might run as a different user depending on the needs of wyUpdate (i.e. needing elevation to complete the update -- thus wyUpdate might be elevated as a different user)
You will save yourself a ton of trouble just by using HTTP / HTTPS.
