HELP! - Hitting 260 character limit on parameters in URL - how to avoid?

Hi,
Got some reports with a lot of parameters to deal with, a custom web front
end and using the ReportViewer component to render the reports. A typical
URL generated by the app is:
http://localhost/reportserver?/Reports/My%20Report&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false&DateFrom=12/08/2004%2013:59:44&DateTo=12/08/2004%2013:59:44&ClientRefFrom=_All_&ClientRefTo=_All_&SurnameFrom=_All_&SurnameTo=_All_&AreaFrom=_All_&AreaTo=_All_&RegionFrom=_All_&RegionTo=_All_
Problem is i'm getting the following error message displayed:
Reporting Services Error
----
--
a.. The path of the item '/Reports/My Report,' is not valid. The full path
must be less than 260 characters long, must start with slash; other
restrictions apply. Check the documentation for complete set of
restrictions. (rsInvalidItemPath) Get Online Help
----
--
How do I get around this? I understand I need to convert the params in some
way & pass them into the report, cannot find out howto atm.
Any help appreciated
SiDo you have a Folder called Reports in the home directory? Is the 'My
Report' report located in that folder? If you navigate to
//localhost/reportserver you can then click on the folder and the report and
see what the url should look like.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Si" <no@.spam.thanks> wrote in message
news:uhscKCHgEHA.636@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Got some reports with a lot of parameters to deal with, a custom web front
> end and using the ReportViewer component to render the reports. A typical
> URL generated by the app is:
>
http://localhost/reportserver?/Reports/My%20Report&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false&DateFrom=12/08/2004%2013:59:44&DateTo=12/08/2004%2013:59:44&ClientRefFrom=_All_&ClientRefTo=_All_&SurnameFrom=_All_&SurnameTo=_All_&AreaFrom=_All_&AreaTo=_All_&RegionFrom=_All_&RegionTo=_All_
> Problem is i'm getting the following error message displayed:
> Reporting Services Error
> ----
--
> --
> a.. The path of the item '/Reports/My Report,' is not valid. The full
path
> must be less than 260 characters long, must start with slash; other
> restrictions apply. Check the documentation for complete set of
> restrictions. (rsInvalidItemPath) Get Online Help
> ----
--
> --
>
> How do I get around this? I understand I need to convert the params in
some
> way & pass them into the report, cannot find out howto atm.
> Any help appreciated
> Si
>|||Hi Daniel,
Yup the reports work fine if I have less params to play with i.e. if I
just use DateFrom & DateTo it's ok, just when I use all the parameters
in the report I get this message.
Just seems to be the length of the params that causes the problem,
seems like I need to use SetReportParameters to programatically pass
the params into the report but as i'm using the ReportViewer component
(programmatic access), there is no Render method for me to use to pass
these params into!
Si
On Thu, 12 Aug 2004 10:14:55 -0700, "Daniel Reib [MSFT]"
<danreib@.online.microsoft.com> wrote:
>Do you have a Folder called Reports in the home directory? Is the 'My
>Report' report located in that folder? If you navigate to
>//localhost/reportserver you can then click on the folder and the report and
>see what the url should look like.
>--
>-Daniel
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>"Si" <no@.spam.thanks> wrote in message
>news:uhscKCHgEHA.636@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> Got some reports with a lot of parameters to deal with, a custom web front
>> end and using the ReportViewer component to render the reports. A typical
>> URL generated by the app is:
>>
>http://localhost/reportserver?/Reports/My%20Report&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false&DateFrom=12/08/2004%2013:59:44&DateTo=12/08/2004%2013:59:44&ClientRefFrom=_All_&ClientRefTo=_All_&SurnameFrom=_All_&SurnameTo=_All_&AreaFrom=_All_&AreaTo=_All_&RegionFrom=_All_&RegionTo=_All_
>> Problem is i'm getting the following error message displayed:
>> Reporting Services Error
>> ----
>--
>> --
>> a.. The path of the item '/Reports/My Report,' is not valid. The full
>path
>> must be less than 260 characters long, must start with slash; other
>> restrictions apply. Check the documentation for complete set of
>> restrictions. (rsInvalidItemPath) Get Online Help
>> ----|||Found the problem,
You were correct in the URL was suspect but it was with the parameters
rather than the path to the report. I noticed that there was an extra
ampersand at the end of the paramstring and also the date format
included a timestamp. Removing those two entries seems to have fixed
the problem
Thanks for the heads up. At least I now know i'm not going mad!
Si
On Fri, 13 Aug 2004 08:15:04 +0100, Si <no@.spam.thanks> wrote:
>Hi Daniel,
>Yup the reports work fine if I have less params to play with i.e. if I
>just use DateFrom & DateTo it's ok, just when I use all the parameters
>in the report I get this message.
>Just seems to be the length of the params that causes the problem,
>seems like I need to use SetReportParameters to programatically pass
>the params into the report but as i'm using the ReportViewer component
>(programmatic access), there is no Render method for me to use to pass
>these params into!
>Si
>On Thu, 12 Aug 2004 10:14:55 -0700, "Daniel Reib [MSFT]"
><danreib@.online.microsoft.com> wrote:
>>Do you have a Folder called Reports in the home directory? Is the 'My
>>Report' report located in that folder? If you navigate to
>>//localhost/reportserver you can then click on the folder and the report and
>>see what the url should look like.
>>--
>>-Daniel
>>This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>"Si" <no@.spam.thanks> wrote in message
>>news:uhscKCHgEHA.636@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> Got some reports with a lot of parameters to deal with, a custom web front
>> end and using the ReportViewer component to render the reports. A typical
>> URL generated by the app is:
>>
>>http://localhost/reportserver?/Reports/My%20Report&rs:Command=Render&rs:Format=HTML4.0&rc:Parameters=false&DateFrom=12/08/2004%2013:59:44&DateTo=12/08/2004%2013:59:44&ClientRefFrom=_All_&ClientRefTo=_All_&SurnameFrom=_All_&SurnameTo=_All_&AreaFrom=_All_&AreaTo=_All_&RegionFrom=_All_&RegionTo=_All_
>> Problem is i'm getting the following error message displayed:
>> Reporting Services Error
>> ----
>>--
>> --
>> a.. The path of the item '/Reports/My Report,' is not valid. The full
>>path
>> must be less than 260 characters long, must start with slash; other
>> restrictions apply. Check the documentation for complete set of
>> restrictions. (rsInvalidItemPath) Get Online Help
>> ----

