DrillThrough Report Error: rsInvalidItemPath

RS 2005 rsInvalidItemPath Error.
I am calling a drillthrough report from the ReportViewer control in a
VS 2005 web application. My report structure is as follows:
ParentReport (drillthrough)
ChildReport1(drillthrough)
ChildReport2
I can drill from Parent Report to Child1, but when I drill from Child1
to Child2, I get the following error:
The path of the item "(null)" is not valid. The path must be less than
260 characters long and must start with slash. Other restrictions
apply
Stack-Trace:
Microsoft.Reporting.WebForms.ReportServerException: The path of the
item "(null)" is not valid. The path must be less than 260 characters
long and must start with slash. Other restrictions apply.
(rsInvalidItemPath) at
Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
drillthroughId, String& reportPath) at
Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
drillthroughID) at
Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
actionType, String actionParam, Int32& currentPage, Boolean&
pageSetByEvent, String& navigationID, String& searchText, Int32&
searchStartPage, String& alertMessage, Report& targetReport) at
Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
Report Path: /screensave/screensave
Report URL: http://myserver/reportserver
IsDrillThrough: True
I am passing two parameters.
Any recommendations would be much appreciated.
Thanks.On Mar 20, 2:25 pm, "Rob" <rtemp...@.gmail.com> wrote:
> RS 2005 rsInvalidItemPath Error.
> I am calling a drillthrough report from the ReportViewer control in a
> VS 2005 web application. My report structure is as follows:
> ParentReport (drillthrough)
> ChildReport1(drillthrough)
> ChildReport2
> I can drill from Parent Report to Child1, but when I drill from Child1
> to Child2, I get the following error:
> The path of the item "(null)" is not valid. The path must be less than
> 260 characters long and must start with slash. Other restrictions
> apply
> Stack-Trace:
> Microsoft.Reporting.WebForms.ReportServerException: The path of the
> item "(null)" is not valid. The path must be less than 260 characters
> long and must start with slash. Other restrictions apply.
> (rsInvalidItemPath) at
> Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
> drillthroughId, String& reportPath) at
> Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
> drillthroughID) at
> Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
> actionType, String actionParam, Int32& currentPage, Boolean&
> pageSetByEvent, String& navigationID, String& searchText, Int32&
> searchStartPage, String& alertMessage, Report& targetReport) at
> Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHan=dl=ADer.RaisePostBackEvent(String
> eventArgument)
> Report Path: /screensave/screensave
> Report URL:http://myserver/reportserver
> IsDrillThrough: True
> I am passing two parameters.
> Any recommendations would be much appreciated.
> Thanks.
Just to add one more thing, when I run this from Report Manager which
is located on the same machine as the Report Server, I do not get this
error. It must be in the exchange between the reportviewer control on
the web app and the web service on the reportserver. Does anyone know
how this connection takes place in a drill down scenario? I assume
that when the web application (with reportviewer control) makes a call
to the web service, it opens the authenticated connection. Then at
each drill down event, does it make a round trip back to the web app?
It is on the third round trip that I see the error.
Thanks again..|||Hi Rob,
I am getting a similar problem as well. What happens in my case is,
I have a parent report and from it I open the drill down. This works fine as
you pointed out.
I have kept an textbox in the drilled down report which has a hyperlink to
take it back to the parent report. This works fine on the Report server, but
fails on the Web server inside the Report viewer control.
My assumption is that as the viewer opens the page, on subsequent drill
downs, the path keeps on increasing in length and eventually goes above limit.
I will let you know if I find any solution for this. Please keep me posted
as well if you get any solutions yourself.
Harsh
"Rob" wrote:
> On Mar 20, 2:25 pm, "Rob" <rtemp...@.gmail.com> wrote:
> > RS 2005 rsInvalidItemPath Error.
> >
> > I am calling a drillthrough report from the ReportViewer control in a
> > VS 2005 web application. My report structure is as follows:
> >
> > ParentReport (drillthrough)
> > ChildReport1(drillthrough)
> > ChildReport2
> >
> > I can drill from Parent Report to Child1, but when I drill from Child1
> > to Child2, I get the following error:
> >
> > The path of the item "(null)" is not valid. The path must be less than
> > 260 characters long and must start with slash. Other restrictions
> > apply
> >
> > Stack-Trace:
> > Microsoft.Reporting.WebForms.ReportServerException: The path of the
> > item "(null)" is not valid. The path must be less than 260 characters
> > long and must start with slash. Other restrictions apply.
> > (rsInvalidItemPath) at
> > Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
> > drillthroughId, String& reportPath) at
> > Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
> > drillthroughID) at
> > Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
> > actionType, String actionParam, Int32& currentPage, Boolean&
> > pageSetByEvent, String& navigationID, String& searchText, Int32&
> > searchStartPage, String& alertMessage, Report& targetReport) at
> > Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHandl­er.RaisePostBackEvent(String
> > eventArgument)
> >
> > Report Path: /screensave/screensave
> > Report URL:http://myserver/reportserver
> > IsDrillThrough: True
> >
> > I am passing two parameters.
> >
> > Any recommendations would be much appreciated.
> >
> > Thanks.
> Just to add one more thing, when I run this from Report Manager which
> is located on the same machine as the Report Server, I do not get this
> error. It must be in the exchange between the reportviewer control on
> the web app and the web service on the reportserver. Does anyone know
> how this connection takes place in a drill down scenario? I assume
> that when the web application (with reportviewer control) makes a call
> to the web service, it opens the authenticated connection. Then at
> each drill down event, does it make a round trip back to the web app?
> It is on the third round trip that I see the error.
> Thanks again..
>