@!#$%^&*( SSL/TLS

OK, I have a fresh installation. I installed SSL prior to SQL Server 2005 and let the installer create the default configuration. SSL is working, cert auth is in place. Started up Report Manager and it is working. Tried out Report Builder and it is working just fine. I go to run some reports, I get the parameters (some are dynamic) working fine. When I go to render the report I get the almighty dreaded

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. The remote certificate is invalid according to the validation procedure.

Anyone have any ideas what is going on?

Report Server Virtual directory is set to 3 - All Soap APIs.

Just to recap, Report Manager, OK. Report Builder, OK, Params OK, Report Data, NOT OK.

R

Just found out, it isn't asking for credentials. Looks like it is trying to use ASPNET. Now I am lost.

Hi Ron. I'm having the exact same issue as you, and I'm also completely lost. I even can see the reports from ReportServer (https://myserver:mysslport/ReportServer), but not from Report Manager. Have you find any clue on this?

Thanks,

Julio

@!#$%^&*( SSL/TLS

OK, I have a fresh installation. I installed SSL prior to SQL Server 2005 and let the installer create the default configuration. SSL is working, cert auth is in place. Started up Report Manager and it is working. Tried out Report Builder and it is working just fine. I go to run some reports, I get the parameters (some are dynamic) working fine. When I go to render the report I get the almighty dreaded

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. The remote certificate is invalid according to the validation procedure.

Anyone have any ideas what is going on?

Report Server Virtual directory is set to 3 - All Soap APIs.

Just to recap, Report Manager, OK. Report Builder, OK, Params OK, Report Data, NOT OK.

R

Just found out, it isn't asking for credentials. Looks like it is trying to use ASPNET. Now I am lost.

Hi Ron. I'm having the exact same issue as you, and I'm also completely lost. I even can see the reports from ReportServer (https://myserver:mysslport/ReportServer), but not from Report Manager. Have you find any clue on this?

Thanks,

Julio

|||I was also having this problem and found a solution here:
http://ezra.auerbach.co.il/?postid=7

You need to add the root certifacate of the one being used by the sharepoint and reporting services IIS sites to the computer's Trusted Root Authorities.sql

::fn_trace_getinfo(default)

To check for any traces running :
SELECT * FROM ::fn_trace_getinfo(default)
Why do we use the :: before the function name ?Hassan
Take a look at this article
http://vyaskn.tripod.com/fn_get_sql.htm
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
> To check for any traces running :
> SELECT * FROM ::fn_trace_getinfo(default)
> Why do we use the :: before the function name ?
>
>|||But it does not answer my question of the 2 colons :: ?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
> Hassan
> Take a look at this article
> http://vyaskn.tripod.com/fn_get_sql.htm
>
>
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
>> To check for any traces running :
>> SELECT * FROM ::fn_trace_getinfo(default)
>> Why do we use the :: before the function name ?
>>
>|||In books online
System table functions that are included in Microsoft=AE SQL Server=99
2000 need to be invoked using a '::' prefix before the function name.
Regards
Amish|||Hi,
If i am not wrong the owner of these functions (there are several others)
seems system_function_schema. Which means there is no corresponding user for
them on master db. And you can only refer them using ::.
That's what i know but there might be a better explanation..
"Hassan" wrote:
> But it does not answer my question of the 2 colons :: ?
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
> > Hassan
> > Take a look at this article
> > http://vyaskn.tripod.com/fn_get_sql.htm
> >
> >
> >
> >
> >
> >
> > "Hassan" <Hassan@.hotmail.com> wrote in message
> > news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
> >> To check for any traces running :
> >>
> >> SELECT * FROM ::fn_trace_getinfo(default)
> >>
> >> Why do we use the :: before the function name ?
> >>
> >>
> >>
> >
> >
>
>

::fn_trace_getinfo(default)

To check for any traces running :
SELECT * FROM ::fn_trace_getinfo(default)
Why do we use the :: before the function name ?
Hassan
Take a look at this article
http://vyaskn.tripod.com/fn_get_sql.htm
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
> To check for any traces running :
> SELECT * FROM ::fn_trace_getinfo(default)
> Why do we use the :: before the function name ?
>
>
|||But it does not answer my question of the 2 colons :: ?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
> Hassan
> Take a look at this article
> http://vyaskn.tripod.com/fn_get_sql.htm
>
>
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
>
|||In books online
System table functions that are included in Microsoft=AE SQL Server=99
2000 need to be invoked using a '::' prefix before the function name.
Regards
Amish
|||Hi,
If i am not wrong the owner of these functions (there are several others)
seems system_function_schema. Which means there is no corresponding user for
them on master db. And you can only refer them using ::.
That's what i know but there might be a better explanation..
"Hassan" wrote:

> But it does not answer my question of the 2 colons :: ?
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
>
>

::fn_trace_getinfo(default)

To check for any traces running :
SELECT * FROM ::fn_trace_getinfo(default)
Why do we use the :: before the function name ?Hassan
Take a look at this article
http://vyaskn.tripod.com/fn_get_sql.htm
"Hassan" <Hassan@.hotmail.com> wrote in message
news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
> To check for any traces running :
> SELECT * FROM ::fn_trace_getinfo(default)
> Why do we use the :: before the function name ?
>
>|||But it does not answer my question of the 2 colons :: ?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
> Hassan
> Take a look at this article
> http://vyaskn.tripod.com/fn_get_sql.htm
>
>
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:uJ09PygAGHA.2912@.tk2msftngp13.phx.gbl...
>|||In books online
System table functions that are included in Microsoft=AE SQL Server=99
2000 need to be invoked using a '::' prefix before the function name.
Regards
Amish|||Hi,
If i am not wrong the owner of these functions (there are several others)
seems system_function_schema. Which means there is no corresponding user fo
r
them on master db. And you can only refer them using ::.
That's what i know but there might be a better explanation..
"Hassan" wrote:

> But it does not answer my question of the 2 colons :: ?
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ezuePShAGHA.436@.TK2MSFTNGP10.phx.gbl...
>
>

(Select All) Checkbox As Default

All,

When creating a dynamic parameter list from a query, Reporting Services graciously provides a "(Select All)" checkbox. How can I select this checkbox by default so that when a user generates the report, all of the values are selected?

Thanks

The "select all" item is just a UI concept at this point. You could setup a default value for the report parameter that contains all values of the valid values list - but in that case all the checkboxes for individual items would be pre-selected, but the "select all" would still not be pre-selected.

-- Robert

|||Thanks for the reply. I actually tried your approach before posting my question. The problem that I am facing when using this approach is that the pre-selection is always static so this will not work when my checkbox list is populated from a query. Since the results of the query are dynamic, I can't setup a default list with any degree of accuracy.|||

Robert,

Is there any way to tell when the Select All option is selected?

R

|||

I don't know if this works

But if my dropdown source is Query, and with "Multi-Value items" checkbox checked

Under Default Values, If I choose "Query", pick the Dataset, put in the value field -> it will select all rows in the query by default

When I go to Preview, all items from the query ARE checked in the dropdown. Even the "ALL" option I created myself

(now the problem is, how do you uncheck them all with ease...)

I hope that's what you're looking for, I wish there's easy way to post pictures

|||

The closest you can get is to compare the number of rows in the dataset used for the valid values list (e.g. =CountRows("ParameterDataSetName")) with the number of selected parameter values (e.g. =Parameters!P1.Count)

-- Robert

(Select All) Checkbox As Default

All,

When creating a dynamic parameter list from a query, Reporting Services graciously provides a "(Select All)" checkbox. How can I select this checkbox by default so that when a user generates the report, all of the values are selected?

Thanks

The "select all" item is just a UI concept at this point. You could setup a default value for the report parameter that contains all values of the valid values list - but in that case all the checkboxes for individual items would be pre-selected, but the "select all" would still not be pre-selected.

-- Robert

|||Thanks for the reply. I actually tried your approach before posting my question. The problem that I am facing when using this approach is that the pre-selection is always static so this will not work when my checkbox list is populated from a query. Since the results of the query are dynamic, I can't setup a default list with any degree of accuracy.|||

Robert,

Is there any way to tell when the Select All option is selected?

R

|||

I don't know if this works

But if my dropdown source is Query, and with "Multi-Value items" checkbox checked

Under Default Values, If I choose "Query", pick the Dataset, put in the value field -> it will select all rows in the query by default

When I go to Preview, all items from the query ARE checked in the dropdown. Even the "ALL" option I created myself

(now the problem is, how do you uncheck them all with ease...)

I hope that's what you're looking for, I wish there's easy way to post pictures

|||

The closest you can get is to compare the number of rows in the dataset used for the valid values list (e.g. =CountRows("ParameterDataSetName")) with the number of selected parameter values (e.g. =Parameters!P1.Count)

-- Robert

(Select All) Checkbox As Default

All,

When creating a dynamic parameter list from a query, Reporting Services graciously provides a "(Select All)" checkbox. How can I select this checkbox by default so that when a user generates the report, all of the values are selected?

Thanks

The "select all" item is just a UI concept at this point. You could setup a default value for the report parameter that contains all values of the valid values list - but in that case all the checkboxes for individual items would be pre-selected, but the "select all" would still not be pre-selected.

-- Robert

|||Thanks for the reply. I actually tried your approach before posting my question. The problem that I am facing when using this approach is that the pre-selection is always static so this will not work when my checkbox list is populated from a query. Since the results of the query are dynamic, I can't setup a default list with any degree of accuracy.|||

Robert,

Is there any way to tell when the Select All option is selected?

R

|||

I don't know if this works

But if my dropdown source is Query, and with "Multi-Value items" checkbox checked

Under Default Values, If I choose "Query", pick the Dataset, put in the value field -> it will select all rows in the query by default

When I go to Preview, all items from the query ARE checked in the dropdown. Even the "ALL" option I created myself

(now the problem is, how do you uncheck them all with ease...)

I hope that's what you're looking for, I wish there's easy way to post pictures

|||

The closest you can get is to compare the number of rows in the dataset used for the valid values list (e.g. =CountRows("ParameterDataSetName")) with the number of selected parameter values (e.g. =Parameters!P1.Count)

-- Robert

(Problem) Named instance as SQLEXPRESS?

What if I give my named instance as SQLEXPRESS? I read that SQLEXPRESS

would be the name of the DEFAULT instance if no named instance is given.

In such a situation how can I find out if its a named or the default one?

SQLExpress is always a named instance.

jens K. Suessmeyer.

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

Hi Ananda,

You might be a bit confused by the terms "default instance" and the fact that SQL Express is installed by default as a named instance.

Default Instance - This is the term we use to describe the copy of SQL Server that can be refered to by just the name of the computer in a connection string. There can only be one default instance of SQL Server on any computer. This is compared to a named instance, which is refered to by the <machine name>\<named instance name> in the connection string.

As Jens points out, SQL Express is installed by default as a named instance, and that named instance is SQLEXPRESS. If you specified SQLEXPRESS for the INSTANCENAME parameter in a command line install, or in the UI, you have installed a named instance. You can also install to a different named instance (up to 16 different instances for SQL Express) or you can install SQL Express as the default instance, but the default instance does not have a specific instance name.

Mike