RS PARAMETERS

I have a report with a Dataset that has a query string:
exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado, @.Agencia,@.Ruta
The report is working, but I want to delete the parameter @.Rute and the
follow error are displaying:
An error has occurred during report processing.
Query execution failed for dataset "resumen"
Must declare the variable @.Usuario.
Plese help me.
--
MauryqTwo things to try. Click on the refresh fields button (to the right of the
...). The other thing is to click on the ... and go to the parameters tab
and make sure all the expected parameters are there.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mauryq" <mauryq@.hotmail.com> wrote in message
news:3F2DFA2A-C1B9-4219-8EB7-7C71487DF6EF@.microsoft.com...
> I have a report with a Dataset that has a query string:
> exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
@.Agencia,@.Ruta
> The report is working, but I want to delete the parameter @.Rute and the
> follow error are displaying:
> An error has occurred during report processing.
> Query execution failed for dataset "resumen"
> Must declare the variable @.Usuario.
> Plese help me.
> --
> Mauryq|||When you create a dataset with a SP with parameters, automatically the
parameters are created at the report, but in this case the parameters can't
be created automatically, and have that created it manually, and when I eject
the preview is like the parameter cant be recognized.
exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
@.Agencia,@.Ruta
"Bruce L-C [MVP]" escribió:
> Two things to try. Click on the refresh fields button (to the right of the
> ...). The other thing is to click on the ... and go to the parameters tab
> and make sure all the expected parameters are there.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mauryq" <mauryq@.hotmail.com> wrote in message
> news:3F2DFA2A-C1B9-4219-8EB7-7C71487DF6EF@.microsoft.com...
> > I have a report with a Dataset that has a query string:
> >
> > exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
> @.Agencia,@.Ruta
> >
> > The report is working, but I want to delete the parameter @.Rute and the
> > follow error are displaying:
> >
> > An error has occurred during report processing.
> > Query execution failed for dataset "resumen"
> > Must declare the variable @.Usuario.
> >
> > Plese help me.
> >
> > --
> > Mauryq
>
>|||I have had mixed results with RS automatically creating the parameters.
Sometimes it messes up. Did you try either of the two things I mentioned?
What happens when you click on the ... and go to the parameters tab?
I have had some stored procedures in SQL Server (I work with both Sybase and
SQL Server) that worked flawlessly with RS creating the Report Parameter.
When you have an @.Paramname in your SQL what happens is that RS looks for a
matching Report Parameter. If it doesn't see it then it assumes that it is a
T-SQL variable. You can have a multi-line T-SQL code with declare
@.SOMEVARIABLE. So what is happening to you is that the wiring between your
query parameters and your report parameters has gotten messed up. It is
important to remember that they are two different things (which gets
confusing because RS is being helpful behind the scenes and creating Report
Parameters).
You need to do two things. You need to check the parameter mapping ( click
on the ... and go to the parameter tab and make sure the query parameters
you expect are all there and are mapped to the appropriate Report
Parameter). You can also from layout view go to the Report Menu, Parameters.
You should see
You say you want to get rid of @.Ruta query parameter. Then you should delete
it from your query calling code, make sure it is deleted from the query
parameter to report parameter mapping and finally that it is not still a
report parameter.
exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado, @.Agencia
Note that you can also be in generic query designer and leave off the exec:
sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado, @.Agencia
I never use the exec. See if that helps at all.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mauryq" <mauryq@.hotmail.com> wrote in message
news:7DF27C6B-F720-46D7-A24F-54641DD96461@.microsoft.com...
> When you create a dataset with a SP with parameters, automatically the
> parameters are created at the report, but in this case the parameters
> can't
> be created automatically, and have that created it manually, and when I
> eject
> the preview is like the parameter cant be recognized.
> exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
> @.Agencia,@.Ruta
>
> "Bruce L-C [MVP]" escribió:
>> Two things to try. Click on the refresh fields button (to the right of
>> the
>> ...). The other thing is to click on the ... and go to the parameters
>> tab
>> and make sure all the expected parameters are there.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Mauryq" <mauryq@.hotmail.com> wrote in message
>> news:3F2DFA2A-C1B9-4219-8EB7-7C71487DF6EF@.microsoft.com...
>> > I have a report with a Dataset that has a query string:
>> >
>> > exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
>> @.Agencia,@.Ruta
>> >
>> > The report is working, but I want to delete the parameter @.Rute and the
>> > follow error are displaying:
>> >
>> > An error has occurred during report processing.
>> > Query execution failed for dataset "resumen"
>> > Must declare the variable @.Usuario.
>> >
>> > Plese help me.
>> >
>> > --
>> > Mauryq
>>|||Mauryq,
whenever get this type of error, I go back to the source and debug from
there.
You say you want to remove a param. Did you already do this on the SProc
itself? Try exec from QA on the SQL instance to ensure the problem isn't at
the source, and then work forwards onto the RS.
Tony
"Bruce L-C [MVP]" wrote:
> I have had mixed results with RS automatically creating the parameters.
> Sometimes it messes up. Did you try either of the two things I mentioned?
> What happens when you click on the ... and go to the parameters tab?
> I have had some stored procedures in SQL Server (I work with both Sybase and
> SQL Server) that worked flawlessly with RS creating the Report Parameter.
> When you have an @.Paramname in your SQL what happens is that RS looks for a
> matching Report Parameter. If it doesn't see it then it assumes that it is a
> T-SQL variable. You can have a multi-line T-SQL code with declare
> @.SOMEVARIABLE. So what is happening to you is that the wiring between your
> query parameters and your report parameters has gotten messed up. It is
> important to remember that they are two different things (which gets
> confusing because RS is being helpful behind the scenes and creating Report
> Parameters).
> You need to do two things. You need to check the parameter mapping ( click
> on the ... and go to the parameter tab and make sure the query parameters
> you expect are all there and are mapped to the appropriate Report
> Parameter). You can also from layout view go to the Report Menu, Parameters.
> You should see
> You say you want to get rid of @.Ruta query parameter. Then you should delete
> it from your query calling code, make sure it is deleted from the query
> parameter to report parameter mapping and finally that it is not still a
> report parameter.
> exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado, @.Agencia
> Note that you can also be in generic query designer and leave off the exec:
> sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado, @.Agencia
> I never use the exec. See if that helps at all.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mauryq" <mauryq@.hotmail.com> wrote in message
> news:7DF27C6B-F720-46D7-A24F-54641DD96461@.microsoft.com...
> > When you create a dataset with a SP with parameters, automatically the
> > parameters are created at the report, but in this case the parameters
> > can't
> > be created automatically, and have that created it manually, and when I
> > eject
> > the preview is like the parameter cant be recognized.
> >
> > exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
> > @.Agencia,@.Ruta
> >
> >
> > "Bruce L-C [MVP]" escribió:
> >
> >> Two things to try. Click on the refresh fields button (to the right of
> >> the
> >> ...). The other thing is to click on the ... and go to the parameters
> >> tab
> >> and make sure all the expected parameters are there.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Mauryq" <mauryq@.hotmail.com> wrote in message
> >> news:3F2DFA2A-C1B9-4219-8EB7-7C71487DF6EF@.microsoft.com...
> >> > I have a report with a Dataset that has a query string:
> >> >
> >> > exec sp_ReporteFlashVentasXRutaYDiario @.Usuario, 1, @.Mercado,
> >> @.Agencia,@.Ruta
> >> >
> >> > The report is working, but I want to delete the parameter @.Rute and the
> >> > follow error are displaying:
> >> >
> >> > An error has occurred during report processing.
> >> > Query execution failed for dataset "resumen"
> >> > Must declare the variable @.Usuario.
> >> >
> >> > Plese help me.
> >> >
> >> > --
> >> > Mauryq
> >>
> >>
> >>
>
>

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!