file "killed" a few seconds after it's generated

[200dogz]

Hi,

I have a aspx page that generates reports with the data it gets from databases.

It used to work quick and fine until recently when a file is generated it gets killed a few seconds after that. It can still be downloaded if fast enough:

A few seconds later...

The interesting thing is that only reports that are approximately larger than 1MB would get destroyed. Small reports would stay there forever until it's downloaded.

At first I thought the server might be out of space/memory to store the created report and asked the server admin to check. I didn't get a reply from him so it's probably caused by something else.

If anyone knows a possible reason for this problem please let me know; I've stucked on this for almost a week =(

Thanks

[200dogz]

@Frinavale
Hey Frinavale I think you are probably right!

This is what's being used to output the file:

HttpContext context = HttpContext.Current;
context.Response.Clear();
context.Response.AppendHeader("Content-Type", "application/msword");
context.Response.AppendHeader("Content-disposition", "attachment; filename=\"report.doc\"");
context.Response.Write(this.document);
context.Response.BufferOutput = true;
context.Response.Flush();
context.Response.Close();

I will ask our admin to increase the memory allowance for each process in IIS first and see if it fixes the problem :).

[200dogz]

Umm...the problem seems to be gone after...a server reboot.

That probably means it's a resource issue?

Anyway, I believe the same problem is going to pop up again in the future but as long as there's way to resolve it I guess it's all good :)

Many thanks

[NeoPa]

... Unless the reboot is required because of your code being resource hungry, or maybe untidy (not releasing resources it has finished with).

If that is the case, this is likely to recur.

It could all be entirely unconnected with your code too, of course.

[Frinavale]

@200dogz
It's hard for me to tell if you're using session or not...
When you use "context.Respon se.Write(this.d ocument);" I'm not sure where you're retrieving your document from or what "this" is.

If you have more problems with this in the future, and you are changing your asp (or C#) code, feel free to ask for help in the Asp.NET forum. If you're having server problems and need assistance configuring or debugging your IIS feel free asking questions in the IIS forum.

-Frinny

[200dogz]

@Frinavale
it's just a string variable =P


@Frinavale
cool, thanks

[NeoPa]

@200dogz
This may sound stupid from a non-asp person, but is it possible for a simple string variable to work as an object? Put another way - Can a string variable have a document property?

[200dogz]

@NeoPa
Yes that's what I've been using for all my reports. As long as the headers are set correctly you can write any string as output.

[NeoPa]

Cool. That confirms it is simply down to my not understanding ASP.

-NeoPa <creeping quietly away - hoping nobody notices>

[Frinavale]

Um....?
The String object doesn't have a "document" property.......
"document" is the name of your String variable right?

I think you meant to say that "this" refers to the page, and "document" is the name of a variable within the page.