Report Error, Help!

Hi
I have beening trying to build a report with 2 parameters. When I run it
under VS.net, it all went well, but after I deploy it to the server, I got
the message as following: Reporting Services Error--The path of the item ''
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
what went wrong, please help. TIAYou sure have to post your URL to help you.
Jens Suessmeyer.
"wd1153" <wd1153@.discussions.microsoft.com> schrieb im Newsbeitrag
news:5138A906-7AA9-4D7A-A1B5-E3C9756BE7E1@.microsoft.com...
> Hi
> I have beening trying to build a report with 2 parameters. When I run it
> under VS.net, it all went well, but after I deploy it to the server, I got
> the message as following: Reporting Services Error--The path of the item
> ''
> 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
> what went wrong, please help. TIA
>
>|||Sorry, the URL as following:
http://localhost/reportserver?%2fRev_Stats%2fRev_Stats&rs:Command=Render
"Jens Sü�meyer" wrote:
> You sure have to post your URL to help you.
> Jens Suessmeyer.
>
> "wd1153" <wd1153@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:5138A906-7AA9-4D7A-A1B5-E3C9756BE7E1@.microsoft.com...
> > Hi
> >
> > I have beening trying to build a report with 2 parameters. When I run it
> > under VS.net, it all went well, but after I deploy it to the server, I got
> > the message as following: Reporting Services Error--The path of the item
> > ''
> > 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
> > what went wrong, please help. TIA
> >
> >
> >
>
>

report does not accept null values for its parameters

