Arthur
Mon Jul 14 11:14:27 CDT 2008
Hi, ... okay, I have tried disabling both my AV and firewall, neither
helped.
It must be something on the client, because I can open the same files fine
from another client...
I tried it from another client, and was able to open the same files just
fine. So it DEF had to be something on the client.
Finally, I thought of something else to try, which fixed it...
I went in Visual Studio, clicked on the website project, and looked in the
properties window,
at the property called "Full Path", which points to a locally cached copy of
the projct... at something like:
C:\Users\<username>\AppData\Local\Temp\VWDWebCache\<webSiteUrlPath>\
I deleted the whole directory <webSiteUrlPath> and then re-opened VS, and
all was good with the world again! :)
Thanks for the ideas and help... much appreciated.
"David Wang" <w3.4you@gmail.com> wrote in message
news:567b7066-66d9-4c60-9753-0b3b7b13f449@26g2000hsk.googlegroups.com...
> If the status codes are all 200 0, then this is likely not an issue
> with IIS because IIS already served up the content, and you said that
> you can retrieve it from IIS directly.
>
> You say that it occurred suddenly one day, and only certain files. I
> would suggest looking at what you had changed recently on either
> client or server (think about security, anti-virus, etc changes).
> Perhaps something on the client is filtering the files based on its
> contents, etc.
>
>
> //David
>
http://w3-4u.blogspot.com
>
http://blogs.msdn.com/David.Wang
> //
>
>
>
> On Jul 13, 6:42 am, "Arthur Dent" <hitchhikersguideto-n...@yahoo.com>
> wrote:
>> The status codes are all 200 0. It wouldn't be the mime/type, because it
>> is
>> not limited to certain file types... just certain files.
>> Some aspx files I can open, some not. Some .aspx.vb files I can open,
>> some
>> not.
>>
>> And it doesn't give me any more useful information than just "Could not
>> get
>> the file".
>>
>> I can open the files directly from the web server though with no
>> problems.
>>
>> "David Wang" <w3.4...@gmail.com> wrote in message
>>
>> news:e637a4fc-b453-404a-9b72-cbc3a8d44b83@2g2000hsn.googlegroups.com...
>>
>>
>>
>> > On Jul 11, 12:28 pm, "Arthur Dent" <hitchhikersguideto-n...@yahoo.com>
>> > wrote:
>> >> Hello all, I have a problem which is being a major hindrance to being
>> >> able
>> >> to work.
>>
>> >> I have a web (actually a subweb) on a Windows 2003 box, with FPE
>> >> installed,
>> >> and all.
>> >> I can open the project fine in Visual Studio 2008 (on Vista).
>> >> But all of a sudden yesterday, I can no longer open CERTAIN files.
>> >> Some
>> >> files are completely fine,
>> >> but other ones, when I try to open them, I get an error about
>>
>> >> "Unable to get file '<filename.ext>' from the Web server."
>>
>> >> The status bar says "Getting file ... from the web..." as usual, but
>> >> then
>> >> that error pops up.
>>
>> >> I tried recalculating the web. I did a server health check.
>> >> I stopped and restarted IIS. I deleted the subweb and recreated it.
>> >> I checked the physical file security properties...
>>
>> >> I cannot find anything off about the files that don't work, but it
>> >> just
>> >> won't let me open them.
>> >> Any ideas???
>>
>> > Can you look at the IIS logfile entries for the files that fail to be
>> > retrieved.
>>
>> > If the status/substatus/win32-error codes are "404 3 50", then the
>> > failure is due to the fact that IIS6 disallows download of resources
>> > with unspecified MIME Type for security reasons (and because of HTTP
>> > compliance reasons). To make the filetypes downloadable, you need to
>> > add a proper MIME Type for that extension.
>>
>> > //David
>> >
http://w3-4u.blogspot.com
>> >
http://blogs.msdn.com/David.Wang
>> > //- Hide quoted text -
>>
>> - Show quoted text -
>