HELP! - 8060 limit/select statement

BTW, I'm using SQL Server 2000
Thanks again...
"segis bata" <segisbata@.hotmail.com> wrote in message
news:%23wY31UQdIHA.4744@.TK2MSFTNGP06.phx.gbl...
> Hello all,
> I want to know if it's possible to make a select statement that brings
> only the records with a number of bytes of less than 8060
> so, imagine I have a table with 10 records, and two of those ten records
> have more than 8060 bytes, so, if I do this:
> select a, b, c, d from tableX
> where (len(a)+len(b)+len(c)+len(d) < 8060)
> it will only bring 8 records, not 10
> I tried this approach and it doesn't work, so, my question is, is there a
> way (similar to this) using a select statement to limit the results to
> those records with less than 8060 bytes, so I will never get the error?
> Thanks again for all your help!,
> SB-R
On Feb 22, 8:43Xam, "segis bata" <segisb...@.hotmail.com> wrote:
> BTW, I'm using SQL Server 2000
> Thanks again...
> "segis bata" <segisb...@.hotmail.com> wrote in message
> news:%23wY31UQdIHA.4744@.TK2MSFTNGP06.phx.gbl...
>
>
>
>
>
> - Show quoted text -
Dear Segis,
It is not possible to trim the record size using a where predicate. If
you are using table which has record length more than 8060 bytes then
it should be having varchar column. If so...on the varchar column use
substring function to trim the data above 8060 bytes. Hope this
suggestion helps.
Regards
Balaji
|||The LEN() function returns the number of characters, not the number of
bytes. DATALENGTH() returns the number of bytes. If you have any
NVARCHAR columns, which use two bytes per character, you need to use
DATALENGTH().
Also note that there is overhead to the row that is not captured with
the expression you have. Part of that is two bytes for each varying
length column.
Roy Harvey
Beacon Falls, CT
On Thu, 21 Feb 2008 22:43:49 -0500, "segis bata"
<segisbata@.hotmail.com> wrote:

>BTW, I'm using SQL Server 2000
>Thanks again...
>
>"segis bata" <segisbata@.hotmail.com> wrote in message
>news:%23wY31UQdIHA.4744@.TK2MSFTNGP06.phx.gbl...
>