Microsoft Reporting Services

Default value or value provided for the report parameter 'ParamaterName' is
not a valid value. (rsInvalidReportParameter)
I am getting this error when I am trying to run a deployed report.
However,
this is driving me mad because in the report preview within VS.Net the
report
works fine and i can choose the same parameter settings from within the dev
environment with no problems. I am populating this parameter with a
dropdown
with valid values from a sproc (and this I've done a thousand times before)
.
I can not figure out why it is throwing this error, particularly since it
works perfectly fine in the preview pane. How could it be crappin out when
I
deploy it?!?! I am going insane!
Pl. put in forum.
regards
Arvind Sharma
--
Message posted via http://www.sqlmonster.comOn the deployed report, in report manager, properties... is the prompt string
blank? If so it will try to render the report without prompting for input
which will throw that error.
"arvind sharma via SQLMonster.com" wrote:
> Default value or value provided for the report parameter 'ParamaterName' is
> not a valid value. (rsInvalidReportParameter)
> I am getting this error when I am trying to run a deployed report.
> However,
> this is driving me mad because in the report preview within VS.Net the
> report
> works fine and i can choose the same parameter settings from within the dev
> environment with no problems. I am populating this parameter with a
> dropdown
> with valid values from a sproc (and this I've done a thousand times before)
> ..
> I can not figure out why it is throwing this error, particularly since it
> works perfectly fine in the preview pane. How could it be crappin out when
> I
> deploy it?!?! I am going insane!
> Pl. put in forum.
> regards
> Arvind Sharma
> --
> Message posted via http://www.sqlmonster.com
>sql

Microsft Fix for wrong SP

Hi!
Tried to cure a problem described here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;328551&Product=sql
The article says that
quote:
----
Hotfix 8.00.0702
A supported fix is now available from Microsoft, but it is only
intended to correct the problem described in this article. Only apply
it to systems that are experiencing this specific problem. This fix
may receive additional testing to further ensure product quality.
Therefore, if you are not severely affected by this problem, Microsoft
recommends that you wait for the next Microsoft SQL Server 2000
service pack (sp4) that contains this fix.
----
So I should be able to apply this fix for MS SQL2000 SP3. I could not
do it: It says that I have wrong service pack or version... Why?
Thanks."Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0311120254.3a5323ad@.posting.google.com...
> Tried to cure a problem described here:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;328551&Product=sql
> The article says that
> quote:
> ----
--
> Hotfix 8.00.0702
> A supported fix is now available from Microsoft, but it is only
> intended to correct the problem described in this article. Only apply
> it to systems that are experiencing this specific problem. This fix
> may receive additional testing to further ensure product quality.
> Therefore, if you are not severely affected by this problem, Microsoft
> recommends that you wait for the next Microsoft SQL Server 2000
> service pack (sp4) that contains this fix.
> ----
--
> So I should be able to apply this fix for MS SQL2000 SP3. I could not
> do it: It says that I have wrong service pack or version... Why?
It's possible you need to apply the latest service pack which is SQL Server
2000 SP3a , then apply the hotfix.
Steve|||This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build of
760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
hotfix build 765 to get the fix for SP3.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||- So, what SP matches this service pack, 1st or 2nd?
(I could not install it on MS SQL2000 w/o SP too)
rboyd@.onlinemicrosoft.com (Rand Boyd [MS]) wrote in message news:<uOuMCDYqDHA.1548@.cpmsftngxa06.phx.gbl>...
> This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build of
> 760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
> hotfix build 765 to get the fix for SP3.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.|||"Roust_m" <roustam@.hotbox.ru> wrote in message
news:a388fd78.0311140139.49eb3fc0@.posting.google.com...
> - So, what SP matches this service pack, 1st or 2nd?
> (I could not install it on MS SQL2000 w/o SP too)
If you mean which service patch would match that hotfix -- the hotfix should
work on a post SP2 SQL installation.
For version information
http://support.microsoft.com/default.aspx?scid=kb;en-us;321185&Product=sql
I'd recommend getting the post sp3 hotfix and installing SQL Server SP3a.
Steve
> rboyd@.onlinemicrosoft.com (Rand Boyd [MS]) wrote in message
news:<uOuMCDYqDHA.1548@.cpmsftngxa06.phx.gbl>...
> > This hotfix is a pre-SP3 hotfix. Build number 702 is prior to SP3 build
of
> > 760. This hotfix cannot be applied to SQL Server 2000 SP3. You will need
> > hotfix build 765 to get the fix for SP3.
> >
> > Rand
> > This posting is provided "as is" with no warranties and confers no
rights.|||You need to contact Microsoft and get the post-SP3 hotfix.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Metadata for SP parameter default values

I am looking for a way to list any default values for stored procedure
parameters.
For example with this stored procedure:
CREATE PROC dbo.pr_GetSomeData
(
@.SomeInt int,
@.AnotherInt int = 0,
@.SomeDate datetime = NULL
)
I'd like to be able to create a table that would look like this
ParameterName DefaultValue
@.SomeInt
@.AnotherInt 0
@.SomeDate NULL
I can get at the parameters themselves through information_schema.PARAMETERS
but I don't see a way to get at the default value.
Any suggestions would be appreciated.
Joel Reinford
Data Management Solutions LLCSQL Server does not store information about this in any sys table. One
possible solution could be parsing the sp code from syscomment or
information_schema.routines for the sp in question.
AMB
"Joel Reinford" wrote:

> I am looking for a way to list any default values for stored procedure
> parameters.
> For example with this stored procedure:
> CREATE PROC dbo.pr_GetSomeData
> (
> @.SomeInt int,
> @.AnotherInt int = 0,
> @.SomeDate datetime = NULL
> )
> I'd like to be able to create a table that would look like this
> ParameterName DefaultValue
> @.SomeInt
> @.AnotherInt 0
> @.SomeDate NULL
> I can get at the parameters themselves through information_schema.PARAMETE
RS
> but I don't see a way to get at the default value.
> Any suggestions would be appreciated.
>
> Joel Reinford
> Data Management Solutions LLC
>
>

Meta Data Services

Hello SQL Gurus:
How do I enable the SQL Server Meta Data Services? When I installed the
default instance, during SQL installation for the first time, I did not see
anything about installing meta data services. I am practicing with DTS and in
the Select Source Table And Views page, the SQL Services Meta Data Services
is grayed out and I want to be able to select it and proceed with my tasks in
the 70-228 book about modifying tables and summarizing dta in the
northwindreportdata database using the DTS Import/Export wizard. How do I
enable the meta data services? Thank you.Hi
I have never used this, but one way may be to install the meta data SDK.
John
"Dominick D." wrote:
> Hello SQL Gurus:
> How do I enable the SQL Server Meta Data Services? When I installed the
> default instance, during SQL installation for the first time, I did not see
> anything about installing meta data services. I am practicing with DTS and in
> the Select Source Table And Views page, the SQL Services Meta Data Services
> is grayed out and I want to be able to select it and proceed with my tasks in
> the 70-228 book about modifying tables and summarizing dta in the
> northwindreportdata database using the DTS Import/Export wizard. How do I
> enable the meta data services? Thank you.|||Well, I was looking, but I could not find out how to install the meta data
SDK. Can you point me in the right direction? Thanks.
"John Bell" wrote:
> Hi
> I have never used this, but one way may be to install the meta data SDK.
> John
> "Dominick D." wrote:
> > Hello SQL Gurus:
> >
> > How do I enable the SQL Server Meta Data Services? When I installed the
> > default instance, during SQL installation for the first time, I did not see
> > anything about installing meta data services. I am practicing with DTS and in
> > the Select Source Table And Views page, the SQL Services Meta Data Services
> > is grayed out and I want to be able to select it and proceed with my tasks in
> > the 70-228 book about modifying tables and summarizing dta in the
> > northwindreportdata database using the DTS Import/Export wizard. How do I
> > enable the meta data services? Thank you.|||Hi
I think this is part of the SQL 2000 installation, but I don't remember ever
seeing it!
John
"Dominick D." wrote:
> Well, I was looking, but I could not find out how to install the meta data
> SDK. Can you point me in the right direction? Thanks.
> "John Bell" wrote:
> > Hi
> >
> > I have never used this, but one way may be to install the meta data SDK.
> >
> > John
> >
> > "Dominick D." wrote:
> >
> > > Hello SQL Gurus:
> > >
> > > How do I enable the SQL Server Meta Data Services? When I installed the
> > > default instance, during SQL installation for the first time, I did not see
> > > anything about installing meta data services. I am practicing with DTS and in
> > > the Select Source Table And Views page, the SQL Services Meta Data Services
> > > is grayed out and I want to be able to select it and proceed with my tasks in
> > > the 70-228 book about modifying tables and summarizing dta in the
> > > northwindreportdata database using the DTS Import/Export wizard. How do I
> > > enable the meta data services? Thank you.