Hi all
Im using a stored procedure with in params as datasource to a report.
These params are initialized to null by default in the procedure.
When executing this datasource in the report designer's data tab
every thing works fine - i can live these parameters with nulls (or set
other values) and the procedures return appropriate results.
Then in the report parameters tab i allow these params to get null values,
with no default value.
But when executing the report in the 'preview' mode of visual studio i must
enter values for all params or else the report is not displayed at all (not
even with empty result set..).
No error massage is displayed - just the default blank background..
Thanks for your attention
ReaThe report will not execute unless you provide Default values in the Report
Parameters dialog. Without setting a default value on each and every
parameter, RS has no way of knowing what to use. It is unaware that your SP
has default values assigned.
hth
fmi see www.sqlreportingservices.net
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:%23nq$JF3YEHA.2500@.TK2MSFTNGP09.phx.gbl...
> Hi all
> Im using a stored procedure with in params as datasource to a report.
> These params are initialized to null by default in the procedure.
> When executing this datasource in the report designer's data tab
> every thing works fine - i can live these parameters with nulls (or set
> other values) and the procedures return appropriate results.
> Then in the report parameters tab i allow these params to get null values,
> with no default value.
> But when executing the report in the 'preview' mode of visual studio i
must
> enter values for all params or else the report is not displayed at all
(not
> even with empty result set..).
> No error massage is displayed - just the default blank background..
> Thanks for your attention
> Rea
>|||ok then how do i set null values as default values for report's parameters'
i tried : null , =null, =System.DBnull - all were rejected by compilation.
Thanks again
Rea
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:uAKFBp3YEHA.1764@.TK2MSFTNGP10.phx.gbl...
> The report will not execute unless you provide Default values in the
Report
> Parameters dialog. Without setting a default value on each and every
> parameter, RS has no way of knowing what to use. It is unaware that your
SP
> has default values assigned.
> hth
> fmi see www.sqlreportingservices.net
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:%23nq$JF3YEHA.2500@.TK2MSFTNGP09.phx.gbl...
> > Hi all
> > Im using a stored procedure with in params as datasource to a report.
> > These params are initialized to null by default in the procedure.
> > When executing this datasource in the report designer's data tab
> > every thing works fine - i can live these parameters with nulls (or set
> > other values) and the procedures return appropriate results.
> > Then in the report parameters tab i allow these params to get null
values,
> > with no default value.
> > But when executing the report in the 'preview' mode of visual studio i
> must
> > enter values for all params or else the report is not displayed at all
> (not
> > even with empty result set..).
> > No error massage is displayed - just the default blank background..
> > Thanks for your attention
> > Rea
> >
> >
>|||=Nothing
(according to Peter)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Rea Peleg" <rea_p@.afek.co.il> wrote in message
news:uip9OnAZEHA.1356@.TK2MSFTNGP09.phx.gbl...
> ok then how do i set null values as default values for report's
parameters'
> i tried : null , =null, =System.DBnull - all were rejected by compilation.
> Thanks again
> Rea
> "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> news:uAKFBp3YEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > The report will not execute unless you provide Default values in the
> Report
> > Parameters dialog. Without setting a default value on each and every
> > parameter, RS has no way of knowing what to use. It is unaware that your
> SP
> > has default values assigned.
> >
> > hth
> > fmi see www.sqlreportingservices.net
> >
> >
> > --
> > ____________________________________
> > William (Bill) Vaughn
> > Author, Mentor, Consultant
> > Microsoft MVP
> > www.betav.com
> > Please reply only to the newsgroup so that others can benefit.
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > __________________________________
> >
> > "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> > news:%23nq$JF3YEHA.2500@.TK2MSFTNGP09.phx.gbl...
> > > Hi all
> > > Im using a stored procedure with in params as datasource to a report.
> > > These params are initialized to null by default in the procedure.
> > > When executing this datasource in the report designer's data tab
> > > every thing works fine - i can live these parameters with nulls (or
set
> > > other values) and the procedures return appropriate results.
> > > Then in the report parameters tab i allow these params to get null
> values,
> > > with no default value.
> > > But when executing the report in the 'preview' mode of visual studio i
> > must
> > > enter values for all params or else the report is not displayed at all
> > (not
> > > even with empty result set..).
> > > No error massage is displayed - just the default blank background..
> > > Thanks for your attention
> > > Rea
> > >
> > >
> >
> >
>|||Thanks i found a way:
Null values should be added to the parameter's result set/data source.
Then you allow null values for it and set for default value - none.
I hope =Nothing does not work because i spent some 2 hours figuring in
out...:))
Rea
"William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
news:ew$ZIAJZEHA.2016@.TK2MSFTNGP09.phx.gbl...
> =Nothing
> (according to Peter)
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
> "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> news:uip9OnAZEHA.1356@.TK2MSFTNGP09.phx.gbl...
> > ok then how do i set null values as default values for report's
> parameters'
> > i tried : null , =null, =System.DBnull - all were rejected by
compilation.
> > Thanks again
> > Rea
> >
> > "William (Bill) Vaughn" <billvaRemoveThis@.nwlink.com> wrote in message
> > news:uAKFBp3YEHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > The report will not execute unless you provide Default values in the
> > Report
> > > Parameters dialog. Without setting a default value on each and every
> > > parameter, RS has no way of knowing what to use. It is unaware that
your
> > SP
> > > has default values assigned.
> > >
> > > hth
> > > fmi see www.sqlreportingservices.net
> > >
> > >
> > > --
> > > ____________________________________
> > > William (Bill) Vaughn
> > > Author, Mentor, Consultant
> > > Microsoft MVP
> > > www.betav.com
> > > Please reply only to the newsgroup so that others can benefit.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > __________________________________
> > >
> > > "Rea Peleg" <rea_p@.afek.co.il> wrote in message
> > > news:%23nq$JF3YEHA.2500@.TK2MSFTNGP09.phx.gbl...
> > > > Hi all
> > > > Im using a stored procedure with in params as datasource to a
report.
> > > > These params are initialized to null by default in the procedure.
> > > > When executing this datasource in the report designer's data tab
> > > > every thing works fine - i can live these parameters with nulls (or
> set
> > > > other values) and the procedures return appropriate results.
> > > > Then in the report parameters tab i allow these params to get null
> > values,
> > > > with no default value.
> > > > But when executing the report in the 'preview' mode of visual studio
i
> > > must
> > > > enter values for all params or else the report is not displayed at
all
> > > (not
> > > > even with empty result set..).
> > > > No error massage is displayed - just the default blank background..
> > > > Thanks for your attention
> > > > Rea
> > > >
> > > >
> > >
> > >
> >
> >
>

