HELP!!-Jump to URL

I input for "Jump to URL".
But I don't want to open URL on same page.
Is it possible to open new window for that URL page after click one which
have a "Jump to URL".Yes it is, something like this:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?%2fJBOSC%2fJLRRS%2fworkorder%2fwondetail&WON=" & Fields!COL2.Value &
"','_blank'))"
"Ken" wrote:
> I input for "Jump to URL".
> But I don't want to open URL on same page.
> Is it possible to open new window for that URL page after click one which
> have a "Jump to URL".
>
>

HELP!!!! - Report parameter "Read Only"

I'm stuck with a report not being able to use the URL parameter.

I get the error:

The report parameter is read-only and cannot be modified.

I do have a prompting text for the report, and I've checked the XML and there are <PROMPT></PROMPT> tags!

Most likely, you've modified the parameter definition in Report Manager to make it read-only. If you are using SQL 2005, this can happen when you mark it in the designer as 'Internal'.|||

I just dealt with a similar problem (working in RS2000) and no matter what I tried, I couldn't get the error to go away. I tried removing the parameter and re-adding it manually. I tried removing the procedure that required the parameter, re-deploying, and then adding the procedure (and thus the parameter) back in. That still didn't work. This is what I finally did:

1) Removed the parameter from the procedure (commented out the param and any references to it in the sp)

2) Refresh the dataset (to remove the parameter). Ensured the parameter was removed from the report.

3) Re-deployed the report (without the offending parameter). It worked.

4) Went back to the sp and uncommented out the parameter and all references to it

5) Refreshed the dataset (to add the parameter back into the report).

6) Re-deployed. It worked and now accepted the parameter.

I can only surmise that RS had some former reference to the parameter that indicated it was read only, and any re-deployment that I did didn't overwrite that reference. Only by completely removing the parameter, re-deploying, and adding the parameter back in did this issue go away.

I hope this helps someone out there.

|||I got the same problem with VS2005. One time paremeter was checked as "Not Prompt user". After that I changed, deleted and recreated parameter, redeploys report to report server but recived the same error "Report parameter Read Only". Its helped a manualy chnage property of report parameter direct on report server using Report Manager( check on "Propmpt User" property of required parameter). Redeploy of report from VS don't cause changes of report properties on server.

HELP!!!! - Report parameter "Read Only"

I'm stuck with a report not being able to use the URL parameter.

I get the error:

The report parameter is read-only and cannot be modified.

I do have a prompting text for the report, and I've checked the XML and there are <PROMPT></PROMPT> tags!

Most likely, you've modified the parameter definition in Report Manager to make it read-only. If you are using SQL 2005, this can happen when you mark it in the designer as 'Internal'.|||

I just dealt with a similar problem (working in RS2000) and no matter what I tried, I couldn't get the error to go away. I tried removing the parameter and re-adding it manually. I tried removing the procedure that required the parameter, re-deploying, and then adding the procedure (and thus the parameter) back in. That still didn't work. This is what I finally did:

1) Removed the parameter from the procedure (commented out the param and any references to it in the sp)

2) Refresh the dataset (to remove the parameter). Ensured the parameter was removed from the report.

3) Re-deployed the report (without the offending parameter). It worked.

4) Went back to the sp and uncommented out the parameter and all references to it

5) Refreshed the dataset (to add the parameter back into the report).

6) Re-deployed. It worked and now accepted the parameter.

I can only surmise that RS had some former reference to the parameter that indicated it was read only, and any re-deployment that I did didn't overwrite that reference. Only by completely removing the parameter, re-deploying, and adding the parameter back in did this issue go away.

I hope this helps someone out there.

|||I got the same problem with VS2005. One time paremeter was checked as "Not Prompt user". After that I changed, deleted and recreated parameter, redeploys report to report server but recived the same error "Report parameter Read Only". Its helped a manualy chnage property of report parameter direct on report server using Report Manager( check on "Propmpt User" property of required parameter). Redeploy of report from VS don't cause changes of report properties on server.

HELP!!!! - Report parameter "Read Only"

I'm stuck with a report not being able to use the URL parameter.

I get the error:

The report parameter is read-only and cannot be modified.

I do have a prompting text for the report, and I've checked the XML and there are <PROMPT></PROMPT> tags!

