Can't Get a Hidden Parameter to Work

I am running 2000 with SP1.
Here's what I've tried so far.
I specified no prompt in the designer (put a blank) and deployed the report.
I got the following error: Parameter validation failed. It is not possible
to provide valid values for all parameters.
I then deleted the prompt in the Report Manager and tried again. It did not
work. I then unchecked the Prompt User box, and it still did not work. In
fact, it kept filling in the prompt field with the name of the parameter.
Therefore, I had to leave the Prompt User box checked. However, for both
scenarios, I got the following error: This report requires a default or
user-defined value for the report parameter 'EmployeeId'. To run or subscribe
to this report, you must provide a parameter value.
Here is the query string I used (not using SSL yet; still testing on my own
machine):
http://<computer
name>/Reports/Pages/Report.aspx?ItemPath=/Emileage/Emileage_Aging_Report_ByEmployee&EmployeeId=0000103518
The EmployeeId is a string so I was not sure how to denote that. I have
tried this with quotes and without quotes around the EmployeeId value, and
neither works.
The employee id is the third parameter. Does it need to be the first one?
Any help would be greatly appreciated.
LizMy suggestion is to first get it working without being hidden.
Your URL is wrong. Don't use /reports use reportserver like this. It will
pull up the report but it will not if I remember correctly fill in your
parameters for you. /reports is reportmanager, the portal that ships with
RS. reportserver is the actual Reporting Services asp.net application.
http://server/reportserver?/Sales/Northwest/Employee Sales
Report&rs:Command=Render&EmployeeID=1234Also make sure your parameter name
matches your case exactly, it is (unfortunately) case sensitive.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Liz" <Liz@.discussions.microsoft.com> wrote in message
news:FB6DFF78-8495-44E0-91C5-E16D81F3BF57@.microsoft.com...
>I am running 2000 with SP1.
> Here's what I've tried so far.
> I specified no prompt in the designer (put a blank) and deployed the
> report.
> I got the following error: Parameter validation failed. It is not possible
> to provide valid values for all parameters.
> I then deleted the prompt in the Report Manager and tried again. It did
> not
> work. I then unchecked the Prompt User box, and it still did not work.
> In
> fact, it kept filling in the prompt field with the name of the parameter.
> Therefore, I had to leave the Prompt User box checked. However, for both
> scenarios, I got the following error: This report requires a default or
> user-defined value for the report parameter 'EmployeeId'. To run or
> subscribe
> to this report, you must provide a parameter value.
> Here is the query string I used (not using SSL yet; still testing on my
> own
> machine):
> http://<computer
> name>/Reports/Pages/Report.aspx?ItemPath=/Emileage/Emileage_Aging_Report_ByEmployee&EmployeeId=0000103518
> The EmployeeId is a string so I was not sure how to denote that. I have
> tried this with quotes and without quotes around the EmployeeId value, and
> neither works.
> The employee id is the third parameter. Does it need to be the first
> one?
> Any help would be greatly appreciated.
> Liz
>|||Yippee! That worked!!
Where can I get some more information on hidden parameters? I looked at the
Books Online but there is almost nothing on Reporting Services. I also have
"The Hitchhiker's Guide" which is a great book, but it doesn't have enough on
hidden parameters. I will, however, go and look at it again. I might get
more out of it this time:-)
Thanks so much!
Liz
"Bruce L-C [MVP]" wrote:
> My suggestion is to first get it working without being hidden.
> Your URL is wrong. Don't use /reports use reportserver like this. It will
> pull up the report but it will not if I remember correctly fill in your
> parameters for you. /reports is reportmanager, the portal that ships with
> RS. reportserver is the actual Reporting Services asp.net application.
> http://server/reportserver?/Sales/Northwest/Employee Sales
> Report&rs:Command=Render&EmployeeID=1234Also make sure your parameter name
> matches your case exactly, it is (unfortunately) case sensitive.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Liz" <Liz@.discussions.microsoft.com> wrote in message
> news:FB6DFF78-8495-44E0-91C5-E16D81F3BF57@.microsoft.com...
> >I am running 2000 with SP1.
> >
> > Here's what I've tried so far.
> >
> > I specified no prompt in the designer (put a blank) and deployed the
> > report.
> > I got the following error: Parameter validation failed. It is not possible
> > to provide valid values for all parameters.
> >
> > I then deleted the prompt in the Report Manager and tried again. It did
> > not
> > work. I then unchecked the Prompt User box, and it still did not work.
> > In
> > fact, it kept filling in the prompt field with the name of the parameter.
> > Therefore, I had to leave the Prompt User box checked. However, for both
> > scenarios, I got the following error: This report requires a default or
> > user-defined value for the report parameter 'EmployeeId'. To run or
> > subscribe
> > to this report, you must provide a parameter value.
> >
> > Here is the query string I used (not using SSL yet; still testing on my
> > own
> > machine):
> > http://<computer
> > name>/Reports/Pages/Report.aspx?ItemPath=/Emileage/Emileage_Aging_Report_ByEmployee&EmployeeId=0000103518
> >
> > The EmployeeId is a string so I was not sure how to denote that. I have
> > tried this with quotes and without quotes around the EmployeeId value, and
> > neither works.
> >
> > The employee id is the third parameter. Does it need to be the first
> > one?
> >
> > Any help would be greatly appreciated.
> >
> > Liz
> >
> >
>
>|||I suggest searching 2005 books on-line on the microsoft site. For things
like url integration absolutely nothing has changed between 2000 and 2005.
How you do hidden parameters I believe has changed. There are some new
features (multi-select parameters, end user sorting) but that does not
affect URL integration. They have lots of good documentation on URL
integration (was not there in the 2000 docs).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Liz" <Liz@.discussions.microsoft.com> wrote in message
news:E328C5E9-1894-4C6F-AB8A-20904F1527D6@.microsoft.com...
> Yippee! That worked!!
> Where can I get some more information on hidden parameters? I looked at
> the
> Books Online but there is almost nothing on Reporting Services. I also
> have
> "The Hitchhiker's Guide" which is a great book, but it doesn't have enough
> on
> hidden parameters. I will, however, go and look at it again. I might get
> more out of it this time:-)
> Thanks so much!
> Liz
> "Bruce L-C [MVP]" wrote:
>> My suggestion is to first get it working without being hidden.
>> Your URL is wrong. Don't use /reports use reportserver like this. It will
>> pull up the report but it will not if I remember correctly fill in your
>> parameters for you. /reports is reportmanager, the portal that ships with
>> RS. reportserver is the actual Reporting Services asp.net application.
>> http://server/reportserver?/Sales/Northwest/Employee Sales
>> Report&rs:Command=Render&EmployeeID=1234Also make sure your parameter
>> name
>> matches your case exactly, it is (unfortunately) case sensitive.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Liz" <Liz@.discussions.microsoft.com> wrote in message
>> news:FB6DFF78-8495-44E0-91C5-E16D81F3BF57@.microsoft.com...
>> >I am running 2000 with SP1.
>> >
>> > Here's what I've tried so far.
>> >
>> > I specified no prompt in the designer (put a blank) and deployed the
>> > report.
>> > I got the following error: Parameter validation failed. It is not
>> > possible
>> > to provide valid values for all parameters.
>> >
>> > I then deleted the prompt in the Report Manager and tried again. It
>> > did
>> > not
>> > work. I then unchecked the Prompt User box, and it still did not work.
>> > In
>> > fact, it kept filling in the prompt field with the name of the
>> > parameter.
>> > Therefore, I had to leave the Prompt User box checked. However, for
>> > both
>> > scenarios, I got the following error: This report requires a default
>> > or
>> > user-defined value for the report parameter 'EmployeeId'. To run or
>> > subscribe
>> > to this report, you must provide a parameter value.
>> >
>> > Here is the query string I used (not using SSL yet; still testing on my
>> > own
>> > machine):
>> > http://<computer
>> > name>/Reports/Pages/Report.aspx?ItemPath=/Emileage/Emileage_Aging_Report_ByEmployee&EmployeeId=0000103518
>> >
>> > The EmployeeId is a string so I was not sure how to denote that. I
>> > have
>> > tried this with quotes and without quotes around the EmployeeId value,
>> > and
>> > neither works.
>> >
>> > The employee id is the third parameter. Does it need to be the first
>> > one?
>> >
>> > Any help would be greatly appreciated.
>> >
>> > Liz
>> >
>> >
>>