Report Designer: preview goes into infinite loop

Hello,
Situation:
- a report with cascading parameters [A], [B], [C]
- first parameter [A] loaded via non-queried values
- second parameter [B] loaded via stored procedure, taking [A] and a
constant as input (via dataset dsB)
- third parameter [C] loaded via the same stored procedure, taking [A] and
[B] as input (via dataset dsC)
When I preview this report:
- initial view ok
- modify [A] -> [B] changes accordingly
- modify [B] -> the designer starts flickering and goes into a never ending
loop.
The deployed report works just fine and as expected.
Bug ? Any work arounds ?
Thanks for any input!
TomSounds like a bug. There is another bug I have found with the preview tab
and cascading parameters. It only cascades once. I.e. if you go back a
second time and change A it does not change B. Again, deploy works fine. I
have access to the the internal bug reporting tool and when I report the
previous but I'll do this one too. I am not aware of any workaround. At
least it works in deployed mode.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> Hello,
> Situation:
> - a report with cascading parameters [A], [B], [C]
> - first parameter [A] loaded via non-queried values
> - second parameter [B] loaded via stored procedure, taking [A] and a
> constant as input (via dataset dsB)
> - third parameter [C] loaded via the same stored procedure, taking [A] and
> [B] as input (via dataset dsC)
> When I preview this report:
> - initial view ok
> - modify [A] -> [B] changes accordingly
> - modify [B] -> the designer starts flickering and goes into a never
ending
> loop.
> The deployed report works just fine and as expected.
> Bug ? Any work arounds ?
> Thanks for any input!
> Tom|||Thanks for reporting it.
It is annoying as the first parameter in our reports is the choice of
language. Depending on the selection the contents of the other dropdown
boxes is changed.
So we have cascading parameters in every report.
But we can use the deployed reports luckily.
Regards,
Tom
"Bruce L-C [MVP]" wrote:
> Sounds like a bug. There is another bug I have found with the preview tab
> and cascading parameters. It only cascades once. I.e. if you go back a
> second time and change A it does not change B. Again, deploy works fine. I
> have access to the the internal bug reporting tool and when I report the
> previous but I'll do this one too. I am not aware of any workaround. At
> least it works in deployed mode.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> >
> > Hello,
> >
> > Situation:
> > - a report with cascading parameters [A], [B], [C]
> > - first parameter [A] loaded via non-queried values
> > - second parameter [B] loaded via stored procedure, taking [A] and a
> > constant as input (via dataset dsB)
> > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > [B] as input (via dataset dsC)
> >
> > When I preview this report:
> > - initial view ok
> > - modify [A] -> [B] changes accordingly
> > - modify [B] -> the designer starts flickering and goes into a never
> ending
> > loop.
> >
> > The deployed report works just fine and as expected.
> >
> > Bug ? Any work arounds ?
> >
> > Thanks for any input!
> > Tom
>
>|||I am not using cascading parameters but I have experieced a similiar problems
with the Report Designer preview (loops) and I sometimes get a Processing
Error 'Specified Cast in not Valid' , If I remove the Page Header OR Footer I
do not get the error, OR if there is labels only (no ReportItems! or Globals!
in the header/footer) it works.
There are no problems when the report is deployed.
"Tom VdP" wrote:
> Thanks for reporting it.
> It is annoying as the first parameter in our reports is the choice of
> language. Depending on the selection the contents of the other dropdown
> boxes is changed.
> So we have cascading parameters in every report.
> But we can use the deployed reports luckily.
> Regards,
> Tom
>
> "Bruce L-C [MVP]" wrote:
> > Sounds like a bug. There is another bug I have found with the preview tab
> > and cascading parameters. It only cascades once. I.e. if you go back a
> > second time and change A it does not change B. Again, deploy works fine. I
> > have access to the the internal bug reporting tool and when I report the
> > previous but I'll do this one too. I am not aware of any workaround. At
> > least it works in deployed mode.
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> > "Tom VdP" <unick@.hot_mail_.c-o-m> wrote in message
> > news:1FBF14D5-28E3-4B76-93BF-47F292BC33FE@.microsoft.com...
> > >
> > > Hello,
> > >
> > > Situation:
> > > - a report with cascading parameters [A], [B], [C]
> > > - first parameter [A] loaded via non-queried values
> > > - second parameter [B] loaded via stored procedure, taking [A] and a
> > > constant as input (via dataset dsB)
> > > - third parameter [C] loaded via the same stored procedure, taking [A] and
> > > [B] as input (via dataset dsC)
> > >
> > > When I preview this report:
> > > - initial view ok
> > > - modify [A] -> [B] changes accordingly
> > > - modify [B] -> the designer starts flickering and goes into a never
> > ending
> > > loop.
> > >
> > > The deployed report works just fine and as expected.
> > >
> > > Bug ? Any work arounds ?
> > >
> > > Thanks for any input!
> > > Tom
> >
> >
> >

