(local) name explanation please

In some SQL2K instances, I have (LOCAL) in others its (Local) and in
development code the connect to server parameter is always local.
Where is (local) associated to 127.0.0.1 or local server name?
If I have 2 or more instances of SQL Server on my maching which one would
(local) refer too?
TIA
Neil.
(local) or . refers to the local machine. The dot (.) or local tells the
client that the host is local and not remote, such that a local pipe
connection can be made. This avoids going on the network. This applied
more so to SQL 6.5, and SQL 7.0, since with SQL 2000 we use Shared Memory
for local connections.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thanks for your response.
So this is pipe and not tcp/ip then. Can you point me to any books
on-line/help files that actually explain the local usage please as they must
be somewhere?
Also do you know why LOCAL is uppercase on some machines and lowercase on
others in EM I mean?
thanks
"Kevin McDonnell [MSFT]" wrote:

> (local) or . refers to the local machine. The dot (.) or local tells the
> client that the host is local and not remote, such that a local pipe
> connection can be made. This avoids going on the network. This applied
> more so to SQL 6.5, and SQL 7.0, since with SQL 2000 we use Shared Memory
> for local connections.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||Yes. local pipe is a pipe connection not a socket based connection.
We mention local pipes briefly in Books Online under the topic "Client and
Server Net-Libraries".
I've also seen it discussed in Network Programming books.
"Windows NT Network Programming" Davis.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

(local) name explanation please

In some SQL2K instances, I have (LOCAL) in others its (Local) and in
development code the connect to server parameter is always local.
Where is (local) associated to 127.0.0.1 or local server name?
If I have 2 or more instances of SQL Server on my maching which one would
(local) refer too?
TIA
Neil.(local) or . refers to the local machine. The dot (.) or local tells the
client that the host is local and not remote, such that a local pipe
connection can be made. This avoids going on the network. This applied
more so to SQL 6.5, and SQL 7.0, since with SQL 2000 we use Shared Memory
for local connections.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks for your response.
So this is pipe and not tcp/ip then. Can you point me to any books
on-line/help files that actually explain the local usage please as they must
be somewhere?
Also do you know why LOCAL is uppercase on some machines and lowercase on
others in EM I mean?
thanks
"Kevin McDonnell [MSFT]" wrote:

> (local) or . refers to the local machine. The dot (.) or local tells th
e
> client that the host is local and not remote, such that a local pipe
> connection can be made. This avoids going on the network. This applied
> more so to SQL 6.5, and SQL 7.0, since with SQL 2000 we use Shared Memory
> for local connections.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Yes. local pipe is a pipe connection not a socket based connection.
We mention local pipes briefly in Books Online under the topic "Client and
Server Net-Libraries".
I've also seen it discussed in Network programming books.
"Windows NT Network Programming" Davis.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

"Select all" as default for a multi-value parameter

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

...Does anybody know how to accomplish this?

(...or the reason why this is impossible?)

Stefano

StefanoEbitAET wrote:

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

|||If you set the default to query and then point it to the same query that populates the choices all will be selected.|||

Thank you very much:

I had already tried this solution before -without success- and quitted...

after reading your reply I've been pushed to try again and I discovered the problem: my query was returning 4 good values and a "null" one... and apparently this is not allowed (no default value was considered).

Thanks again

Stefano

|||I've tried pointing back as well - it works, but it seems like the query then gets executed another time. I wish there was a way to prevent this..

Something I'd like to do: Leaving the parameter blank.
Then RS complains that it wants a value. Wouldn't that be a bug if 'allow blank' is checked?|||I dont think so(but i am not sure), because no record has blank as key. If you want "blank" as an option you can use allow null instead.|||Thanks a lot.
It worked & solved my problem (Even without raising a thread!!!)

"Select all" as default for a multi-value parameter

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

...Does anybody know how to accomplish this?

(...or the reason why this is impossible?)

Stefano

