none
Server error in '/Reports' application, when exporting reports to Excel

    Question

  • All,

    i have this error when i tried to export my reports to excel.

    For more information about this error navigate to the report server on the local server machine, or enable remote errors body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }

    For more information about this error navigate to the report server on the local server machine, or enable remote errors

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [Exception: For more information about this error navigate to the report server on the local server machine, or enable remote errors]
    
    [Exception: An error occurred during rendering of the report.]
    
    [Exception: The operation has timed out. The report server has canceled the operation.]
       Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +4232
       Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +6152
       Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension) +344
       Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +856
       Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +504
       System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +4360
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +520
    

    any idea what happen and how to solve this?

    thanks!
    AddinGanteng
    Wednesday, August 19, 2009 2:24 AM

Answers

  • If you use ReportViewer in an application, try to export your report to Excel using Report Manager and see if you can get more specific error messages.

    There might be multiple reasons for this error, unfortunately the only thing this error message tells is that it's been timing out because the server did not respond. It can be because the report is big, or a server error. First we need to find out whether it is a product issue or a performance problem.

    Thanks,
    Krisztian

    Thursday, August 20, 2009 1:03 AM

All replies

  • Hi,

    Which version of SQL Server do you use? Are there reports that can be exported, or all of your reports fail?

    Thanks,
    Krisztian
    Wednesday, August 19, 2009 4:44 AM
  • SQL Server 2005.
    Only this report that returns error.

    thanks for your reply.

    AddinGanteng
    Wednesday, August 19, 2009 8:01 AM
  • If you use ReportViewer in an application, try to export your report to Excel using Report Manager and see if you can get more specific error messages.

    There might be multiple reasons for this error, unfortunately the only thing this error message tells is that it's been timing out because the server did not respond. It can be because the report is big, or a server error. First we need to find out whether it is a product issue or a performance problem.

    Thanks,
    Krisztian

    Thursday, August 20, 2009 1:03 AM