Most likely, you've modified the parameter definition in Report Manager to make it read-only. If you are using SQL 2005, this can happen when you mark it in the designer as 'Internal'.|||

I just dealt with a similar problem (working in RS2000) and no matter what I tried, I couldn't get the error to go away. I tried removing the parameter and re-adding it manually. I tried removing the procedure that required the parameter, re-deploying, and then adding the procedure (and thus the parameter) back in. That still didn't work. This is what I finally did:

1) Removed the parameter from the procedure (commented out the param and any references to it in the sp)

2) Refresh the dataset (to remove the parameter). Ensured the parameter was removed from the report.

3) Re-deployed the report (without the offending parameter). It worked.

4) Went back to the sp and uncommented out the parameter and all references to it

5) Refreshed the dataset (to add the parameter back into the report).

6) Re-deployed. It worked and now accepted the parameter.

I can only surmise that RS had some former reference to the parameter that indicated it was read only, and any re-deployment that I did didn't overwrite that reference. Only by completely removing the parameter, re-deploying, and adding the parameter back in did this issue go away.

I hope this helps someone out there.

|||I got the same problem with VS2005. One time paremeter was checked as "Not Prompt user". After that I changed, deleted and recreated parameter, redeploys report to report server but recived the same error "Report parameter Read Only". Its helped a manualy chnage property of report parameter direct on report server using Report Manager( check on "Propmpt User" property of required parameter). Redeploy of report from VS don't cause changes of report properties on server.

HELP!!!! - Report parameter "Read Only"

I'm stuck with a report not being able to use the URL parameter.

I get the error:

The report parameter is read-only and cannot be modified.

I do have a prompting text for the report, and I've checked the XML and there are <PROMPT></PROMPT> tags!

Most likely, you've modified the parameter definition in Report Manager to make it read-only. If you are using SQL 2005, this can happen when you mark it in the designer as 'Internal'.|||

I just dealt with a similar problem (working in RS2000) and no matter what I tried, I couldn't get the error to go away. I tried removing the parameter and re-adding it manually. I tried removing the procedure that required the parameter, re-deploying, and then adding the procedure (and thus the parameter) back in. That still didn't work. This is what I finally did:

1) Removed the parameter from the procedure (commented out the param and any references to it in the sp)

2) Refresh the dataset (to remove the parameter). Ensured the parameter was removed from the report.

3) Re-deployed the report (without the offending parameter). It worked.

4) Went back to the sp and uncommented out the parameter and all references to it

5) Refreshed the dataset (to add the parameter back into the report).

6) Re-deployed. It worked and now accepted the parameter.

I can only surmise that RS had some former reference to the parameter that indicated it was read only, and any re-deployment that I did didn't overwrite that reference. Only by completely removing the parameter, re-deploying, and adding the parameter back in did this issue go away.

I hope this helps someone out there.

|||I got the same problem with VS2005. One time paremeter was checked as "Not Prompt user". After that I changed, deleted and recreated parameter, redeploys report to report server but recived the same error "Report parameter Read Only". Its helped a manualy chnage property of report parameter direct on report server using Report Manager( check on "Propmpt User" property of required parameter). Redeploy of report from VS don't cause changes of report properties on server.

Help!!! launching report builder from url is adding .rdl to name when saving.

Hi,

When I launch a report using the following url, and then make changes to the report and save it, Reportbuilder is creating another report with the same name but also including the .rdl within the name itself.. therfore I now have two reports now displayed within the report manager

http://localhost/reportserver/reportbuilder/reportbuilder.application?/Report1

Can someone please help...

Hi,

this issue was resolved by applying SP2

thanks.

|||

or:

the same rdl has been uploaded directly using Report Manager and Published in Visual Studio at the same time...

Help!!! launching report builder from url is adding .rdl to name when saving.

Hi,

When I launch a report using the following url, and then make changes to the report and save it, Reportbuilder is creating another report with the same name but also including the .rdl within the name itself.. therfore I now have two reports now displayed within the report manager

http://localhost/reportserver/reportbuilder/reportbuilder.application?/Report1

Can someone please help...

Hi,

this issue was resolved by applying SP2

thanks.

|||

or:

the same rdl has been uploaded directly using Report Manager and Published in Visual Studio at the same time...

Help! launching report builder from url is adding .rdl to name when saving.

