完整路径必须少于 260 个字符 - SSRS

Question

I point one of the menu items in my web application to the below path

http://localhost/Reports/Pages/Folder.aspx?ItemPath=/Parent Reports/Child

Reports

When I click on it the report manager UI displays the following message:

The path of the item ' http://localhost/Reports/Pages/Folder.aspx?ItemPath=/Parent Reports/Child Reports ' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.

Answer 1

I had the same issue when one of my developers were trying to edit a report in ssrs, using the report builder

the problem started when he was accessing the data source which was on a different path.

I soon as I granted that specific data source, the permissions below, it all worked fine:

Answer 2

There is certainly a 260 path limit in Windows (or is it NTFS?). Perhaps the path to your solution folder and child folders and file name for the aspx page that services that request is longer than 260 characters. If this is the case, try moving the solution folder closer to the c:\\ root and try again.

Answer 3

Note that Windows does implement a solution to the legacy MS-DOS 260 char path limit. It's the Long UNC path format, which starts with \\\\?\\ such as \\\\?\\c:\\path\\file.txt .

If you have access to the source code of the web service producing this error, you might try digging around in the service code that converts the URL arguments into local file paths and see if tacking the \\?\\ on the front helps matters at all.

It also seems odd that you would get this file path error message on a URL. Check your code (or the code of the web service) to see if somebody is using Path functions where they should be using URI functions.

Finally, note that your example contains space characters, both in the path and in the URI. Space characters are definitely prohibited in URIs; you will need to URI escape them with %20 to make them valid URIs. That could be the real cause of the problem - the web service is not actually receiving the whole URI you're sending, since URI parsing will stop at the first space character.