Can't connect using SqlClient after creating new database.

Hi,

I am writing a c# console application that allows you to update a database to a specified version. It does this by running a set of scripts that are listed in an xml manifest.

The application also provides an option to create the database and then run scripts to update it.

I have a method that reads blocks of SQL from each script and runs them using the ADO.NET classes in the SqlClient namespace.

I am finding that after the application runs the script to create the database, the first time the application tries to connect to that new database the connection attempt fails. The error I receive is :-

Cannot open database {dbname} requested by the login. The login failed.
Login failed for user {user}

I find that if I set the thread to sleep for 3 seconds after the database is created, I can then connect without the error occurring, but this is a bit of a nasty hack. I'd prefer to find a better solution.

This is occurring against a local SQL Server Express instance.

My machine is reasonable. 3.4 Ghz. 2Gb RAM, so I wouldn't have thought there's any problems in that regard.

Does anyone have any pointers, firstly as to why this is occurring, and secondly, how I might solve this problem in a nicer way?

Thanks,

David.

Hi David,

This is strange behaviour. Are you using Windows auth or SQL auth? Also, are there any errors written to your error log?

Thanks,
Il-Sung.

|||

Hi ll-Sung,

Sorry it has taken so long for me to get back to you about this.

My SQL Express is set up for Windows Auth only, and I am connecting as such.