Hi,
When I launch a report using the following url, and then make changes to the
report and save it, Reportbuilder is creating another report with the same
name but also including the .rdl within the name itself.. therfore I now
have two reports now displayed within the report managerCan you check the file type for rdl in Windows Explorer and see if it is
misconfigured? Also, do your report names contain any non-alphanumeric
characters?
--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
"Rob Dob" <robdob20012002@.yahoo.com> wrote in message
news:OUA8VAbXHHA.4560@.TK2MSFTNGP03.phx.gbl:
> Hi,
> When I launch a report using the following url, and then make changes to the
> report and save it, Reportbuilder is creating another report with the same
> name but also including the .rdl within the name itself.. therfore I now
> have two reports now displayed within the report manager|||> Can you check the file type for rdl in Windows Explorer and see if it is
> misconfigured? Also, do your report names contain any non-alphanumeric
> characters?
>
Thank you, SP2 seemed to resolve this issue

HELP! - URL Access - Localhost vs. ServerName

We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. We have tried two ways--building the URL string and popping up a new browser with the Reporting Services URL access string and simply using an anchor tag and setting its URL parameter to the Reporting Services URL access string. Both options don't work--well, one works for the local server and the other works for client computers (not the server), but neither work for both.

Basically, we're having trouble using localhost vs. servername in our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS are running, but not from other computers (because of the "localhost").
// Build the URL for the report
url = "http://localhost/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";
// Build the javascript to display the message
string sScript = "<script language=\"javascript\" type=\"text/javascript\">window.open(\"" + url + "\", \"ReportsDateSelectionGenerateReport\", \"height=675,width=975,left=0,top=0,copyHistory=no,directories=no,location=no,menubar=no,resizable=no,scrollbars=no,status=no,toolbar=no\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "LinkButtonGenerateReport_Click", sScript);

<a id="runreport" runat="server" target="_blank" style="font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef = "http://localhost/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";

The examples below use the servername for URL access.
These work fine from other computers (because of the server name), but I get the Connect to <servername> popup asking for User name and Password when I run from the server which Reporting Services and IIS are running.
// Build the URL for the report
url = "http://" + <servername> + "/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";
// Build the javascript to display the message
string sScript = "<script language=\"javascript\" type=\"text/javascript\">window.open(\"" + url + "\", \"ReportsDateSelectionGenerateReport\", \"height=675,width=975,left=0,top=0,copyHistory=no,directories=no,location=no,menubar=no,resizable=no,scrollbars=no,status=no,toolbar=no\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "LinkButtonGenerateReport_Click", sScript);

<a id="runreport" runat="server" target="_blank" style="font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef = "http://" + <servername> + "/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";

I guess the main issue is using the servername in the URL access string pops up the connect to server dialog wanting a user name and password, even though we're trying to access the report on the server running Reporting Services and IIS. We're using Windows Authentication and impersonation (in our Web.config file), and we're logged into the server as local Administrator. Therefore, we should have no permissions issues.

How can we use the servername in URL access for both the server and client workstation to generate and display reports?

Thanks in advance.

That is very strange. You should be able to subsitute the server name for localhost on the server. Do you get this same behavior when you try this form IE?

How do you get <servername>? Is it possibly getting the wrong value when on the local machine?

|||

