An error occurred during local report processing

Fixes an "An error occurred during local report processing" error message that occurs when you export a report in SSRS 2008. This issue occurs when you add a Tablix control in the header or footer.

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

Symptoms

Consider the following scenario:

  • You create a report in Microsoft SQL Server 2008 Reporting Services (SSRS 2008).

  • You define a Tablix control and an expression in the header or footer of the report.

  • You define a parent group and a child group in the Tablix control.

  • You try to export the report to a file that is a hard page-break renderer . For example, you try to export the report to a PDF-formatted or TIFF-formatted file. The parent group is not expanded before you export the report.

In this scenario, you may receive the following error message:

An error occurred during local report processing.
An internal error occurred on the report server. See the error log for more details.

Resolution

Cumulative update information

SQL Server 2008

The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1.

For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

I am new to using SSRS. I am using a .rdlc file for report generation in a PDF with VS 2012. When I tried to set the parameters like

ReportParameter param = new ReportParameter(kvp.Key, kvp.Value);
LocalReport.SetParameters(param);

This throws an exception:

An error occurred during local report processing..The definition of the report » is invalid.. Could not load file or assembly ‘System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Access is denied.

More details:

{Microsoft.Reporting.WebForms.LocalProcessingException: An error occurred during local report processing. ---> Microsoft.Reporting.DefinitionInvalidException: The definition of the report '' is invalid. ---> System.IO.FileLoadException: Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Activator.CreateInstance(String assemblyString, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(String assemblyName, String typeName)
   at System.AppDomain.CreateInstance(String assemblyName, String typeName)
   at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
   at System.AppDomain.CreateAppDomainManager()
   at System.AppDomain.Setup(Object arg)
   at System.AppDomain.nCreateDomain(String friendlyName, AppDomainSetup setup, Evidence providedSecurityInfo, Evidence creatorsSecurityInfo, IntPtr parentSecurityDescriptor)
   at System.AppDomainManager.CreateDomainHelper(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
   at System.AppDomainManager.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
   at System.AppDomain.InternalCreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
   at System.AppDomain.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
   at Microsoft.Reporting.ReportCompiler.CreateCompilationTempAppDomain()
   at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
   --- End of inner exception stack trace ---
   at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
   at Microsoft.Reporting.LocalService.GetCompiledReport(PreviewItemContext itemContext, Boolean rebuild, ControlSnapshot& snapshot)
   at Microsoft.Reporting.LocalService.CompileReport()
   at Microsoft.Reporting.LocalService.Microsoft.Reporting.ILocalProcessingHost.CompileReport()
   at Microsoft.Reporting.WebForms.LocalReport.EnsureExecutionSession()
   --- End of inner exception stack trace ---
   at Microsoft.Reporting.WebForms.LocalReport.EnsureExecutionSession()
   at Microsoft.Reporting.WebForms.LocalReport.SetParameters(IEnumerable1 parameters)
   at Microsoft.Reporting.WebForms.Report.SetParameters(ReportParameter parameter)

What am I missing. In some posts, it ‘s been advised to use missing Microsoft.ReportViewer.PorcessingObjectMode.dll. I did that so I have all the required dlls like:

-    Microsoft.ReportViewer.Common.dll
-    Microsoft.ReportViewer.WebForms.dll
-    Microsoft.ReportViewer.ProcessingObjectModel.dll

are there.

I referred to this post. But still I could not get this done.

Содержание

  1. KB2446498 — FIX: «An error occurred during local report processing» error message may occur when you export a report in SQL Server 2008 Reporting Services
  2. Symptoms
  3. Resolution
  4. Cumulative update information
  5. SQL Server 2008
  6. SQL Server 2008 Service Pack 2
  7. Status
  8. References
  9. KB2485396 — FIX: Error when you use a hard page-break renderer to export a report in SSRS 2008 R2 if the HideDuplicates property is not set to None
  10. Symptoms
  11. Cause
  12. Resolution
  13. Cumulative update information
  14. SQL Server 2008 R2
  15. Status
  16. References
  17. Error an error occurred during local report processing
  18. Answered by:
  19. Question
  20. Error an error occurred during local report processing
  21. Answered by:
  22. Question
  23. Answers
  24. All replies

KB2446498 — FIX: «An error occurred during local report processing» error message may occur when you export a report in SQL Server 2008 Reporting Services

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.

Symptoms

Consider the following scenario:

You create a report in Microsoft SQL Server 2008 Reporting Services (SSRS 2008).

You define a Tablix control and an expression in the header or footer of the report.

You define a parent group and a child group in the Tablix control.

You try to export the report to a file that is a hard page-break renderer . For example, you try to export the report to a PDF-formatted or TIFF-formatted file. The parent group is not expanded before you export the report.

In this scenario, you may receive the following error message:

An error occurred during local report processing.
An internal error occurred on the report server. See the error log for more details.

Resolution

Cumulative update information

SQL Server 2008

The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1.

For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

References

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Источник

KB2485396 — FIX: Error when you use a hard page-break renderer to export a report in SSRS 2008 R2 if the HideDuplicates property is not set to None

Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.

Symptoms

Consider the following scenario:

You install Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) on a computer.

You create a report that contains a Tablix control. This Tablix control has a text box.

You set the HideDuplicates property for the text box to a value that is in scope of the report. Therefore, the value of this property is not set to None.

You try to render or export the report by using any hard-page-break renderer. For example, you try to use one of the following renderers:

Print/Print Layout/Print Preview

In this scenario, the report is not exported. Additionally, you receive the following error message in a report design tool:

An error occurred during local report processing.
(processing): ScalableList: Index outside the allowed range [0:: ]

Additionally, you receive the following error message in Report Manager or the Report Server web service:

An internal error occurred on the report server. See the error log for more details. (rsInternalError)
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: Microsoft.Reporting.WebForms.ReportServerException: An internal error occurred on the report server. See the error log for more details. (rsInternalError)
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.

Cause

This issue occurs because hard-page-break renderers throw an exception when the HideDuplicates property is not set to None for a text box in a Tablix control.

Resolution

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2489376 Cumulative Update package 6 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

References

For more information about the HideDuplicates property for a text box, visit the following Microsoft Developer Network (MSDN) website:

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Источник

Error an error occurred during local report processing

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I developed a report that works fine in my environment. However, when moving it to another server I get the error code below.

System_Error > An error occurred during local report processing. StackTrace: at Microsoft.Reporting.WebForms.LocalReport.EnsureExecutionSession() at Microsoft.Reporting.WebForms.LocalReport.InternalRender(String format, Boolean allowInternalRenderers, String deviceInfo, PageCountMode pageCountMode, CreateAndRegisterStream createStreamCallback, Warning[]& warnings) at Microsoft.Reporting.WebForms.LocalReport.InternalRender(String format, Boolean allowInternalRenderers, String deviceInfo, PageCountMode pageCountMode, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings) at Microsoft.Reporting.WebForms.LocalReport.Render(String format, String deviceInfo, PageCountMode pageCountMode, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings) at Microsoft.Reporting.WebForms.Report.Render(String format, String deviceInfo, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings) at GetCustomerReport(Int64 IdentificationNumber) in C: Leads.vb:line 124 at MarketingServices.WSReports.GetReport(String IdentificationNumber, String Password) in C: WSReports.asmx.vb:line 35

It fails in the line as I don’t get any error when this line is commented:

Источник

Error an error occurred during local report processing

This forum is closed. Thank you for your contributions.

Answered by:

Question

I have a form with 2 Report-viewers each displaying their own rdlc file they both are Identical the only diference is the user has the option to have their name or their logo on it .

They both render perfectly in the report-viewer .

I get the error only on one of the reports when I try to export to PDF with code I wrote not the built in export button in ReportViewer,if I use the built in export button it exports well.

This is the line the error ocures

Here is the code I use to export.

Answers

Welcome to the MSDN Forum.

Here are a few related threads for your reference:

I hope you can get some ideas from that thread.

Please try to ask there.

Mike Feng
MSDN Community Support | Feedback to us
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

The error being ? It could help to diagnose the issue. Have you checked if AttDir & fileName & «.pdf» is a valid path/filename.

Please always mark whatever response solved your issue so that the thread is properly marked as «Answered».

thanks Patrice for your reply.

Like I said I have 2 RDLC fiiles.

I tried exporting both reports having AttDir & fileName the same one exports OK the other does not..

You forgot to tell what is the exception you have (also you gave 2 lines rather than one to tell where it happens). The exact location and the exact exception you get are likely where diagnosing a bug should always starts.

Please always mark whatever response solved your issue so that the thread is properly marked as «Answered».

Sorry Patrice I’m new to development.

I don’t know if this is what you want.

the exception I get with the try catch is an error occured during local report processing.

By removing the try catch I was able to copy this when the error occurred.

Microsoft.Reporting.WinForms.LocalProcessingException was unhandled

Message=An error occurred during local report processing.

at Microsoft.Reporting.WinForms.LocalReport.InternalRender(String format, Boolean allowInternalRenderers, String deviceInfo, PageCountMode pageCountMode, CreateAndRegisterStream createStreamCallback, Warning[]& warnings)

at Microsoft.Reporting.WinForms.LocalReport.InternalRender(String format, Boolean allowInternalRenderers, String deviceInfo, PageCountMode pageCountMode, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings)

at Microsoft.Reporting.WinForms.LocalReport.Render(String format, String deviceInfo, PageCountMode pageCountMode, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings)

at Microsoft.Reporting.WinForms.Report.Render(String format, String deviceInfo, String& mimeType, String& encoding, String& fileNameExtension, String[]& streams, Warning[]& warnings)

at CFI.CFI_Report.Create_PDF() in C:UsersJohnDocumentsVB ProjectsCFICFICFI_Report.vb:line 123

at CFI.CFI_Report.btnMail_Click(Object sender, EventArgs e) in C:UsersJohnDocumentsVB ProjectsCFICFICFI_Report.vb:line 75

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

at CFI.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81

at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)

at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

Message=Report ‘CFI_Report_Logo’ contains external images. The EnableExternalImages property has not been set for this report.

Источник

  • Remove From My Forums
  • Question

  • A report is driven by finding data so if no data is found, there should be a way to report «NO DATA FOUND». The property for the tablix (NoRowsMessage) should be able to function as a method to show this data. Instead, with the value on the properties
    filled to say «No Data Found» the message does not change. It still says «An error occurred during local report processing» Why does it not show the message listed in the NoRowsMessage property?

Answers

  • I’ll try the profiler.  But the report works in Production.  It’s unlikely that it is a SQL query issue.  It only fails when it does not find any data and returns an empty data set. Turns out the people who operate our IIS have problems
    configuring permissions so the Parameter for the Root Web URL causes this error. Removing the parameter during editing and then reinserting it when publishing fixes the problem. Thanks for the help.

    • Edited by

      Tuesday, November 16, 2010 3:51 PM
      IIS

    • Marked as answer by
      Challen Fu
      Wednesday, November 17, 2010 8:42 AM

  • Hi Ramu,

    From your descriptions, you have rendered the report to an image and then printed the image. But the report is printed twice with different kind of data. The first print is working fine. The second print will throw the error \TestReportPrinting\WindowsApplication1\bin\Debug\Report3_1.emf’ because it is being used by another process.

    The error indicates the exported file is being used by another process.   The issue seems to be caused by the process is still writing the file. So, to solve the issue, please make sure the stream has been closed.

    However, the understand form your description is limited. There are 2 render method for the localreport to render reports.

    public void Render (

        string format,

        string deviceInfo,

        CreateStreamCallback createStream,

        out Warning[] warnings

    )

    public override byte[] Render (

        string format,

        string deviceInfo,

        out string mimeType,

        out string encoding,

        out string fileNameExtension,

        out string[] streams,

        out Warning[] warnings

    )

    If using the first method, please use the following code to make sure the writing process has finished:

    foreach (Stream stream in m_streams)

                stream.Position = 0;

    If using the second method, please use the following code to make sure the writing process has finished:

    byte[] bytes = ReportViewer1.LocalReport.Render(

                   «Excel», null, out mimeType, out encoding,

                    out extension,

                   out streamids, out warnings);

                FileStream fs = new FileStream(@»c:output.xls»,

                   FileMode.Create);

                fs.Write(bytes, 0, bytes.Length);

                fs.Close();

    If the solution above does not help, could you please help to post some sample codes and check which process is using the file by using Unlocker.

    For more information, please see:

    LocalReport.Render Method: http://msdn.microsoft.com/en-us/library/microsoft.reporting.webforms.localreport.render.aspx

    Unlocker: http://ccollomb.free.fr/unlocker/

    Please feel free to ask, if you have any more questions.

    Thanks,

    Jin Chen


    Jin Chen — MSFT

    • Marked as answer by

      Friday, July 10, 2009 9:51 AM

  • Как бороться с ошибкой «An error occurred during local report processing»? Возникает при попытке экспортировать фаил в формат PDF при работе с ReportViewer. RDLC создается динамически.Пользуюсь примером Generate RDLC dynamically — Table из http://www.gotreportviewer.com/. Подозреваю, что вот здесь- Add new node, натворила что-то не то

    C#
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    
      
    private MemoryStream GenerateRdl(List<string> allFields, List<string> selectedFields)
            {
                try
                {
                    MemoryStream ms = new MemoryStream();
                    RdlGenerator gen = new RdlGenerator();
     
                    gen.AllFields = allFields;
                    gen.SelectedFields = selectedFields;
                    gen.WriteXml(ms);
                    ms.Position = 0;
                    XmlDocument xDocument = new XmlDocument();
                    xDocument.Load(ms);
                    ms.Position = 0;
                 //Add new node
                   XmlNode newNode = xDocument.CreateNode("element", "RepeatOnNewPage", "http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition");
                    newNode.InnerText = "true";
                    xDocument.ChildNodes[1].ChildNodes[1].ChildNodes[0].ChildNodes[0].ChildNodes[1].ChildNodes[0].ChildNodes[0].AppendChild(newNode);
    //Может я этот узел не туда, куда надо поставила?
                    xDocument.Save(ms);
     
                    ms.Position = 0;
                    return ms;

    Вот тот RDLC, которыи получается и не может экспортироваться-см attach

    Вот код функции EXPORT

    C#
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    
     public string ExportReport(string filename)
            {
                Warning[] warnings;
                string[] streamids;
                string mimeType;
                string encoding;
                string filenameExtension;
     
                string deviceInfo =
                     "<DeviceInfo>" +
                     " <OutputFormat>PDF</OutputFormat>" +
                     " <PageWidth>11in</PageWidth>" +
                     " <PageHeight>8.5.0in</PageHeight>" +
                     " <MarginTop>0.05in</MarginTop>" +
                     " <MarginLeft>0.05in</MarginLeft>" +
                     " <MarginRight>0.05in</MarginRight>" +
                     " <MarginBottom>0.05in</MarginBottom>" +
     
                    " <RepeatOnNewPage>true</RepeatOnNewPage>" + 
                try
                {
                    byte[] bytes = reportViewer1.LocalReport.Render(
                        "PDF", deviceInfo, out mimeType, out encoding, out filenameExtension,   
                         out streamids, out warnings);
     
                    using (FileStream fs = new FileStream(filename, FileMode.Create))
                    {
                        fs.Write(bytes, 0, bytes.Length);
                        fs.Close();
                    }
                    return filename;
                }
                catch (Exception e)
                {
                    MessageBox.Show("Error in ExportReport - " +e.Message);
                    return "";
                }
            }
     
        }

    Очень нужна помощь Давно бьюсь! Спасибо!!!

    I was developed an wpf application in visual studio 2012. The application is working perfectly when i am running in visual studio . In my application i used the RDLC reports.
    When i was running the application in visual studio reports are getting the results, then i was created a setup file for the application.
    Then the application is installed in my machine and i performs the print operation. It will thoughs the error. Here is the exception:
    «

    An error occurred during local report processing.
    at Microsoft.Reporting.WinForms.LocalReport.EnsureExecutionSession()
    at Microsoft.Reporting.WinForms.LocalReport.SetParameters(IEnumerable`1 parameters)
    at Restaurant.Classes.ReportPrintClass..ctor(String _DataSourceName, DataTable _DataSourceValue, String _ReportPath, ReportParameter[] arrParams, Double pagewidth, Double pageheight, Double leftmargin, Double rightmargin, Double topmargin, Double bottommargin)
    at Restaurant.OrderDetailInCashierWindow.btnPrint_Click(Object sender, RoutedEventArgs e)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
    at System.Windows.Controls.Button.OnClick()
    at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
    at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
    at System.Windows.Input.InputManager.ProcessStagingArea()
    at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
    at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
    at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    at System.Windows.Window.ShowHelper(Object booleanBox)
    at System.Windows.Window.ShowDialog()
    at Restaurant.CashierOrdersListUserControl.btnShowDetails_Click(Object sender, RoutedEventArgs e)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
    at System.Windows.Controls.Button.OnClick()
    at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
    at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
    at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
    at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
    at System.Windows.Input.InputManager.ProcessStagingArea()
    at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
    at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
    at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
    at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
    at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
    at System.Windows.Window.ShowHelper(Object booleanBox)
    at System.Windows.Window.ShowDialog()
    at Restaurant.LoginWindow.CheckUser(String userName, String password)
    System.ApplicationException: The report definition for report ‘Report_Receipt’ has not been specified —> System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:UsersRoopasoftDesktopReportSrcReport_Receipt.rdlc’.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
    at Microsoft.ReportingServices.StandalonePreviewStore.GetReportDefinition(PreviewItemContext itemContext)
    — End of inner exception stack trace —
    at Microsoft.ReportingServices.StandalonePreviewStore.GetReportDefinition(PreviewItemContext itemContext)
    at Microsoft.Reporting.LocalService.GetCompiledReport(PreviewItemContext itemContext, Boolean rebuild, ControlSnapshot& snapshot)
    at Microsoft.Reporting.LocalService.CompileReport()
    at Microsoft.Reporting.WinForms.LocalReport.EnsureExecutionSession()
    «

    Actually i was added the ReportViewer in Prerequesties in the installation process.

    I am new to using SSRS. I am using a .rdlc file for report generation in a PDF with VS 2012. When I tried to set the parameters like

    ReportParameter param = new ReportParameter(kvp.Key, kvp.Value);
    LocalReport.SetParameters(param);
    

    This throws an exception:

    An error occurred during local report processing..The definition of the report » is invalid.. Could not load file or assembly ‘System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Access is denied.

    More details:

    {Microsoft.Reporting.WebForms.LocalProcessingException: An error occurred during local report processing. ---> Microsoft.Reporting.DefinitionInvalidException: The definition of the report '' is invalid. ---> System.IO.FileLoadException: Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied.
       at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
       at System.Activator.CreateInstance(String assemblyString, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(String assemblyName, String typeName)
       at System.AppDomain.CreateInstance(String assemblyName, String typeName)
       at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName)
       at System.AppDomain.CreateAppDomainManager()
       at System.AppDomain.Setup(Object arg)
       at System.AppDomain.nCreateDomain(String friendlyName, AppDomainSetup setup, Evidence providedSecurityInfo, Evidence creatorsSecurityInfo, IntPtr parentSecurityDescriptor)
       at System.AppDomainManager.CreateDomainHelper(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
       at System.AppDomainManager.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup appDomainInfo)
       at System.AppDomain.InternalCreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
       at System.AppDomain.CreateDomain(String friendlyName, Evidence securityInfo, AppDomainSetup info)
       at Microsoft.Reporting.ReportCompiler.CreateCompilationTempAppDomain()
       at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
       --- End of inner exception stack trace ---
       at Microsoft.Reporting.ReportCompiler.CompileReport(ICatalogItemContext context, Byte[] reportDefinition, Boolean generateExpressionHostWithRefusedPermissions, ControlSnapshot& snapshot)
       at Microsoft.Reporting.LocalService.GetCompiledReport(PreviewItemContext itemContext, Boolean rebuild, ControlSnapshot& snapshot)
       at Microsoft.Reporting.LocalService.CompileReport()
       at Microsoft.Reporting.LocalService.Microsoft.Reporting.ILocalProcessingHost.CompileReport()
       at Microsoft.Reporting.WebForms.LocalReport.EnsureExecutionSession()
       --- End of inner exception stack trace ---
       at Microsoft.Reporting.WebForms.LocalReport.EnsureExecutionSession()
       at Microsoft.Reporting.WebForms.LocalReport.SetParameters(IEnumerable1 parameters)
       at Microsoft.Reporting.WebForms.Report.SetParameters(ReportParameter parameter)
    

    What am I missing. In some posts, it ‘s been advised to use missing Microsoft.ReportViewer.PorcessingObjectMode.dll. I did that so I have all the required dlls like:

    -    Microsoft.ReportViewer.Common.dll
    -    Microsoft.ReportViewer.WebForms.dll
    -    Microsoft.ReportViewer.ProcessingObjectModel.dll
    

    are there.

    I referred to this post. But still I could not get this done.

    I am using Windows 10, language Serbian, SQL Management Studio 2016 and can’t use Database reports because there is error:

    An error occurred during local report processing Culture is not
    supported Parameter name: culture 3072 (0x0c00) is invalid culture
    identifier.

    I try with different settings for Windows 10 — language (English), try with different settings for SSMS (English) but got same error.

    Do you have idea how to solve this?

    P.S. My Windows 10 system locale settings:

    Get-WinSystemLocale
    LCID       Name            DisplayName
    ----       ----            ----
    9242       sr-Latin-RS     Serbian(Latin, Serbia)
    

    asked May 7, 2017 at 6:48

    Jelena's user avatar

    JelenaJelena

    1331 gold badge1 silver badge7 bronze badges

    I think 3072 (0x0c00) is an invalid locale ID, at least according to this. So this looks like a corrupted Windows installation, perhaps from a flaky disk (eg. a byte overwrite of a locale 0x0c1a, which is the code for «Serbia and Montenegro (Former)»).

    You can try changing the current locale from Control Panel.

    answered May 7, 2017 at 7:06

    Remus Rusanu's user avatar

    Remus RusanuRemus Rusanu

    51.4k3 gold badges93 silver badges171 bronze badges

    1

    Had the same error.

    Turns out that it was my setting in Region -> Formats -> Format. When it was on English (World) or English (Europe), I would get this error. Setting it to English (United States) solves it.

    I’m guessing that English (World) or English (Europe) were new formats with Windows 10, and SSMS is not prepared for it.

    answered Oct 11, 2017 at 8:47

    d.hernandez's user avatar

    d.hernandezd.hernandez

    3212 silver badges3 bronze badges

    6

    No need to change the RegEdit Register Editor.

    If you are facing the Error 0xc002f210: Preparation SQL Task 1: Executing the query "Culture is not supported. Parameter name: culture 3072 (0x0c00) is an invalid culture identifier." just set the Regional format to English (United States):

    enter image description here

    This also works if you are trying to import a flat file to Azure SQL Database

    answered Nov 22, 2022 at 9:39

    Francesco Mantovani's user avatar

    Like this post? Please share to your friends:
  • An error occurred during loading please try again later error code 4 vk
  • An error occurred during installation ubuntu server
  • An error occurred during decryption
  • An error occurred during authentication vcenter
  • An error occurred during authentication back to login screen