Simone B
asked on
Can't reach subreport through url sent by email
I have an SSRS report, containing a subreport, that's posted and works properly in Report Manager. When I send the report url via email, the main report opens correctly, but the subreport throws an error when I attempt to drill into it. Below is the error. The error log does not have any further details.
Thanks in advance for any help you can provide.
Reporting Services Error
__________________________ __________ ____
• An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
o The URL-encoded form data is not valid.
¿ Operation is not valid due to the current state of the object.
__________________________ __________ ____
SQL Server Reporting Services
Thanks in advance for any help you can provide.
Reporting Services Error
__________________________
• An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
o The URL-encoded form data is not valid.
¿ Operation is not valid due to the current state of the object.
__________________________
SQL Server Reporting Services
ASKER
Thank you. I found the error in the log, and it's not due to insufficient privileges. My group all has admin access to the server, in any case. This is the error in the log file (same as the one originally posted):
Info: Microsoft.ReportingService s.Diagnost ics.Utilit ies.Intern alCatalogE xception: An internal error occurred on the report server. See the error log for more details. ---> System.Web.HttpException: The URL-encoded form data is not valid. ---> System.InvalidOperationExc eption: Operation is not valid due to the current state of the object.
Info: Microsoft.ReportingService
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you. We actually tried that earlier today, but it hasn't made any difference. This is really stumping our team.
One \thing you might try is to run report export as a pdf then email the report.
ASKER
Thanks for your suggestion. But this is an audit report sent as a finalstep in SQL Agent jobs. It wouldn't work very well as a subscription. The report is designed so that we can drill down to problem areas.
ASKER
It turns out that we had to move the location of the MaxCollectionKeys line in the config file, although your response pointed us in the right direction. Thank you.
C:\Program Files\Microsoft SQL Server\<<Your SQL Instance>>\Reporting Services\LogFiles