Ssrs on Matt Thornton

SSRS: the given path's format is not supported

Fri, 16 Mar 2018 13:57:33 +0000

As an aside to my other post on SSRS in SharePoint integrated mode, this is a niggly little issue I encountered.

If you find yourself needing to edit a published report and, for whatever reason can’t go back to source to make the change, then a reasonable option is to download a copy of the report from SharePoint and then open it up in your Visual Studio of choice and make the edits. RDL files are pretty great at encapsulating everything they need to run within a single file (they are just XML files, after all) so this is a workable approach.

SSRS + Visual Studio + SP Integrated Mode

Fri, 16 Mar 2018 13:44:30 +0000

Visual Studio is a good option for designing SSRS reports. Now, that is. But years ago we had a different toolset. One of those around the 2009/2010 time was ‘Business Intelligence Developer Studio’. This was effecting a Visual Studio shell that had report templates for the various SQL Business Intelligence suite (e.g., SSIS, SSRS, SSAS.) and was installed from the main SQL Server installer. This then morphed in to SQL Server Data Tools which was available as a standalone package.

Event ID: 1108 SQL Server Reporting Services cannot load the SQLPDW extension

Thu, 27 Feb 2014 17:33:57 +0000

This event log error will occur in Sharepoint 2010 or SharePoint 2013 environments with SQL Server 2012 and SSRS in integrated mode. You will see either

“SQL Server Reporting Services Shared Service cannot load the SQLPDW extension. (Application: [service app name]. CorrelationId: etc.)”

“SQL Server Reporting Services Shared Service cannot load the TERADATA extension. (Application: [service app name]. CorrelationId: etc.)”

This link explains some of the reasoning behind it.

This error occurs because the Teradata extension is registered in the Reporting Services configuration file by default, but the Teradata assemblies are not shipped with SQL Server 2008 or as part of the .NET Framework. If the error message does not bother you, you can ignore the error when it is logged.

SharePoint 2010 + SSRS Integrated mode + deploy + login prompt

Wed, 02 Oct 2013 10:52:48 +0000

If you try to deploy an SSRS report from Visual Studio to your SharePoint environment, where SSRS has been configured in Integrated Mode, using the built-in deployment mechanism, you may encounter a situation where you are endlessly prompted for login boxes, and no account details seem to help.

There is some useful info out there about what causes this - typically a mismatch where you’re using Kerberos authentication. There’s a good post and some resolution here.

SSRS error: Operation is not valid due to the current state of the object

Fri, 10 Feb 2012 12:27:50 +0000

If you’re using SSRS in SharePoint integrated mode, you may come across this error when using report parameters that have a high number of items in them. A recent security bulletin highlighted some issues and vulnerabilities in ASP.net, and a patch was released to cover some of the items. One of these was the maximum number of items you can have in a collection. If you exceed the limit, then you’ll likely get an error like:

SharePoint 2010 Foundation + SQL Server Reporting Services Integrated mode installation issues: Failed to establish connection with report server, 401 errors and more

Thu, 09 Feb 2012 18:50:28 +0000

You may be trying to set up SharePoint 2010 to act as the report repository for SQL Server Reporting Services report. This is a pretty nifty feature, especially as it’s available in the Foundation (i.e., Free) version of SharePoint. There is a pretty exhaustive guide on how to set it up and for extra help, this blog post is pretty good too, and if you follow the steps, you get pretty far. However, if you’re in a multiple server setup (i.e. your SQL server isn’t on the same server as your Central Admin) you will likely encounter configuration issues surrounding authentication, and there is a great deal of confusion about what it all means - especially when it comes down to Kerberos. That’s beyond the scope of this post - what I’m covering here is one very annoying issue that there was no definitive answer to on the web.

Assuming you get all the server parts setup and Reporting Services configured, you might find that you can browse to your report server address on the machine hosting reporting services, but, if you try to browse to that address from anywhere else, you’ll get an endless stream of login boxes, and no credentials will work. Also, if you go to Central Admin and go to General Application Settings > Reporting Services Integration, when you fill in the details to connect to reporting services, you’ll hit an error like:

Failed to establish connection with report server. Verify the server URL is correct or review ULS logs for more information. Product area: SQL Server Reporting Services, Category: Configuration Pages

and, in the ULS logs, an error like:

SQL Server Reporting Services Configuration Pages Failed to retrieve RS configuration information: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

Here’s ~~how I fixed it~~ my workaround.