Wednesday, February 15, 2012

Error: Subreport could not be shown

Hi,
I've been searching everywhere to try and find the solution to my problem.
I have a main report with a subreport. The first row renders the sub report
just fine but for the rest of the rows it gives the error: Error: Subreport
could not be shown.
The parameters I'm passing are valid, and I am also casting them to the data
type the sub report is expecting. Is this some sort of SSRS bug? There
doesn't seem to be a valid solution to this problem. Any help would be much
appreciated.
Thanks,
dev88Yeah, we had the same problem here. In our case, it looks like it has to do
with basing the the Main report and Sub-report on the same Report Model. I
don't know all the details, but when it tries to add the second instance of
the same sup-report, it finds it already has an index entry (where? I'm not
sure) with that id, and can't / won't show it again. Hence, the "Subreport
could not be shown".
Our workaround : rebuild the Sub-Reports without using the Report model; go
directly to the database, and use SQL to bring back the data with same field
names. Oh, and the field names are case-sensitive, so watch out.
I hear there may be fix for this in SP2, when it arrives. (However, I also
heard Elvis playing in the room next door, so my hearing may be bad! :) )
Also, your problem may be something different. But, this worked for us.
Mark
"dev88" <dev88@.discussions.microsoft.com> wrote in message
news:D1FD303C-D618-4F37-B850-CEB7B84E0D81@.microsoft.com...
> Hi,
> I've been searching everywhere to try and find the solution to my problem.
> I have a main report with a subreport. The first row renders the sub
> report
> just fine but for the rest of the rows it gives the error: Error:
> Subreport
> could not be shown.
> The parameters I'm passing are valid, and I am also casting them to the
> data
> type the sub report is expecting. Is this some sort of SSRS bug? There
> doesn't seem to be a valid solution to this problem. Any help would be
> much
> appreciated.
> Thanks,
> dev88|||Thanks for the advice Mark. This is quite a strange problem. My parent
report and my subreport both connect to a shared datasource which is an
analysis services database, therefore I didn't need to use a Report Model.
I did however try to change the datasource of my parent report to get the
data directly from a sql database (so the parent report and sub report
weren't sharing a connection) and now half the subreports are displayed
properly while the other half still display the same error "Error: Subreport
could not be shown". I'm half way there, anyone have any other suggestions?
Thanks.
"theMark" wrote:
> Yeah, we had the same problem here. In our case, it looks like it has to do
> with basing the the Main report and Sub-report on the same Report Model. I
> don't know all the details, but when it tries to add the second instance of
> the same sup-report, it finds it already has an index entry (where? I'm not
> sure) with that id, and can't / won't show it again. Hence, the "Subreport
> could not be shown".
> Our workaround : rebuild the Sub-Reports without using the Report model; go
> directly to the database, and use SQL to bring back the data with same field
> names. Oh, and the field names are case-sensitive, so watch out.
> I hear there may be fix for this in SP2, when it arrives. (However, I also
> heard Elvis playing in the room next door, so my hearing may be bad! :) )
> Also, your problem may be something different. But, this worked for us.
> Mark
>
> "dev88" <dev88@.discussions.microsoft.com> wrote in message
> news:D1FD303C-D618-4F37-B850-CEB7B84E0D81@.microsoft.com...
> > Hi,
> >
> > I've been searching everywhere to try and find the solution to my problem.
> > I have a main report with a subreport. The first row renders the sub
> > report
> > just fine but for the rest of the rows it gives the error: Error:
> > Subreport
> > could not be shown.
> >
> > The parameters I'm passing are valid, and I am also casting them to the
> > data
> > type the sub report is expecting. Is this some sort of SSRS bug? There
> > doesn't seem to be a valid solution to this problem. Any help would be
> > much
> > appreciated.
> >
> > Thanks,
> > dev88
>
>|||"dev88" wrote:
> Thanks for the advice Mark. This is quite a strange problem. My parent
> report and my subreport both connect to a shared datasource which is an
> analysis services database, therefore I didn't need to use a Report Model.
> I did however try to change the datasource of my parent report to get the
> data directly from a sql database (so the parent report and sub report
> weren't sharing a connection) and now half the subreports are displayed
> properly while the other half still display the same error "Error: Subreport
> could not be shown". I'm half way there, anyone have any other suggestions?
> Thanks.
> "theMark" wrote:
> > Yeah, we had the same problem here. In our case, it looks like it has to do
> > with basing the the Main report and Sub-report on the same Report Model. I
> > don't know all the details, but when it tries to add the second instance of
> > the same sup-report, it finds it already has an index entry (where? I'm not
> > sure) with that id, and can't / won't show it again. Hence, the "Subreport
> > could not be shown".
> >
> > Our workaround : rebuild the Sub-Reports without using the Report model; go
> > directly to the database, and use SQL to bring back the data with same field
> > names. Oh, and the field names are case-sensitive, so watch out.
> >
> > I hear there may be fix for this in SP2, when it arrives. (However, I also
> > heard Elvis playing in the room next door, so my hearing may be bad! :) )
> > Also, your problem may be something different. But, this worked for us.
> >
> > Mark
> >
> >
> > "dev88" <dev88@.discussions.microsoft.com> wrote in message
> > news:D1FD303C-D618-4F37-B850-CEB7B84E0D81@.microsoft.com...
> > > Hi,
> > >
> > > I've been searching everywhere to try and find the solution to my problem.
> > > I have a main report with a subreport. The first row renders the sub
> > > report
> > > just fine but for the rest of the rows it gives the error: Error:
> > > Subreport
> > > could not be shown.
> > >
> > > The parameters I'm passing are valid, and I am also casting them to the
> > > data
> > > type the sub report is expecting. Is this some sort of SSRS bug? There
> > > doesn't seem to be a valid solution to this problem. Any help would be
> > > much
> > > appreciated.
> > >
> > > Thanks,
> > > dev88
> >
> >
> >|||I have a similar symptom. I have a main report with several subreports. The
truly odd thing is that this report has run correctly for many months.
Recently we have had this symptom showing up after about 5 or 6 pages. I
cannot see an errors showing up when I use the profiler. We are getting our
enterprise IT group to install some other diagnostic tools to see if there is
something else going on. I am beginning to suspect some system problem at a
lower level than Reporting services. I would very much like to hear from
anyone else who has this problem.
Stuart
"dev88" wrote:
> Thanks for the advice Mark. This is quite a strange problem. My parent
> report and my subreport both connect to a shared datasource which is an
> analysis services database, therefore I didn't need to use a Report Model.
> I did however try to change the datasource of my parent report to get the
> data directly from a sql database (so the parent report and sub report
> weren't sharing a connection) and now half the subreports are displayed
> properly while the other half still display the same error "Error: Subreport
> could not be shown". I'm half way there, anyone have any other suggestions?
> Thanks.
> "theMark" wrote:
> > Yeah, we had the same problem here. In our case, it looks like it has to do
> > with basing the the Main report and Sub-report on the same Report Model. I
> > don't know all the details, but when it tries to add the second instance of
> > the same sup-report, it finds it already has an index entry (where? I'm not
> > sure) with that id, and can't / won't show it again. Hence, the "Subreport
> > could not be shown".
> >
> > Our workaround : rebuild the Sub-Reports without using the Report model; go
> > directly to the database, and use SQL to bring back the data with same field
> > names. Oh, and the field names are case-sensitive, so watch out.
> >
> > I hear there may be fix for this in SP2, when it arrives. (However, I also
> > heard Elvis playing in the room next door, so my hearing may be bad! :) )
> > Also, your problem may be something different. But, this worked for us.
> >
> > Mark
> >
> >
> > "dev88" <dev88@.discussions.microsoft.com> wrote in message
> > news:D1FD303C-D618-4F37-B850-CEB7B84E0D81@.microsoft.com...
> > > Hi,
> > >
> > > I've been searching everywhere to try and find the solution to my problem.
> > > I have a main report with a subreport. The first row renders the sub
> > > report
> > > just fine but for the rest of the rows it gives the error: Error:
> > > Subreport
> > > could not be shown.
> > >
> > > The parameters I'm passing are valid, and I am also casting them to the
> > > data
> > > type the sub report is expecting. Is this some sort of SSRS bug? There
> > > doesn't seem to be a valid solution to this problem. Any help would be
> > > much
> > > appreciated.
> > >
> > > Thanks,
> > > dev88
> >
> >
> >

No comments:

Post a Comment