Report deployment with RS2k, SP1

Hello,
I have a problem with report's deployment (SQL 2k, RS SP1). All my reports
have only hidden parameters (parameters with a prompt blank).
When I deploy from VS. NET 2003 to an empty folder on my RS server, the
prompts reappear and the checkbox "prompt user" is unchecked. That means
read only parameters and my reports return an error. The only way to correct
that is to manualy change the checkbox.
After the first deployment, each time I deploy the same reports (I replace
the existing), the checks stay but the prompt reappear. I have 15 reports
with 5-10 parameters on 3 environments (dev, qa, prod) and after each
deployment, I have to manualy remove the prompt..... I get crazy....
If someone have some experience with that problem or a workaround, don't
hesitate...
Thanks in adavance
LaurentHi,
have you tried rs.CreateReport with overwrite properties so that you can
overwrite all the parameter and report properties..
when i do upgrade i use this property to overwrite report in the script..
Bava
"Laurent" wrote:
> Hello,
> I have a problem with report's deployment (SQL 2k, RS SP1). All my reports
> have only hidden parameters (parameters with a prompt blank).
> When I deploy from VS. NET 2003 to an empty folder on my RS server, the
> prompts reappear and the checkbox "prompt user" is unchecked. That means
> read only parameters and my reports return an error. The only way to correct
> that is to manualy change the checkbox.
> After the first deployment, each time I deploy the same reports (I replace
> the existing), the checks stay but the prompt reappear. I have 15 reports
> with 5-10 parameters on 3 environments (dev, qa, prod) and after each
> deployment, I have to manualy remove the prompt..... I get crazy....
> If someone have some experience with that problem or a workaround, don't
> hesitate...
> Thanks in adavance
> Laurent
>
>sql

Report deployement

Hi,

I have a heavy report:

- 18 datasets (some with filters)

- 15 parameters

- about 10 tables (some with groups)

- lots of TextBox static or calculated (50 at least)

- and a little report footer

Anyway…

I’m using Visual Studio 2005 to deploy my report on a server. Recently, my deployments became very long and now, Visual Studio throw Timeouts when I deploy it. I walk around this problem with the report management site on the server But deploying my report through it takes about 8 or 10 minutes…quite long !

Here are my questions :

- What are report elements that causes such time span ?

- How lighten the deployment ?

- How configure the deployement timeout in visual studio ?

Thanks

Which exact error message are you experiencing ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

The report services on the server has been installed with the french version

so the error message is in french : "Le dlai d'attente de l'opration a expir"

in english it looks like : "The wait delay of the operation has expire"

thanks

Report DateTime Parameters in UK date format

I have a report that I've developed that accepts several datetime parameters.
In the Report properties, I've set the report Language to English (United
Kingdom).
I am calling my report via the Web Service from an ASP.Net application. The
ASP.Net application Culture and UICulture are set for en-GB.
What is happening is that when a date is passed to one of the report
parameters (gEndDate) as "14/12/2004" (December 14), I get the following
error:
The value provided for the report parameter 'gEndDate' is not valid for its
typeI should also point out that my Visual Studio .Net 2003 environment is in
en-US and my computer is in the United States English setting.
The development environment I am testing (where I got the error) is a
Virtual PC environment set up as English UK in the Control Panel.
"AdamB" wrote:
> I have a report that I've developed that accepts several datetime parameters.
> In the Report properties, I've set the report Language to English (United
> Kingdom).
> I am calling my report via the Web Service from an ASP.Net application. The
> ASP.Net application Culture and UICulture are set for en-GB.
> What is happening is that when a date is passed to one of the report
> parameters (gEndDate) as "14/12/2004" (December 14), I get the following
> error:
> The value provided for the report parameter 'gEndDate' is not valid for its
> type
>