Well, I'm always using IE. We don't support other browsers (our ASP.NET 2.0 (C#) application is an intranet application and end-users are required to use IE).

And, yes, we get the same behavior if we copy and paste the entire URL string into the browser's Address bar. It's the same thing as if we were running it through our app's code.

It seems kind of wierd to us too. It seems that if you're working on the server, using the server name should work fine (just like using "localhost").

By the way, we're working on a Win 2003 server with SP1 and using SQL Server 2005 Reporting Services. I read somewhere that the security settings in Win 2003 might be causing such an issue.

As for the servername, we're getting it using a .NET method (I can't remember right now). But, we've definitely tested this and are getting the correct server name from both the server and workstation.

So, we're stumped. Any ideas?

Thanks!

|||

Is there any other .NET Framework class with a property or method that would tell whether the request is coming from a different computer or if the request is coming from the server itself?

Then I could say:

if (coming from workstation computer--not the server == true)
{
// use http://servername/ReportServer...
}
else if (coming from a browser on the server == true)
{
// use http://localhost/ReportServer...
}

Any thoughts?

|||

You could always check the request IP address, but that would be masking the issue rather then fixing the cause.

Have you tried to repro this via your own web app? My guess this is more of an IIS configuration issue then an RS issue. I will have one of our other devs look over this thread and see if he has any other suggestions.

HELP! - URL Access - Localhost vs. ServerName

We have a confusing problem and need some guidance.

We are trying to use URL access to generate and display a report. We have tried two ways--building the URL string and popping up a new browser with the Reporting Services URL access string and simply using an anchor tag and setting its URL parameter to the Reporting Services URL access string. Both options don't work--well, one works for the local server and the other works for client computers (not the server), but neither work for both.

Basically, we're having trouble using localhost vs. servername in our URL access string.

The examples below use localhost.
These work fine from the server which Reporting Services and IIS are running, but not from other computers (because of the "localhost").
// Build the URL for the report
url = "http://localhost/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";
// Build the javascript to display the message
string sScript = "<script language=\"javascript\" type=\"text/javascript\">window.open(\"" + url + "\", \"ReportsDateSelectionGenerateReport\", \"height=675,width=975,left=0,top=0,copyHistory=no,directories=no,location=no,menubar=no,resizable=no,scrollbars=no,status=no,toolbar=no\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "LinkButtonGenerateReport_Click", sScript);

<a id="runreport" runat="server" target="_blank" style="font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef = "http://localhost/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";

The examples below use the servername for URL access.
These work fine from other computers (because of the server name), but I get the Connect to <servername> popup asking for User name and Password when I run from the server which Reporting Services and IIS are running.
// Build the URL for the report
url = "http://" + <servername> + "/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";
// Build the javascript to display the message
string sScript = "<script language=\"javascript\" type=\"text/javascript\">window.open(\"" + url + "\", \"ReportsDateSelectionGenerateReport\", \"height=675,width=975,left=0,top=0,copyHistory=no,directories=no,location=no,menubar=no,resizable=no,scrollbars=no,status=no,toolbar=no\");</script>";
// Execute the script
Page.ClientScript.RegisterClientScriptBlock(this.GetType(), "LinkButtonGenerateReport_Click", sScript);

<a id="runreport" runat="server" target="_blank" style="font-size: large; font-weight: bold;">View Report</a>
this.runreport.HRef = "http://" + <servername> + "/ReportServer?/Reports/MyReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=false&rc:Zoom=Page Width";

I guess the main issue is using the servername in the URL access string pops up the connect to server dialog wanting a user name and password, even though we're trying to access the report on the server running Reporting Services and IIS. We're using Windows Authentication and impersonation (in our Web.config file), and we're logged into the server as local Administrator. Therefore, we should have no permissions issues.

How can we use the servername in URL access for both the server and client workstation to generate and display reports?

Thanks in advance.

That is very strange. You should be able to subsitute the server name for localhost on the server. Do you get this same behavior when you try this form IE?

How do you get <servername>? Is it possibly getting the wrong value when on the local machine?

|||

Well, I'm always using IE. We don't support other browsers (our ASP.NET 2.0 (C#) application is an intranet application and end-users are required to use IE).

And, yes, we get the same behavior if we copy and paste the entire URL string into the browser's Address bar. It's the same thing as if we were running it through our app's code.

It seems kind of wierd to us too. It seems that if you're working on the server, using the server name should work fine (just like using "localhost").

By the way, we're working on a Win 2003 server with SP1 and using SQL Server 2005 Reporting Services. I read somewhere that the security settings in Win 2003 might be causing such an issue.

As for the servername, we're getting it using a .NET method (I can't remember right now). But, we've definitely tested this and are getting the correct server name from both the server and workstation.

So, we're stumped. Any ideas?

Thanks!

|||

Is there any other .NET Framework class with a property or method that would tell whether the request is coming from a different computer or if the request is coming from the server itself?

Then I could say:

if (coming from workstation computer--not the server == true)
{
// use http://servername/ReportServer...
}
else if (coming from a browser on the server == true)
{
// use http://localhost/ReportServer...
}

Any thoughts?

|||

You could always check the request IP address, but that would be masking the issue rather then fixing the cause.

Have you tried to repro this via your own web app? My guess this is more of an IIS configuration issue then an RS issue. I will have one of our other devs look over this thread and see if he has any other suggestions.

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
>> ----