Displaying Parameter in RDLC report cause error RRS feed

  • Question

  • User-1716951449 posted

    I'm running a RDLC with local mode processing.

    I can pass parameter no problem.

    the problem is when I want to display/render that parameter (string), i keep getting unhelpful error in report viewer.

    removing that parameter textbox, it will work.

    Thursday, November 2, 2017 8:14 AM


All replies

  • User347430248 posted

    Hi Kelmen,

    is this a same issue like you mentioned in thread below?

    RDLC ASP.NET report viewer - default empty datasource

    if not , please try to provide detailed information about your issue and steps to reproduce the issue.

    you said that error is unhelpful. but you did not post the error.

    if you post the error then it will be helpful for us to understand the issue in better way.

    it is also possible that you are not passing the value properly causing the error.

    so try to provide the detailed information.

    we will try to provide you further suggestions to solve the issue.



    Thursday, November 2, 2017 8:53 AM
  • User-1716951449 posted

    the error is:

    • An unexpected error occurred in Report Processing.
      • Exception has been thrown by the target of an invocation.
        • The type initializer for 'System.Diagnostics.Activity' threw an exception.
          • Operation could destabilize the runtime.

    this is the parameter setting code:

                var rptParams = new List<ReportParameter>();
                rptParams.Add(new ReportParameter("Disclaimer", @"Disclaimer: blablabla."));

    in the report, i just change a textbox expression from blank (not showing anything) or =Parameters!Disclaimer.Value (attempt to show the parameter)

    the later will get error.

    this is from the rdlc, i only use the designer to work.

        <ReportParameter Name="Disclaimer">

    Thursday, November 2, 2017 9:50 AM
  • User-1716951449 posted

    stumble on this:


    then i remove/disable anything about Microsoft.ApplicationInsights (2.4) in web.config, and it worked

    not using anything of Microsoft.ApplicationInsights, so it can go

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, November 3, 2017 3:15 AM