Site is currently unable to handle this request. HTTP ERROR 502

Question

1.00/5 (1 vote)

See more:

Hi,

In my web application, there is one page which is used for reporting purpose.
Based on selected parameters it fetches the summary data and binds to Gridview.
There is another separate button on which detail excel report should generate.
Problem is this functionality properly works in development environment. Excel report gets generate in development environment.

But in UAT sometime it excel gets generate sometime it doesn't. when it doesn't work it shows following message

This page isn’t working

mindworks.ultimatix.net is currently unable to handle this request.
HTTP ERROR 502

Requesting to give hint about the cause of the issue.

What I have tried:

Tried tracing the issue by logging the steps but it shows all the code is getting executed. But still excel report in not getting generate.

1) Using sql connection to fetch data.
2) Using openxml to generate excel file.

Posted 7-May-17 4:56am

Abhijit Parab

Add a Solution

Comments

Richard Deeming 8-May-17 13:01pm

If you're using Office Interop, then don't. It's not supported in ASP.NET applications.

If you're using OpenXML, then you're going to need to debug your code and check the server's event logs to find out what the real problem is. "Error 502" simply tells us that something went wrong on the server. We have no way to tell you what went wrong, or how to fix it.

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)