The dreaded RsClientController is undefined - thread RRS feed

  • Question

  • My... I've searched the internet but not a single *real* solution to find...


    OK, so I've got this existing VS2005 solution and added a simple .aspx page, put a reportviewer control on it, made the link to the .rdlc report and ready set go... immediate a javascript error box with 'RSClientController is undefined' message. I keep on getting this error...


    This is the situation

     * installed Visual Studio SP 1 for my VS2005 Standard Edition

     * installed the ReportViewer patch to upgrade webforms dll to latest version

     * checked mappings to verify if .axd is unchecked at 'verify if file exists' (and the aspnet_isapi.dll is pointing to .NET 2.0)

     * made sure InProc session state is enabled

     * made sure there's no security issue (when calling Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=8.0.50727.817&Name=Scripts.ReportViewer.js I get the contents of the reportviewer.js file.)


    My configuration: VS2005 Standard with SP1, Sql Server Express, IIS 5.1, Windows XP Pro, .NET 2.0.


    I've tried a little hack by including the content of reportviewer.js in another javascript file and to make sure that file is already loaded. This worked, but then it fails on another line (rsReport is undefined).


    Please help otherwise this reporting services effort is just a waste of time and I'll need to discourage my clients from using it Sad



    Monday, April 2, 2007 8:07 PM

All replies

  • Well.. I fixed it. Just created a new VS2005 project, moved all webforms and projects and now the problem is gone.


    I think the problem only occurs in solutions which are ported from VS2003 to VS2005 (which was here the case).



    Wednesday, April 4, 2007 5:50 PM
  • This fixed it for me - it's stupid, but I've found it works for other .axd related situations - put an empty file called Reserved.ReportViewerWebControl.axd in the root for you application.
    • Proposed as answer by Vivl Thursday, July 16, 2009 5:59 AM
    Wednesday, April 18, 2007 5:50 PM
  • Hello there,

    I have the same problem while using Report Viewer Control. It gives me an error in the format below. How do I add the Reserved.ReportViewerWebControl.axd ? I have tried adding an empty Reserved.ReportViewerWebControl.axd file in the root of the application but I still get the same error. COuld you please help me with this? Thank you.

    Server Error in Application "Default Web Site/MyWebSite"

    HTTP Error 404.3 - Not Found

    Description: The page you are requesting cannot be served because of the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognized, and is not allowed.

    Error Code: 0x80070032

    Notification: ExecuteRequestHandler

    Module: StaticFileModule

    Requested URL: http://localhost:80/MyWebSite/Reserved.ReportViewerWebControl.axd?OpType=DocMapReport&ClientController=ClientControllerctl00_ContentPlaceHolder1_ReportViewer2&ReportUrl=%2fMyWebSite%2fReserved.ReportViewerWebControl.axd%3fMode%3dtrue%26ReportID%3d36eb799d608e4595a9e0a7302333fb5b%26ControlID%3d2e950ec92e154ddfb63e7387b51c5e19%26Culture%3d1033%26UICulture%3d1033%26ReportStack%3d1%26OpType%3dReportArea%26Controller%3dClientControllerctl00_ContentPlaceHolder1_ReportViewer2%26PageNumber%3d1%26ZoomMode%3dPercent%26ZoomPct%3d100%26ReloadDocMap%3dtrue%26SearchStartPage%3d0%26LinkTarget%3d_top

    Physical Path: C:\Projects\Code\MyWebSite\Reserved.ReportViewerWebControl.axd

    Logon User: Anonymous

    Logon Method: Anonymous

    Handler: StaticFile

    Most likely causes:

    • It is possible that a handler mapping is missing. By default, the static file handler processes all content.
    • The feature you are trying to use may not be installed.
    • The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should not download, such as .ASPX pages or .config files.)

    What you can try:

    • In system.webServer/handlers:
    • Ensure that the expected handler for the current page is mapped.
    • Pay careful attention to preconditions (e.g. runtimeVersion, pipelineMode, bitness) and compare them to the settings for your application pool.
    • Pay careful attention to typographical errors in the expected handler line.
    • Please verify that the feature you are trying to use is installed.
    • Verify that the MIME map is enabled or add the MIME map for the Web site using the command-line tool appcmd.exe.
      1. Open a command prompt and change directory to %windir%\system32\inetsrv.
      2. To set a MIME type, use the following syntax: appcmd set config /sectionTongue TiedtaticContent /+[fileExtension='string',mimeType='string']
      3. The variable fileExtension string is the file name extension and the variable mimeType string is the file type description.
      4. For example, to add a MIME map for a file which has the extension ".xyz", type the following at the command prompt, and then press Enter:
      5. appcmd set config /sectionTongue TiedtaticContent /+[fileExtension='.xyz',mimeType='text/plain']
      Warning: Ensure that this MIME mapping is needed for your Web server before adding it to the list. Configuration files such as .CONFIG or dynamic scripting pages such as .ASP or .ASPX, should not be downloaded directly and should always be processed through a handler. Other files such as database files or those used to store configuration, like .XML or .MDF, are sometimes used to store configuration information. Determine if clients can download these file types before enabling them.
    • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

    More Information... This error occurs when the file extension of the requested URL is for a MIME type that is not configured on the server. You can add a MIME type for the file extension for files that are not dynamic scripting pages, database, or configuration files. Process those file types using a handler. You should not allows direct downloads of dynamic scripting pages, database or configuration files.

    Server Version Information: Internet Information Services 7.0.
    Monday, May 14, 2007 8:12 PM
  • Total WTF....Why?????
    Thursday, July 16, 2009 5:59 AM
  • I'm in disbelief that this actually worked but just wanted to say thanks for the post.  I just added it in and magically everything started working.
    Wednesday, October 13, 2010 3:07 PM