In which reference is the schema information for Telerik.Reporting?

6 posts, 0 answers
  1. Jon
    Jon avatar
    17 posts
    Member since:
    Jul 2013

    Posted 06 Sep Link to this post

    Following the instructions online and I'm receiving the error "Could not find schema information for the element 'Telerik.Reporting'" in Web.config.

     In which reference is the schema information?

  2. Stef
    Admin
    Stef avatar
    3036 posts

    Posted 07 Sep Link to this post

    Hi Jon,

    Please check if you have references to the required Telerik Reporting assemblies, and if their CopyLocal is set to true in Visual Studio. In case of an MVC project, namespaces must be declared in the Views folder's web.config.

    In case you added a Telerik.Reporting section in the web.config, please check if it is declared - Telerik Reporting Configuration Section.


    If you need further help, please open a support ticket and send us the problematic project including details where and when the error occurs.

    Regards,
    Stef
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. DevCraft banner
  4. Jon
    Jon avatar
    17 posts
    Member since:
    Jul 2013

    Posted 07 Sep in reply to Stef Link to this post

    Here is what I get when I open your link:

    Server Error in '/reporting' Application.

    Runtime ErrorDescription: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>
    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

    I have not found any benefit in submitting support tickets since they are not answered.

  5. Stef
    Admin
    Stef avatar
    3036 posts

    Posted 08 Sep Link to this post

    Hello Jon,

    The provided details are from the preview in browser of the running application. The details are not sufficient to pinpoint the problem.

    Please use a support ticket to submit a demo project including the custom settings which reproduce the problem. Providing us a project will be helpful for troubleshooting the other issues you mentioned in:
    Include also screenshots of the error in VS and in browser.


    In addition, we do not guarantee replies by Telerik representatives in forums in a timely manner. The usage of the support ticketing system guaranties that your inquiry will be received by the support team.

    Regards,
    Stef
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  6. Jon
    Jon avatar
    17 posts
    Member since:
    Jul 2013

    Posted 08 Sep in reply to Stef Link to this post

    I'll give you a clue - the error occurs when you follow the official Telerik documentation on a new project.
  7. Stef
    Admin
    Stef avatar
    3036 posts

    Posted 09 Sep Link to this post

    Hello Jon,

    The warnings you receive are related to config settings.
    The default implementation of the Reporting REST service includes all cache settings in code. The second option is to use the configuration file, which requires a Telerik Reporting section declaration.

    The article is http://docs.telerik.com/reporting/telerik-reporting-rest-implementing-http-service.

    Thus I guess there are lines as follow in your web.config:
    <configuration>
        <configSections>
          <section
                  name="Telerik.Reporting"
                  type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting, Version=10.1.16.816, Culture=neutral, PublicKeyToken=a9d7983dfcc261be"
                  allowLocation="true"
                  allowDefinition="Everywhere"/>
        </configSections>
      <Telerik.Reporting>
        <restReportService hostAppId="Application1" reportSharingTimeout="10" clientSessionTimeout="10">
          <reportResolver provider="type" />
          <storage provider="file" />
        </restReportService>
      </Telerik.Reporting>
    ......

    There is no XSD which is the reason for the information messages - How to fix Error: “Could not find schema information for the attribute/element” by creating schema. If you build the application with closed web.config the messages will not appear. The application must be runnable regardless the messages.

    We will consider providing such XSD. Please log a feature request in our public feedback portal where other community members can vote for it. Based on the demand the feature can be included in a consecutive release.



    Since this is almost a blind guess, please post the settings as plain text or open a support ticket and send us a demo project that illustrates them. If you have concerns to share your project in a private thread, please let us know.
    If you prefer to share the project in public, note that forums allow only image attachments and it is not recommended. In any case, remove any DLLs included in the project.

    Regards,
    Stef
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top
DevCraft banner