Epicor 10 SSRS Linking New Sub Report Failure

Epicor ERP 10
1

With modifying an existing SSRS report from E10 and making a few changes to an sub report. When I insert the new sub report field and navigate to sub report properties and browse to the correct directory and click the appropriate report file. When trying to sync the data set I get the following error:

I have even tried linking an existing subreport and I still get the following error (I am also doing all of this on the report server)

Report is “Job Traveler”
Sub report is “Raw_MaterialComponent”

Error:
System.Web.Services.Protocols.SoapException: The path of the item ‘/EpicorTest10/reports/CustomReports/JobTraveler //EpicorTest10/reports/CustomReports/JobTraveler/T raveler_RawMaterialComponents_Portrait’ 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 ‘/EpicorTest10/reports/CustomReports/JobTraveler //EpicorTest10/reports/CustomReports/JobTraveler/T raveler_RawMaterialComponents_Portrait’ 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.
at Microsoft.ReportingServices.Library.ReportingServi ce2010Impl.GetItemDefinition(String ItemPath, Byte[]& Definition)
at Microsoft.ReportingServices.WebServer.ReportingSer vice2010.GetItemDefinition(String ItemPath, Byte[]& Definition)

2

Just a quick thought, but the error message shows ‘T
raveler_RawMaterialComponents_Portrait’, with a space between the Two and
the r in traveler…

Norman Hutchins
Systems Administrator
Howell Laboratories, Inc.

3

Check your SQL. This error can be caused by the query syntax missing commas, spaces etc. Carefully go through your query. Possibly run or execute it in Management studio to detect and correct the errors.

4

I have had similar issues moving a SSRS report (with Sub-Reports) from a Test → Production environments. Even though I changed the path within the sub-report properties, I would still get the error. To correct the issue, I used a text-editor and opened the RDL directly and looked for the report path of the sub-report. It still had the “test” path even though I was selecting the report’s subreport production location within the Report Designer.
I manually made the path to be “production” and report worked.