StefanoEbitAET wrote:

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

|||If you set the default to query and then point it to the same query that populates the choices all will be selected.|||

Thank you very much:

I had already tried this solution before -without success- and quitted...

after reading your reply I've been pushed to try again and I discovered the problem: my query was returning 4 good values and a "null" one... and apparently this is not allowed (no default value was considered).

Thanks again

Stefano

|||I've tried pointing back as well - it works, but it seems like the query then gets executed another time. I wish there was a way to prevent this..

Something I'd like to do: Leaving the parameter blank.
Then RS complains that it wants a value. Wouldn't that be a bug if 'allow blank' is checked?|||I dont think so(but i am not sure), because no record has blank as key. If you want "blank" as an option you can use allow null instead.|||Thanks a lot.
It worked & solved my problem (Even without raising a thread!!!)

"Select all" as default for a multi-value parameter

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

...Does anybody know how to accomplish this?

(...or the reason why this is impossible?)

Stefano

StefanoEbitAET wrote:

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

|||If you set the default to query and then point it to the same query that populates the choices all will be selected.|||

Thank you very much:

I had already tried this solution before -without success- and quitted...

after reading your reply I've been pushed to try again and I discovered the problem: my query was returning 4 good values and a "null" one... and apparently this is not allowed (no default value was considered).

Thanks again

Stefano

|||I've tried pointing back as well - it works, but it seems like the query then gets executed another time. I wish there was a way to prevent this..

Something I'd like to do: Leaving the parameter blank.
Then RS complains that it wants a value. Wouldn't that be a bug if 'allow blank' is checked?|||I dont think so(but i am not sure), because no record has blank as key. If you want "blank" as an option you can use allow null instead.|||Thanks a lot.
It worked & solved my problem (Even without raising a thread!!!)

"Select all" as default for a multi-value parameter

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

...Does anybody know how to accomplish this?

(...or the reason why this is impossible?)

Stefano

StefanoEbitAET wrote:

Hi!

I have the following problem:

In my report I have -among others- a multi-value parameter, populated by a query (so I cannot a priori know the content of the list).

I would like my report to start without any user choice, through default parameters, so what I need is the "select all" choice selected by default. How can I achieve this?

[The only default value I am able to pass to the multi-value parameter is one of the elements populating the list, statically writing it in the "Non-queried" section of "Default values": "From query" option seems not to work for multi-valued]

Any help will be greatly appreciated!

Thanks

Stefano

|||If you set the default to query and then point it to the same query that populates the choices all will be selected.|||

Thank you very much:

I had already tried this solution before -without success- and quitted...

after reading your reply I've been pushed to try again and I discovered the problem: my query was returning 4 good values and a "null" one... and apparently this is not allowed (no default value was considered).

Thanks again

Stefano

|||I've tried pointing back as well - it works, but it seems like the query then gets executed another time. I wish there was a way to prevent this..

Something I'd like to do: Leaving the parameter blank.
Then RS complains that it wants a value. Wouldn't that be a bug if 'allow blank' is checked?|||I dont think so(but i am not sure), because no record has blank as key. If you want "blank" as an option you can use allow null instead.|||Thanks a lot.
It worked & solved my problem (Even without raising a thread!!!)

"Parameters" approach to fill report header with source data doesn't work

It's well known issue, that one can't use any dataset fields in a

report header/footer directly. One of the approach is to create

query-based parameter that basically equals

=First(Fields!@.FieldName@..Value, "@.DataSetName@.") and use that

parameter value instead. But it doesn't work in my case!

My report displays some entity description and is parametrized with

EntityID param. Its header contains entity name that, according to the

approach, is queried from the data source through the EntityName

report parameter. There's important issue: the report is displayed in

ReportViewer control, that is embedded into my application and entity

ID parameter isn't ser by user in ReportViewer parameters area. Its

default value is changed by the application with SetReportParameters()

web method every time a user wants to view the report according to the

