Report Server - SharePoint: IReportViewerMessages or could not be found

If you have Report Server running in a virtual directory under a SharePoint web app.

Error: The type Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c does not implement IReportViewerMessages or could not be found.

Cause: Look in your SharePoint web.config file you'll see
<add key="ReportViewerMessages" value="Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />.

Fix: I looked at the Microsoft.SharePoint.Portal.Analytics Namespace and couldn't find a UI.ReportViewerMessages, so I just removed it from the web.config and I haven't experienced any issues.
You can also remove the setting from your ReportServer web.config's just add:

<appSettings>
 <remove key="ReportViewerMessages" />

</appSettings>

Report Server Error: The request failed with HTTP status 400: Bad Request

This also applies to the error message: Microsoft.ReportingServices.UI.Global+RSWebServiceWrapper+CantCommunicateWithReportServerException: The report server is not responding. Verify that the report server is running and can be accessed from this computer.

This took me a little while to figure out, but my initial suspicion was that it was related to the fact I was using it in a Host Header site, ei: I had changed lmhosts or I had multiple web sites using port 80.

Cause:

Report server uses the machine name when setting the config files, but when it tries to reference the url it can't be found because it's in another web site. In my case the server was called MOSSDEV, and the report server virtual directories were in a web site called premisys.

Fix:

1. Open "RSWebApplication.config" in the "Report Manager Virtual Directory". Right click the virtual directory icon in inetmgr, choose open. Default is: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager
2. Enter the full Report Server URL in the <ReportServerUrl> node. Eg: <ReportServerUrl>http://premisys/ReportServer</ReportServerUrl>
3. Delete the <ReportServerVirtualDirectory> value but not the node.
4. Open "rsreportserver.config" in the "Report Server Virtual Directory". Default is: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer
5. Change the <urlroot>http://<servername>/ReportServer</urlroot> to match your URL.

Application Event Log: Unable to connect publishing custom string handler for output caching.

After adding the Reports Services virtual directories to a sharepoint site/web application you see the below in the event log.

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Publishing Cache
Event ID: 5785
Date: 21/05/2008
Time: 3:01:52 PM
User: N/A
Computer:
Description:
Unable to connect publishing custom string handler for output caching. IIS Instance Id is '1957155781', Url is 'http://localhost/ReportServer/ReportService2005.asmx'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Cause: microsoft.sharepoint.publishing.publishinghttpmodule is trying to cache an unmanaged path.

Fix: Remove this httpmodule from the ./ReportServer virtual directory web.config.

Steps:
1. Open the web.config file (D:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer\web.config)
2. Locate the <httpModules> node, if it's not there create it below the <httpHandlers> node.
3. Add the following <remove name="PublishingHttpModule" />.

Everytime you call a report or the reportserver URL/web service SharePoint tries to turn caching on and it's not a managed path it throws an error, so we need to remove the module in the reportserver.