Sharepoint/SSRS: The full path must be less than 260 characters long

All replies

• 

  

  0

  Sign in to vote

  After some tinkering, I now see that I can save reports to \\intranet\sharepoint\ComnanyReports\MyReports but not http://intranet/sharepoint/CompanyReports/MyReports. 

  And although the report saved, when trying to view on the server I still get the same error:

  The path of the item 'http://intranet/sharepoint/CompanyReports/MyReports/test.rdl' 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. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'http://intranet/sharepoint/CompanyReports/MyReports/test.rdl' 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.

  Maybe it is an IIS issue? 

   

  Friday, May 13, 2011 6:48 PM
• 

  

  0

  Sign in to vote

  Hi,

  Please visit the links below that will help you resolve your issues.

  http://www.microsoft.com/products/ee/transform.aspx?evtsrc=microsoft.reportingservices.diagnostics.utilities.errorstrings.resources.strings&evtid=rsinvaliditemname&prodname=sql%20server%20reporting%20services&prodver=8.00&lcid=1033

  http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/ff6bc625-deb7-4c34-a296-b96b59a967e6

  hth,

  ---

  Chirag Patel, MCTS
  @techChirag
  techChirag.com

  • Marked as answer by Leoyi Sun Friday, May 20, 2011 9:46 AM
  • Unmarked as answer by Mike Walsh FIN Tuesday, May 24, 2011 3:41 PM

  Sunday, May 15, 2011 9:16 PM
• 

  

  0

  Sign in to vote

  No, they do not relate to my issue.  I'm not using special characters anywhere in the URL (: ? ; @ ' = + $ , \ * > < | . " : =) like the first article implies, and I'm not doing any coding which pertians to the second article.

  Tuesday, May 24, 2011 2:57 PM
• 

  

  0

  Sign in to vote

  Well, I opened a ticket with MS Support and it turns out the farm servers were not communicating because I made the silly mistake of thinking my two servers were on the same farm, when they weren't.

  I have a separate frontend of Sharepoint running on my Reports Server.  And on that server, reports work fine, and I do not get the error above.  We now just need to join the Reports Server to the farm.  We need both servers to be on the -exact- same version of Sharepoint, so I will be doing that tomorrow after we do the standard post-upgrade reboot of the production SQL server.

  • Marked as answer by _sotomo_ Wednesday, May 25, 2011 9:11 PM

  Wednesday, May 25, 2011 9:11 PM