The exception I receive when I try to connect after creating the database is :-

Cannot open database "DatabaseName" requested by the login. The login failed.

Login failed for user 'Domain\UserName'.

Both the SQL Log and the Windows Event Log display a series of informational messages that occur during the creation of the database. Things like :-

Setting database option ANSI_PADDING to OFF for database DatabaseName

Also in the logs, I receive a Failure Audit error message. This occurs before any of the informational messages occur. It looks like :-

Login failed for user 'Domain\UserName'. [CLIENT: <local machine>]

However this login failure message appears whether or not the database creation succeeds or not (ie the process succeeds when I have my Sleep command in).

So overall, I guess there is no error in any of the logs indicating why this is occurring.

The SQL I am using to create the database is a script that I made simply by scripting off the db in Management Studio. I did not muck around with this at all except to put placeholders in for the database name.

Any further help you can provide for this would be much appreciated.

Thanks,

David.

Can't connect remotely to WSUS referential MSDE database

Hi all,

WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.

I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.

FROM THE SERVER :

osql -E -S MYSERVER\WSUS works fine but

osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error

[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).

If i user "osql -L" command, my instance doesn't appear in the list

FROM A CLIENT COMPUTER

osql -E -S MYSERVER\WSUS and

osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error

I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran

select @.@.version from osql and got result

Microsoft SQL Server 2000 - 8.00.881 (Intel X86)

8.00.881 is not referenced in ms support as a patched version number !!!!!

Can anyone help me please ?

hi,

Shogre wrote:

Hi all,

WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.

I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.

FROM THE SERVER :

osql -E -S MYSERVER\WSUS works fine but

osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error

[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).

If i user "osql -L" command, my instance doesn't appear in the list

FROM A CLIENT COMPUTER

osql -E -S MYSERVER\WSUS and

osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error

I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran

select @.@.version from osql and got result

Microsoft SQL Server 2000 - 8.00.881 (Intel X86)

8.00.881 is not referenced in ms support as a patched version number !!!!!

Can anyone help me please ?

yep, I did not find 8.00.881 build as well... http://www.aspfaq.com/SQL2000Builds.asp ... where did you get it?

anyway... usually named instances do not listen on TCP/IP 1433 port as this one is "reserved" for default instances... using the Server Network Utility you shoud check if your named instance is listening on a dynamic associated port or on a fixed port as you should define a firewall exception as well for it... have a look at http://support.microsoft.com/kb/841249/en-us and http://support.microsoft.com/kb/841251/en-us for further info about the built in W2003 Windows Firewall and how to configure it for remote connections...

regards