report by multiple parameter with OR relationship

I am trying to create a report with three parameters (date, license number and application number). I want report by License Number or Application number in the date that I put in. I trying following in Record Selection:
1.
{Command.LICENSE_NO} = {?License Number} or
{Command.LICENSE_ID} = {?Application Number}

2.
if isnull({?License Number}) = false then
{Command.LICENSE_NO} = {?License Number};
if isnull({?Application Number})=false then
{Command.LICENSE_ID}={?Application Number};

** license_id is the application number(number). license number(string)

but both of them do not work. somehow I can not leave Application number empty.

Please Help!!!As Application Number is a number, Crystal wants you to specify one.
If you default it to 0 you could have a selection formula like

({?Application Number} = 0 and {Command.LICENSE_NO} = {?License Number})
or
({?Application Number} <> 0 and {Command.LICENSE_ID} = {?Application Number})

which means that if you supply a non-zero application number it will be used in preference to any licence id you provide.|||As Application Number is a number, Crystal wants you to specify one.
If you default it to 0 you could have a selection formula like

({?Application Number} = 0 and {Command.LICENSE_NO} = {?License Number})
or
({?Application Number} <> 0 and {Command.LICENSE_ID} = {?Application Number})

which means that if you supply a non-zero application number it will be used in preference to any licence id you provide.

I have tried using 0 as default, but for some reason. I still can not leave application number empty. I used exactly same as your code

({?Application Number} = 0 and {Command.LICENSE_NO} = {?License Number})
or
({?Application Number} <> 0 and {Command.LICENSE_ID} = {?Application Number})

but search will not start if I leave application parameter empty.

any thought?

Thanks for your help|||As Application Number is a number, Crystal wants you to specify one.
If you default it to 0 you could have a selection formula like

({?Application Number} = 0 and {Command.LICENSE_NO} = {?License Number})
or
({?Application Number} <> 0 and {Command.LICENSE_ID} = {?Application Number})

which means that if you supply a non-zero application number it will be used in preference to any licence id you provide.

Got it working with your code!!!

Thanks your so much!!

Report Builder permissions

I would like to know how can I show parts of tables in report builder,

according to parameters that will be sent from the application.

Is it possible?

help...

can I send parameters to report builder, in order to show specific report model for each user?

Report Builder - parameters

Is there a way to pass a parameter to the report builder?

We are not using impersonation to call the report builder so we don't know who the actual user is. We want to be able to pass the UserID to the report builder so we know who the actual user is supposed to be.

Thanks.

Sorry, currently the only parameters that can be passed to Report Builder are a server path, startup model, startup perspective or startup report.

Report Action + multi parameters

Hi

Using Report Action, Can accept multi parameters from Excel Pivot Table?

Exist some way of doing this.

Please help me

thanks for your commentaries

carlos

Your probably better off using an url action instead of report action(which behind the covers is basically the same). Because if you want to specify more than one value you must specify that parameter over and over again at design time(i think), instead of concatenating a string. This because a url with a multivalue parameter looks like this:

http://localhost/ReportServer?%2fCatalog%2fMultiReport&rs:Command=Render&ParameterTest=1&ParameterTest=2

Look at these two links, i think you will get on how to do it in a URL action:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1047470&SiteID=1
http://msdn2.microsoft.com/en-us/library/ms153586.aspx

|||

Hi, thank for the help.

But, When I select several cells, since I do to pass them as parameters to the URL?

Is it possible?

|||

Actions are executed for specific cells based on the co-ordinates of that cell, so I would not expect the Excel user interface to allow you to launch an action when multile cells are selected.

|||

Ok, thank a lot for you help