|
Home > Archive > IIS ASP > April 2006 > Incomplete download in IIS6
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Incomplete download in IIS6
|
|
| Samurai 2006-04-27, 7:52 am |
| I have this ASP application that delivers binary files (by calling C++ COM
object) to a C++ client application. On the server side I read from a file
and write it using Response.BinaryWrite function. On the client side I read
using the MFC CHttpFile::Read() function.
This code has been working for 5 years on Win2000/IIS5. Recently we moved
the ASP application as is into Windows 2003/IIS6. Since then we are seeing
that some large size files are delivered incomplete. There is no error on
both side. I have run the server side C++ COM object via debugger and found
no error, it writes the entire 5MB file without error. I have also run the
client side C++ application via debugger, and it receives 1.6MB and then
terminates without any error.
Whatever happened to rest of the file? I can reproduce this error everytime
for a given file. However, this doesn't happen for most of the files.
Please shed some light here...
| |
|
| Do you have URLScan configured on your server? I think this can limit the
download size of files.
Paul
"Samurai" wrote:
> I have this ASP application that delivers binary files (by calling C++ COM
> object) to a C++ client application. On the server side I read from a file
> and write it using Response.BinaryWrite function. On the client side I read
> using the MFC CHttpFile::Read() function.
>
> This code has been working for 5 years on Win2000/IIS5. Recently we moved
> the ASP application as is into Windows 2003/IIS6. Since then we are seeing
> that some large size files are delivered incomplete. There is no error on
> both side. I have run the server side C++ COM object via debugger and found
> no error, it writes the entire 5MB file without error. I have also run the
> client side C++ application via debugger, and it receives 1.6MB and then
> terminates without any error.
>
> Whatever happened to rest of the file? I can reproduce this error everytime
> for a given file. However, this doesn't happen for most of the files.
>
> Please shed some light here...
>
>
>
| |
| Samurai 2006-04-27, 7:52 am |
| Urlscan, not on Win2003. The old Win2000 had it, but that never caused any
problem.
"Paul" <Paul@discussions.microsoft.com> wrote in message
news:93A7D031-7FBA-46F0-800B-B6E8C9610992@microsoft.com...[vbcol=seagreen]
> Do you have URLScan configured on your server? I think this can limit the
> download size of files.
>
> Paul
>
> "Samurai" wrote:
>
| |
| David Wang [Msft] 2006-04-27, 7:52 am |
| Do you have ASP Response buffering enabled. I believe it is on by default.
And on IIS6, the default maximum ASP buffered response is 4MB. Configurable.
W3SVC/AspBufferingLimit
This limit is introduced for security reasons -- on IIS5, it is possible to
run a rogue ASP page in an infinite loop doing a Response.Write() with
buffering enabled to consume all system memory.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Samurai" <samurai@newsgroup.nospam> wrote in message
news:%23174TPPaGHA.2368@TK2MSFTNGP03.phx.gbl...
> Urlscan, not on Win2003. The old Win2000 had it, but that never caused any
> problem.
>
>
> "Paul" <Paul@discussions.microsoft.com> wrote in message
> news:93A7D031-7FBA-46F0-800B-B6E8C9610992@microsoft.com...
>
>
| |
|
| You probably have a high tech network card sitting in that new server, try
swapping it for a 10 dollar one and see what happens. (I have seen this
exact behaviour before)
"Samurai" <samurai@newsgroup.nospam> schreef in bericht
news:ucBNBbGaGHA.5108@TK2MSFTNGP05.phx.gbl...
>I have this ASP application that delivers binary files (by calling C++ COM
>object) to a C++ client application. On the server side I read from a file
>and write it using Response.BinaryWrite function. On the client side I read
>using the MFC CHttpFile::Read() function.
>
> This code has been working for 5 years on Win2000/IIS5. Recently we moved
> the ASP application as is into Windows 2003/IIS6. Since then we are seeing
> that some large size files are delivered incomplete. There is no error on
> both side. I have run the server side C++ COM object via debugger and
> found no error, it writes the entire 5MB file without error. I have also
> run the client side C++ application via debugger, and it receives 1.6MB
> and then terminates without any error.
>
> Whatever happened to rest of the file? I can reproduce this error
> everytime for a given file. However, this doesn't happen for most of the
> files.
>
> Please shed some light here...
>
|
|
|
|
|