entity the user is exploring in the application. But after the report

has been rendered, its header always contains not actual (outdated)

entity name. Nevertheless, the report body contains actual data

(including entity name). If I alter entity ID parameter in ReportViewer

or in web-based Report Manager and refresh report, header displays

correct entity name.

What's wrong in the workflow described?Up! SSRS can't deal with data in hearders, can it?|||

There is a way:

You can make the header fields refere to databound fields which are location within the body of the reports- to get your results ie You can put a hidden text field in the body and reference that field!

|||

Hi Viral,

If we put the hidden textbox in the body and use those textbox value it works perfectly here the problem is if our result in 5 pages when we export this result to PDF , the problem here is for the first page only the textbox value in the header is displaying from next page onwards it is displaying null values eventhough we made the property of textbox "Repeat With" :table1(result set) set.

Thanks

"One or more DataSources is missing credentials"

Get this when selecting parameter value in Report Manager

Report is working fine in preview

Up to me, it has nothing to do with credentials

I have some analysis server reports.

I have a single value report parameter, the report runs fine with the default value, when I select another value than the default one, I get above message immediately.

I got the error since I rebuild the report with SP2 CTP.

Strange thing is that the other single value parameter of the report works fine (year)

And that I get the error also with other reports, and on the same dimension (Organisation)

And that I do not have the error when I change the parameter to multi-value (but as the report is not written for multiple values...)

MDX queries are as follows:

SELECT NON EMPTY { KPIValue("KPINewBiz"), KPIGoal("KPINewBiz"), KPIStatus("KPINewBiz"), KPITrend("KPINewBiz") } ON COLUMNS,

NONEMPTY

([Reps].[Organisation].[Organisation].ALLMEMBERS

*[Reps].[Rep].[Rep].ALLMEMBERS

*[Date].[Year].[Year].ALLMEMBERS

*[Date].[Month].[Month].ALLMEMBERS

,[Measures].[Gross Sales]

)

DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS

FROM ( SELECT ( STRTOSET(@.ByYear, CONSTRAINED) ) ON COLUMNS FROM ( SELECT ( STRTOSET(@.ByOrganisation, CONSTRAINED) ) ON COLUMNS FROM [Sales])) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

WITH MEMBER [Measures].[ParameterCaption] AS '[Reps].[Organisation].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Reps].[Organisation].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Reps].[Organisation].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,

