Exporting Excel in Production Env doesn't work, works fine locally

Question

1.00/5 (2 votes)

See more:

Hi Friends,

I am facing an issue when I run my code in Production Env.
Same code I am running into my machine with IIS and its working fine here.

This code generates the excel with exported data. Which works fine locally, but in production it says the highlighted error.

404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Help will be appretiated enough.

C#

protected void linkExportExcel_Click(object sender, EventArgs e)
        {
            Response.ClearContent();
            Response.ClearHeaders();
            Response.AddHeader("Cache-Control", "max-age=3");
            Response.AddHeader("Pragma", "public");
            Response.AddHeader("content-disposition", "attachment;filename=LeaveBalanceAsOn(" + DateTime.Now.ToString("MM-dd-yyyy") + ").xls");

            Response.Charset = "";
            Response.Cache.SetCacheability(HttpCacheability.NoCache);

            Response.ContentType = "application/vnd.xls";
            Response.Write(hidHtml.Value);
            //Response.Write(hidHtml.Value);
            Response.Flush();
            Response.End();
        }

Posted 8-Aug-14 7:46am

myself.panku

Updated 8-Aug-14 8:07am

Wendelius

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 8-Aug-14 14:11pm

What file? what directory? You don't show any file system operation, so how to you expect someone to find your bug? See if you use some hard-coded paths in your entire code...
—SA

myself.panku 8-Aug-14 20:23pm

Hi Mika,

Thanks for your instant revert on the question.

But as you have asked i haven't mentioned any file operation in the the above peice of code, so that's all what I have written, i am not using the Introp for creating Excel object and adding 1 by 1 row into the Excel.Application object, this is what I avoid to do.
I have used the conent-disposition which will generate the .xls file irrespective of if there is excel installed in the server or not , bcoz the file needs to be opened at client.

The same piece of code runs in my office site which is deployed in production, I know this could be resolved by some web.config resolution but what are these required changes that I am missing here.

I hope this will make it clear to all, what I am expecting.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2014-08-08T08:09:00

Solution 1

Few things to check:
- Excel properly installed
- the file actually exists
- correct working path is used

In your method, you can use File.Exists[^] method to check if the file actually exists and if not use a proper method to communicate the error.

Posted 8-Aug-14 8:09am

Wendelius

myself.panku · Answer 2 · 2014-08-08T14:22:00

Hi Mika,

Thanks for your instant revert on the question.

But as you have asked i haven't mentioned any file operation in the the above peice of code, so that's all what I have written, i am not using the Introp for creating Excel object and adding 1 by 1 row into the Excel.Application object, this is what I avoid to do.
I have used the conent-disposition which will generate the .xls file irrespective of if there is excel installed in the server or not , bcoz the file needs to be opened at client.

The same piece of code runs in my office site which is deployed in production, I know this could be resolved by some web.config resolution but what are these required changes that I am missing here.

I hope this will make it clear to all, what I am expecting.

Exporting Excel in Production Env doesn't work, works fine locally

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0

Existing Members

...or Join us