NONEMPTY([Reps].[Organisation].[Organisation].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

WITH MEMBER [Measures].[ParameterCaption] AS '[Date].[Year].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Date].[Year].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Date].[Year].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , NONEMPTY([Date].[Year].[Year].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

Discovered something else that is very strange, you change the value of the parameter, you get the error, you hit the back button, and you can run the report with the new parameter

Did one more test, changed the order of the parameters, is now going wrong on the other parameter, Year.

So, it is always on the first parameter.

Correction, I have put a multi-value parameter as first, I still have the problem, it is always on the first single value parameter

I have the same problem.

Up to me, it has nothing to do with credentials

I have some analysis server reports.

I have a single value report parameter, the report runs fine with the default value, when I select another value than the default one, I get above message immediately.

I got the error since I rebuild the report with SP2 CTP.

Strange thing is that the other single value parameter of the report works fine (year)

And that I get the error also with other reports, and on the same dimension (Organisation)

And that I do not have the error when I change the parameter to multi-value (but as the report is not written for multiple values...)

MDX queries are as follows:

SELECT NON EMPTY { KPIValue("KPINewBiz"), KPIGoal("KPINewBiz"), KPIStatus("KPINewBiz"), KPITrend("KPINewBiz") } ON COLUMNS,

NONEMPTY

([Reps].[Organisation].[Organisation].ALLMEMBERS

*[Reps].[Rep].[Rep].ALLMEMBERS

*[Date].[Year].[Year].ALLMEMBERS

*[Date].[Month].[Month].ALLMEMBERS

,[Measures].[Gross Sales]

)

DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS

FROM ( SELECT ( STRTOSET(@.ByYear, CONSTRAINED) ) ON COLUMNS FROM ( SELECT ( STRTOSET(@.ByOrganisation, CONSTRAINED) ) ON COLUMNS FROM [Sales])) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

WITH MEMBER [Measures].[ParameterCaption] AS '[Reps].[Organisation].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Reps].[Organisation].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Reps].[Organisation].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,

NONEMPTY([Reps].[Organisation].[Organisation].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

WITH MEMBER [Measures].[ParameterCaption] AS '[Date].[Year].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Date].[Year].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Date].[Year].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , NONEMPTY([Date].[Year].[Year].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

Discovered something else that is very strange, you change the value of the parameter, you get the error, you hit the back button, and you can run the report with the new parameter

Microsoft released a December update to the CTP yesterday. The update fixes the problem.

http://www.microsoft.com/downloads/details.aspx?FamilyId=D2DA6579-D49C-4B25-8F8A-79D14145500D&displaylang=en

|||thanks

"Less Than or Equal To" MDX query

The following MDX query is generated by the Reporting Services? I need to edit the this MDX query so that it will accept the parameter value "Less Than Or Equal To" the @.AccountPeriodAccountPeriod parameter to filter teh cube data. Thanks.

SELECT NON EMPTY { [Measures].[Costing], [Measures].[Distinct Count] } ON COLUMNS, NON EMPTY { ([AgencyID].[Agency Id].[Agency Id].ALLMEMBERS * [Account Period].[Account Period].[Account Period].ALLMEMBERS * [Account Period].[Prescription Date].[Prescription Date].ALLMEMBERS * [Drug].[Protocol Code].[Protocol Code].ALLMEMBERS * [Drug].[Drug Name].[Drug Name].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM ( SELECT (STRTOSET(@.AccountPeriodAccountPeriod, CONSTRAINED)) ON COLUMNS FROM ( SELECT ( STRTOSET(@.DrugDrugFirstWord, CONSTRAINED) ) ON COLUMNS FROM [Drug Cost By Account Period])) WHERE ( IIF( STRTOSET(@.DrugDrugFirstWord, CONSTRAINED).Count = 1, STRTOSET(@.DrugDrugFirstWord, CONSTRAINED), [Drug].[Drug First Word].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

Assuming that there is an [AccountPeriod].[AccountPeriod] attribute, ordered ascending by time:

SELECT (Filter([AccountPeriod].[AccountPeriod].[AccountPeriod].Members,

Rank([AccountPeriod].[AccountPeriod].CurrentMember,

[AccountPeriod].[AccountPeriod].[AccountPeriod].Members) < =

Rank(STRTOSET(@.AccountPeriodAccountPeriod, CONSTRAINED).Item(0).Item(0),

[AccountPeriod].[AccountPeriod].[AccountPeriod].Members)))

|||Thank you Deepak Puri and it is worked beautifully. However I forgot to include one other condition that only the AgencyID has the Account Period equal to the @.AccountPeriod should be allowed in the final dataset. AgencyID is from another dimension different from the Account Period dimension. Thanks.|||

If you want only those AgencyID members with [Measures].[Costing] data for the selected Account Period, try replacing:

[AgencyID].[Agency Id].[Agency Id].ALLMEMBERS

with:

NonEmpty([AgencyID].[Agency Id].[Agency Id].ALLMEMBERS,

{[Measures].[Costing]} *

STRTOSET(@.AccountPeriodAccountPeriod, CONSTRAINED))

"lenght cannot be less than zero. Parameter name : lenght"

I'm using Visual Studio 2005, and when i try to drop a table from a data source( SQL Mobile database), to a new or existing form, always occors the error ""lenght cannot be less than zero. Parameter name : lenght"" , my project has more than one forms.
If i make the same steps on a new project with only one form, i can drop the same table without problems.
Anyone can help with this problem?

best regards,

Pedro Nogueira

Pedro,

It sounds like you are using the drag and drop data binding in a Windows Forms application using SQL Mobile as the data source?

First I recommend ensuring that you are running VS2005 Service Pack 1. If you are or still have this issue after upgrading, to recreate

this, we would need some insight into your database schema and how you are doing the drag and drop onto the form (are you dropping

the whole table? are you bound to a datagrid or to another control, etc)

What I'm saying is that I don't hear of anyone having problems with drag & drop of SQL Mobile/SQL CE tables onto forms with

VS2005 SP1, so you either have a bad install or have indeed found a bug. Happy to help you with that but would need more info

on your database and how you're doing the binding.

Darren Shaffer

"Key cannot be null. Parameter name: key"

We are using forms authentication with SSRS2005 and we are able to access Report Manager (http://servername/reports) and Reportserver (http://servername/reportserver). The problem we are having is every time we add a user to the Content Manager or the Publisher role. The user is able to login and reach the Report Manager but no folder is showing up and also we have the following error message : "Key cannot be null. Parameter name: key".

We removed users from the Content Manager and Publisher Roles and they are able to reach report manager and see the folders. This only happens with report manager. everything works fine with reportserver(http://servername/reportserver).

Any idea why we're getting an error message when trying to assign the Content Manager and publisher Roles to a user.

here is the error log from ReportServerWebApp :

aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: Key cannot be null.
Parameter name: key
aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: HTTP status code --> 500
-Details--
System.ArgumentNullException: Key cannot be null.

Parameter name: key

at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)

at System.Collections.Hashtable.Add(Object key, Object value)

at Microsoft.ReportingServices.UI.BasePermissions.ReadPermissions(String[] permissions)

at Microsoft.ReportingServices.UI.Permissions.GetPermissions()

at Microsoft.ReportingServices.UI.Permissions.CurrentUser(String itemPath)

at Microsoft.ReportingServices.UI.FolderPage.Page_Init(Object sender, EventArgs e)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Web.UI.Control.OnInit(EventArgs e)

at System.Web.UI.Page.OnInit(EventArgs e)

at System.Web.UI.Control.InitRecursive(Control namingContainer)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

Thanks!

chi

Hi

Check the following post out, it may help

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=327150&SiteID=1

|||

i checked the link, hmmm... did not work. any other suggestions.

chi

"Key cannot be null. Parameter name: key"

We are using forms authentication with SSRS2005 and we are able to access Report Manager (http://servername/reports) and Reportserver (http://servername/reportserver). The problem we are having is every time we add a user to the Content Manager or the Publisher role. The user is able to login and reach the Report Manager but no folder is showing up and also we have the following error message : "Key cannot be null. Parameter name: key".

We removed users from the Content Manager and Publisher Roles and they are able to reach report manager and see the folders. This only happens with report manager. everything works fine with reportserver(http://servername/reportserver).

Any idea why we're getting an error message when trying to assign the Content Manager and publisher Roles to a user.

here is the error log from ReportServerWebApp :

aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: Key cannot be null.
Parameter name: key
aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: HTTP status code --> 500
-Details--
System.ArgumentNullException: Key cannot be null.

Parameter name: key

at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)

at System.Collections.Hashtable.Add(Object key, Object value)

at Microsoft.ReportingServices.UI.BasePermissions.ReadPermissions(String[] permissions)

at Microsoft.ReportingServices.UI.Permissions.GetPermissions()

at Microsoft.ReportingServices.UI.Permissions.CurrentUser(String itemPath)

at Microsoft.ReportingServices.UI.FolderPage.Page_Init(Object sender, EventArgs e)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Web.UI.Control.OnInit(EventArgs e)

at System.Web.UI.Page.OnInit(EventArgs e)

at System.Web.UI.Control.InitRecursive(Control namingContainer)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
aspnet_wp!ui!1!3/27/2007-16:38:49:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)

Thanks!

chi

Hi

Check the following post out, it may help

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=327150&SiteID=1

|||

i checked the link, hmmm... did not work. any other suggestions.

chi

"Duplicated parameter names are not allowed" exception in SQL Server Everywhere

I'm using SQL Server Everywhere CTP with ADO.NET and C# 2.0 and getting following exception:
"Duplicated parameter names are not allowed. [ Parameter name = @.NODE_ID ]"
for the query:

SELECT CHANGE_TYPE,CHANGED,VTRANS,LINK_PARTITION_ID,LINK_ID, SOURCE_PARTITION_ID,SOURCE_NODE_ID,TARGET_PARTITION_ID,TARGET_NODE_ID,TYPE,LOCAL_CHANGE_TIME,ATTR FROM VP8657b26964d4c595a7430761c222f3b3_REL WHERE (((TARGET_NODE_ID=@.NODE_ID AND REL_BASE_TYPE=2)) AND LOCAL_CHANGE_TIME > @.LOCAL_CHANGE_TIME ) OR ((SOURCE_NODE_ID=@.NODE_ID AND REL_BASE_TYPE=2)) ORDER BY LOCAL_CHANGE_TIME DESC

Without underlined frament, query runs fine

IDbCommand.Parameters shows that there are exactly 2 parameters with different names: @.LOCAL_CHANGE_TIME and @.NODE_ID

Exception stack trace is:
System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.CompileQueryPlan() + 0xd5 bytes
System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand(System.Data.CommandBehavior behavior = Default, string method = "ExecuteReader", System.Data.SqlServerCe.ResultSetOptions options = None) + 0x145 bytes
System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.ExecuteReader(System.Data.CommandBehavior behavior = Default) + 0x2d bytes
System.Data.SqlServerCe.dll!System.Data.SqlServerCe.SqlCeCommand.ExecuteDbDataReader(System.Data.CommandBehavior behavior = Default) + 0x1e bytes
System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader() + 0xa bytes

So, what this exception might mean? does it mean that a parameter might not be used multiple times in a query?

alex777 wrote:

So, what this exception might mean? does it mean that a parameter might not be used multiple times in a query?

Unfortunately, that's precisely what it means. If you watch (with SQL Profiler, for example) how a query is run when you submit it with ADO, you'll see that it's fluffed and rumpled just a little bit -- in order to make parameters work. That fluff-and-rumple mechanism can't deal with the same parameter name being bound again.

You can rewrite your query to be a batch that assigns @.NODE_ID to a variable, then reference the variable in the query. Or, you can create @.NODE_ID1 and @.NODE_ID2, and spread those guys around in the query -- then bind the same variable in the client code to the two different values (that is, add two parameters, each with the same value as the other).

|||Thanks for your reply,

Is it an issue only with SQL Mobile (aka Everywhere) or this will also

be present in SQL Express and Full-Featured SQL Server or even in any

ADO.NET provider?

> You can rewrite your query to be a batch that assigns @.NODE_ID to a variable, then reference the variable in the query.

SQL Mobile seems not to support batch queries (maybe executing multiply commands within the same connection will work, but it's a pretty mess. )

Anyway, I'm going just to substitue this parameter manually:
com.CommandText = com.CommandText.Replace("@.NODE_ID", "'"+guid.ToString()+"'");

<Select all> disappear on server

Hello.
I have a parameter with multi value option.
When I run the report in Visual studio, The first value in the drop
down of this parameter is (Select All).
When I check this option it check all the other values for this
parameter and when I unCheck this value it uncheck all the ther values
for this parameter.
The problem is thet when I'm publishing the report to the server and
then open it in IE the (Select All) value does't appear and I only get
all the other values.
Any body know how to fix this?
Thanks.On Nov 27, 11:08 pm, nicknack <roezo...@.gmail.com> wrote:
> Hello.
> I have a parameter with multi value option.
> When I run the report in Visual studio, The first value in the drop
> down of this parameter is (Select All).
> When I check this option it check all the other values for this
> parameter and when I unCheck this value it uncheck all the ther values
> for this parameter.
> The problem is thet when I'm publishing the report to the server and
> then open it in IE the (Select All) value does't appear and I only get
> all the other values.
> Any body know how to fix this?
> Thanks.
Hi
It might be a service pack issue, here's a link to Microsoft.
http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/WhatsNewSQL2005SP2.htm

<Select All>

Is there a way to default a multi-value parameter to "Select All"?
Also, can you test to see if the user clicked <Select All>? I want to
display the parameter on the report as the user selecting all.Have you figured it out - default display a multi-value parameter to "Select
All" yet?
"jtstrassburg@.gmail.com" wrote:
> Is there a way to default a multi-value parameter to "Select All"?
> Also, can you test to see if the user clicked <Select All>? I want to
> display the parameter on the report as the user selecting all.
>

<Select a Value> inconsistent

Hi, has anyone else seen this or know of why it's happening?
I have a report with a parameter Region. The region values are pulled
from a query:
select null as id, '' as name
union
select regionid, regionname from region
The Region parameter allows nulls and has a default value of null.
In the visual studio designer everything looks great. The dropdown
parameter is blank and my region values are there if I pull it down.
When I deploy the report to the server, the region parameter looks
different. It now defaults to <Select a Value>. The blank (null) line
exists but is not defaulted to on open of the report.
Another weird aspect of this is that I have a number of other reports
that "seem" to be set up exactly in this manner that work corrrectly
(i.e. The Region dropdown show up blank with valid regions in the
dropdown and no <select a value> option) in the designer and on the
server.
Thanks for your help,
BrettOn your report parameter have you set a non-queried default value of
=Nothing ?
HTH, Magendo_man
"Brett" wrote:
> Hi, has anyone else seen this or know of why it's happening?
> I have a report with a parameter Region. The region values are pulled
> from a query:
> select null as id, '' as name
> union
> select regionid, regionname from region
> The Region parameter allows nulls and has a default value of null.
> In the visual studio designer everything looks great. The dropdown
> parameter is blank and my region values are there if I pull it down.
> When I deploy the report to the server, the region parameter looks
> different. It now defaults to <Select a Value>. The blank (null) line
> exists but is not defaulted to on open of the report.
> Another weird aspect of this is that I have a number of other reports
> that "seem" to be set up exactly in this manner that work corrrectly
> (i.e. The Region dropdown show up blank with valid regions in the
> dropdown and no <select a value> option) in the designer and on the
> server.
> Thanks for your help,
> Brett
>|||Thanks magendo! That worked! I still don't understand why this
parameter acts differently than other parameters (or why setting the
default to NULL does not work), but at this point, I'm just happy it
works. Thanks a bunch.
Brett

<HTMLViewerStyleSheet> - where in config file?

I need to make use of the HTMLViewerStyleSheet parameter in SP2. I
have applied SP2 and the Hotfix, but still do not see
<HTMLViewerStyleSheet> in the RSReportServer.config file.
Am I looking in the wrong place? If not, can someone please tell me
exactly where and in what format the parameter needs to be?
Thanks
DaveForgot to mention this is for SQL 2000.
dacdev wrote:
> I need to make use of the HTMLViewerStyleSheet parameter in SP2. I
> have applied SP2 and the Hotfix, but still do not see
> <HTMLViewerStyleSheet> in the RSReportServer.config file.
> Am I looking in the wrong place? If not, can someone please tell me
> exactly where and in what format the parameter needs to be?
> Thanks
> Dave|||I added this before the final </Configuration> :
<HTMLViewerStyleSheet>MyStyleSheetName</HTMLViewerStyleSheet>
Needed to restart the ReportServer service. Works fine now.

& in report parameter

Hi,
Using URL parameters, I pass in the following department parameter "Sales & Marketing". The problem is the "&", this causing reporting services to display an error. I assume reporting services thinks it the parameter delimiter.
I have tried URL encloding the string before I pass it in but I still get an error.
Any ideas?
ThanksWhat is the error. Passing an & is fine, and yes it must be encoded on the
URL.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"MikeMcD" <MikeMcD@.discussions.microsoft.com> wrote in message
news:B84B6DAA-93FA-44CF-9CEC-C062E1DED325@.microsoft.com...
> Hi,
> Using URL parameters, I pass in the following department parameter "Sales
& Marketing". The problem is the "&", this causing reporting services to
display an error. I assume reporting services thinks it the parameter
delimiter.
> I have tried URL encloding the string before I pass it in but I still get
an error.
> Any ideas?
> Thanks|||Yes, we need to encode the & when we pass it in the URL.
just search ur string for an & and replace it with %26.
This should work fine.
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.

#&^%@#$ Report services...... OMG how do you set a report parameter in code....

Here's the error message..

Unable to cast object of type 'Microsoft.Reporting.WinForms.ReportParameter' to type 'System.Collections.Generic.IEnumerable`1[Microsoft.Reporting.WinForms.ReportParameter]'.

Here is the code

Dim rp = New Microsoft.Reporting.WinForms.ReportParameter

Me.RV1.ProcessingMode = Microsoft.Reporting.WinForms.ProcessingMode.Remote

Me.RV1.ServerReport.ReportServerUrl = New Uri("http://10.1.1.138/ReportServer/")

Me.RV1.ServerReport.ReportPath = "/test/rEmailInvoice"

rp.Name = "InvoiceNumber"

rp.Values.Add("0618050")

Me.RV1.ServerReport.SetParameters(rp) < get error message here.

Me.RV1.ShowParameterPrompts = False

Me.RV1.RefreshReport()

is it that hard to set a query parameter in code? I have looked through this newsgroup, looked through MSDN, read people's blogs and still can't find the answer. Why couldn't MS create a sample that uses reportparameters?

Has anyone done this in code. Will the world end tomorrow?

Help!?!

D

Hi Maniac,

ServerReport.SetParameters method is expecting a ReportParameters collection not a single ReportParameter

here is a sample:

ReportParameter[] reportParams = new [1];

reportParams[0] = new Microsoft.Reporting.WebForms.ReportParameter("InvoiceNumber", "0618050");

RV1.ServerReport.SetParameters(reportParams);

That's it!

|||

I tried your code..

Dim reportparams() As ReportParameter = New (1) <-- on the open paren I get a "Type expected" error

reportparams(0) = New Microsoft.Reporting.WinForms.ReportParameter("invoicenumber", "0618050")

Me.RV1.ServerReport.SetParameters(reportparams)

What am I missing?

|||

I'm not sure of the syntax in VB but I think the syntax to declare an array of 1 element is a bit different isn'it ?

something like Dim reportParams() As new ReportParameter(1) ?

Don't know exactly how to declare an array in VB but it should be something like that

|||

THANKS! for your help. I got it working..

Here's the code for anyone else who might have the this problem.

Dim reportparams(0) As ReportParameter

Me.RV1.ProcessingMode = Microsoft.Reporting.WinForms.ProcessingMode.Remote

Me.RV1.ServerReport.ReportServerUrl = New Uri("http://blah.blah.blah.blah/ReportServer/")

Me.RV1.ServerReport.ReportPath = "/test/remailinvoice"

reportparams(0) = New Microsoft.Reporting.WinForms.ReportParameter("InvoiceNumber", _Invoice)

'note: _Invoice is a public property

Me.RV1.ServerReport.SetParameters(reportparams)

Me.RV1.ShowParameterPrompts = False

Me.RV1.RefreshReport()

and it works!

Thanks for your help.