problem with cascading parameters after CTP2

In the standard report manager I'm running a report with 5 parameter choices. The first 3 are determinants of the 4th, and the combined 1-4 determine the 5th.

Although this works fine in my VS BIDS (sp1) with SQL 2005 sp2 CTP, when I deploy it to my sp2 CTP Report server, it throws an error as soon as I select the 3rd parameter.

One or more data sources is missing credentials

I found this answer from MS in another thread (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=923684&SiteID=1) and since it deals with my problem, wanted to pass it along to anyone else that is dealing with this problem.

" This is a known regression with CTP2 that will be fixed before SP2 is released. The problem is not specific to multivalue parameters. It has to do with dependencies between parameters.

In some cases, you can work around the issue if you give the dependent parameter a default value. You can also work around the issue by removing the valid values dependency between the parameters, though this may not be possible for a given report."

The suggested workaround does work! I can get beyond the 3rd parameter now because I applied a default value!

The workaround is useless. It only alleviated the problem when I stayed with that default value for my 3rd parameter. As soon as I changed it I'm right back to the 'one or more data sources is missing credentials'

SP2 cannot be soon enough...

|||

The workaround suggested can work, but it's tricky, especially with nested parameters that are dependent on each other. I finally got a six parameter functional again but with some pain. I made all the dependent parameter lists 'multi-select' and gave them a functional default value. Only then do they populate correctly.

And this all because I was hoping to use these reports in WSS 3.0 with the report server addin. Got very close and now have stumbled across similar bug with multiple parameters in Sharepoint. Will post entry to Sharepoint forums.

sql

Problem with BorderStyle while Exporting to PDF

Hi,
I have lines of BoderStyle: Dotted, BorderWidth: 0.5pt in my report
When I preview it and print it I get the dotted lines
But if I export the same report to PDF and then print I get Dashed lines
instead of Dotted Lines
It's very important that I get Dotted lines.
Can Someone Help me with this
Thanks in Advance
PonnurangamThis is a known issue that will be addressed in a future release.
Unfortunately I do not have a work around to suggest you.
Anyone else?
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:OL1Dft%23nEHA.744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have lines of BoderStyle: Dotted, BorderWidth: 0.5pt in my report
> When I preview it and print it I get the dotted lines
> But if I export the same report to PDF and then print I get Dashed lines
> instead of Dotted Lines
> It's very important that I get Dotted lines.
> Can Someone Help me with this
> Thanks in Advance
> Ponnurangam
>

Problem with Boolean Nullable parameter in Report Viewer

I have a problem with a nullable boolean parameter.
By default, the value is Null and that's working fine.

The User clicks either true or false, view the report: fine again.

However, from that point on, if the user checks the Null checkbox and
submits the reports, it reverts automatically back to the last True or
False value.

Is this a known problem? Or am I doing something wrong?

Eric

You aren't doing anything wrong. This is a bug. Unfortunately, there is no workaround. If this is causing you signficant problems, please contact customer support directly for a solution.

http://www.microsoft.com/services/microsoftservices/srv_support.mspx

|||

Thanks for the answer.

Is it reasonable to assume that this will get fixed in the next service pack, whenever this is?

|||I can't make any promises at this point (there are many factors involved), but I am pushing for it.|||Thanks

Problem with barcode in pdf export

I have a report that requires a barcode. I'm using a wasp128 barcode. The barcode works fine except when I export it to a pdf. It shows the barcode only it is spread out like somebody has slipped some spaces every couple of lines. Export to a image works fine and is scanable. Any thoughts?
--
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.What is the font you used when exporting?
=-Chris
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:u#KYFogtEHA.3292@.TK2MSFTNGP12.phx.gbl...
> I have a report that requires a barcode. I'm using a wasp128 barcode. The
barcode works fine except when I export it to a pdf. It shows the barcode
only it is spread out like somebody has slipped some spaces every couple of
lines. Export to a image works fine and is scanable. Any thoughts?
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

Problem with authentication prompting whilst fetching a report over the NET

Hi all,
I'm having a problem with accessing a report.
When I test it on my machine (2000 & reporting services installed on same
machine) there's no problem. As soon as I try to access it vie the internet
(I route through no-ip.org) then a window pops up wanting authentication. I
want to do away with this please.
How do I do this so no prompting occurs?
Regards
John.The authentication for a data source can be different for the dev env than
the production env... Go to the data source in the Prod env, and ensure
that something OTHER than prompt for credentials is set for the data
source...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John" <a@.b.c> wrote in message
news:%23iJ6eE7XFHA.2768@.tk2msftngp13.phx.gbl...
> Hi all,
> I'm having a problem with accessing a report.
> When I test it on my machine (2000 & reporting services installed on same
> machine) there's no problem. As soon as I try to access it vie the
> internet (I route through no-ip.org) then a window pops up wanting
> authentication. I want to do away with this please.
> How do I do this so no prompting occurs?
> Regards
> John.
>

Problem with assebly

I have problems with referensing assebly to my report. I copy my.dll to
\MSSQL\Reporting Services\ReportManager\bin
and
\MSSQL\Reporting Services\ReportServer\bin.
I have added the assembly to the report using the Referecnce tab poniting to \MSSQL\Reporting Services\ReportServer\bin but i still get error File or assembly name AssTest, or one of its dependencies, was not found.
In assebly i have simple function and it's static, i call method like this =Namespace.Class.Method.
Please, help.
AlešI did mistake in path to dll
Aleš
"AG, NLB d.d." wrote:
> I have problems with referensing assebly to my report. I copy my.dll to
> \MSSQL\Reporting Services\ReportManager\bin
> and
> \MSSQL\Reporting Services\ReportServer\bin.
> I have added the assembly to the report using the Referecnce tab poniting to \MSSQL\Reporting Services\ReportServer\bin but i still get error File or assembly name AssTest, or one of its dependencies, was not found.
> In assebly i have simple function and it's static, i call method like this =Namespace.Class.Method.
> Please, help.
> Aleš
>
>sql

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.] System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715 System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102 Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.] System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715 System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102 Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.]

System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715

System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102

Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149

Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

problem with 2005 xml datasource that is xml render of a 2000 report

Hi,
I'm trying to setup an xml datasource in ssrs 2005. The xml datasource is
an xml render from a ssrs 2000 report.
The connection string is a url which works fine when I put it into a
standalone browser (prompts me to save the xml output).
However when I try to then do a basic Query String for a dataset, I get an
error back from ssrs 2000
"The value provided for the report parameter 'EndDate' is not valid for its
type. (rsReportParameterTypeMismatch) "
My url is url encoded, and has the name value pair
"rs:ParameterLanguage=en-GB" defined
Any ideas on troubleshooting this?
Thanks
MartinTurns out I wasn't affecting the url when I thought I was.
"Martin" <x@.y.z> wrote in message
news:%23pgeok9OHHA.3268@.TK2MSFTNGP03.phx.gbl...
> Hi,
> I'm trying to setup an xml datasource in ssrs 2005. The xml datasource is
> an xml render from a ssrs 2000 report.
> The connection string is a url which works fine when I put it into a
> standalone browser (prompts me to save the xml output).
> However when I try to then do a basic Query String for a dataset, I get an
> error back from ssrs 2000
> "The value provided for the report parameter 'EndDate' is not valid for
> its type. (rsReportParameterTypeMismatch) "
> My url is url encoded, and has the name value pair
> "rs:ParameterLanguage=en-GB" defined
> Any ideas on troubleshooting this?
> Thanks
> Martin
>

Problem with 2 Dataset Sharing Parameters

I have a report that will pull out a list of bugs assigned to users for a
period of time (@.StartDate, @.EndDate). Optionally the report has option to
select a single user (@.UserName) or just all of them. There are 2 datasets.
First dataset: Bugs requires 3 parameters: @.StartDate, @.EndDate, @.UserName.
Second dataset: UserName. At first I have a query to list all users. Since
the list has hundreds of users while the result set from dataset Bugs mostly
has less than 10 users, I built another query to list only users having bugs
assigned from @.StartDate to @.EndDate. So it requires 2 parameters @.StartDate
and @.Enddate.
Now both datasets use @.StartDate and @.EndDate. The list to select for
@.UserName is produced after @.StartDate and @.EndDate are entered. I expected
the report to let me select the username after I enter @.StartDate and
@.EndDate. However in the preview tab right at the moment when I clicked on
the box for @.EndDate to enter a value the program hang up (VS 2003). I
uploaded it to a report server to see how it behaves then I got this error
after I click on the EndDate box: The value provided for the report
parameter 'EndDate' is not valid for its type.
(rsReportParameterTypeMismatch).
I don't know what's wrong. If I change the dataset UserName to list all
users (no parameter required) then the report runs fine. I use Visual
Studio .NET 2003 Service Pack 1, report server is SQL 2000 with latest SP on
the O/S, SQL, and SQL RS.
An thought?
Thanks.On May 2, 5:31 pm, "ME" <M...@.mail.com> wrote:
> I have a report that will pull out a list of bugs assigned to users for a
> period of time (@.StartDate, @.EndDate). Optionally the report has option to
> select a single user (@.UserName) or just all of them. There are 2 datasets.
> First dataset: Bugs requires 3 parameters: @.StartDate, @.EndDate, @.UserName.
> Second dataset: UserName. At first I have a query to list all users. Since
> the list has hundreds of users while the result set from dataset Bugs mostly
> has less than 10 users, I built another query to list only users having bugs
> assigned from @.StartDate to @.EndDate. So it requires 2 parameters @.StartDate
> and @.Enddate.
> Now both datasets use @.StartDate and @.EndDate. The list to select for
> @.UserName is produced after @.StartDate and @.EndDate are entered. I expected
> the report to let me select the username after I enter @.StartDate and
> @.EndDate. However in the preview tab right at the moment when I clicked on
> the box for @.EndDate to enter a value the program hang up (VS 2003). I
> uploaded it to a report server to see how it behaves then I got this error
> after I click on the EndDate box: The value provided for the report
> parameter 'EndDate' is not valid for its type.
> (rsReportParameterTypeMismatch).
> I don't know what's wrong. If I change the dataset UserName to list all
> users (no parameter required) then the report runs fine. I use Visual
> Studio .NET 2003 Service Pack 1, report server is SQL 2000 with latest SP on
> the O/S, SQL, and SQL RS.
> An thought?
> Thanks.
The issue sounds kind of strange. Maybe you should check to make sure
that you have the correct @.EndDate mapping as part of the UserName
dataset (via the Data tab -> Edit Selected Dataset button [...] ->
Parameters tab). Also, make sure that the stored procedure/query that
sources the UserName dataset is not expecting a different data type
for @.EndDate (for whatever reason). Sorry I could not be of greater
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks for the reply. I use datatime as data type for @.StartDate, @.EndDate
in both datasets. Double checked everything but still have no clue why.
When I learned and practiced SQL 2005 I had no problem doing similar thing.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1178160515.514988.169100@.e65g2000hsc.googlegroups.com...
> On May 2, 5:31 pm, "ME" <M...@.mail.com> wrote:
>> I have a report that will pull out a list of bugs assigned to users for a
>> period of time (@.StartDate, @.EndDate). Optionally the report has option
>> to
>> select a single user (@.UserName) or just all of them. There are 2
>> datasets.
>> First dataset: Bugs requires 3 parameters: @.StartDate, @.EndDate,
>> @.UserName.
>> Second dataset: UserName. At first I have a query to list all users.
>> Since
>> the list has hundreds of users while the result set from dataset Bugs
>> mostly
>> has less than 10 users, I built another query to list only users having
>> bugs
>> assigned from @.StartDate to @.EndDate. So it requires 2 parameters
>> @.StartDate
>> and @.Enddate.
>> Now both datasets use @.StartDate and @.EndDate. The list to select for
>> @.UserName is produced after @.StartDate and @.EndDate are entered. I
>> expected
>> the report to let me select the username after I enter @.StartDate and
>> @.EndDate. However in the preview tab right at the moment when I clicked
>> on
>> the box for @.EndDate to enter a value the program hang up (VS 2003). I
>> uploaded it to a report server to see how it behaves then I got this
>> error
>> after I click on the EndDate box: The value provided for the report
>> parameter 'EndDate' is not valid for its type.
>> (rsReportParameterTypeMismatch).
>> I don't know what's wrong. If I change the dataset UserName to list all
>> users (no parameter required) then the report runs fine. I use Visual
>> Studio .NET 2003 Service Pack 1, report server is SQL 2000 with latest SP
>> on
>> the O/S, SQL, and SQL RS.
>> An thought?
>> Thanks.
>
> The issue sounds kind of strange. Maybe you should check to make sure
> that you have the correct @.EndDate mapping as part of the UserName
> dataset (via the Data tab -> Edit Selected Dataset button [...] ->
> Parameters tab). Also, make sure that the stored procedure/query that
> sources the UserName dataset is not expecting a different data type
> for @.EndDate (for whatever reason). Sorry I could not be of greater
> assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>

Problem with &rc:toolbar=false parameter

I am having a problem turning the toolbar off in reports. When I add the
&rc:toolbar=false parameter to the URL, the report is displayed with two
vertical scroll bars. The inner scroll bar scrolls the report and the
external scroll bar scrolls down to what appears to be another report
containing the following:
"Reporting Services Error
----
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) Get Online Help
Cannot redirect after HTTP headers have been sent."
With &rc:toolbar=true or without the toolbar parameter, the report displays
fine with only one scroll bar. In this case the toolbar is shown and the
beginning of the URL changes from "http://web01/ReportServer" to
"http://web01/ReportServer/Pages/ReportViewer.aspx" followed by the
parameters.
Since the URL with ReportViewer.aspx displays the report correctly, I tried
to use it with the &rc:toolbar=true parameter but when the report is
displayed, the URL reverts to the one without ReportViewer.aspx and the two
scroll bars appear.
I am using RS2005 and displaying the report in a Windows application and if
the toolbar is shown, it wraps to two lines and consumes too much of the web
browser, so I would like to be able to turn the toolbar off but can't find a
way without getting the error.
Does anyone know how to turn the toolbar off or of anything in the report
that could be causing this behavior?
Thanks,
TomHi Tom,
Thank you for the post.
I have tested in my side, it works fine for me.
The report rendered in a whole html page.
Does this occured on all the report?
Here is a article about the Device information settings, you may try to
follow it to set up.
Reporting Services Device Information Settings
http://msdn2.microsoft.com/en-us/library/ms155397.aspx
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Wei Lu,
Most of our reports use groups with drill-down and those that do use
drill-down exhibit the problem with the toolbar being hidden. Did the
report you tested use drill-down?
The only option we have for setting toolbar=false is in the URL because when
we use a browser to show the reports, we want the toolbar but when the
report is displayed in the Windows app, we want the toolbar hidden.
Thanks,
Tom
"Wei Lu" <weilu@.online.microsoft.com> wrote in message
news:PCCj9tHWGHA.4620@.TK2MSFTNGXA01.phx.gbl...
> Hi Tom,
> Thank you for the post.
> I have tested in my side, it works fine for me.
> The report rendered in a whole html page.
> Does this occured on all the report?
> Here is a article about the Device information settings, you may try to
> follow it to set up.
> Reporting Services Device Information Settings
> http://msdn2.microsoft.com/en-us/library/ms155397.aspx
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Tom,
I also tested with drill down report. It works fine.
Would you please try to post your error log here? By default, the error log
files are located at \Microsoft SQL Server\<SQL Server Instance>\Reporting
Services\LogFiles
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Problem with <Select a value> in report parameters

Hello, Everyone

please, could you make clear how can I avoid appearence of <select a value> in drop downs at all.

thanks

not sure if this will work, but could you set a default value of a zero length string or null value?|||

steveareno wrote:

not sure if this will work, but could you set a default value of a zero length string or null value?

It will definately work if you automatically select the first (or any) item in the list.

sluggy

|||

but doesn't work =)

I have a next drop down with predefined values:

Show all = -2
Local = 0
Another one = -1

I make default value = -2
and when I open report via browser I get this drop down with prepopulated values and currently chosen is Show all

BUT also I can choose <select a value>

P.S. I afraid that I should write custom code for UI of Reporting Services

Thanks, lads

Problem while using stored procedures with temporary tables in dataset

I am trying to generate a report using SQL Server Reporting Service. The dataset is passed the results from a stored procedure. The stored proc contains a temporary table. On exceuting of proc, it fetches the result but when I try to save dataset I get following error message

Invalid object name '#AdditionalParams'. (.Net SqlClient Data Provider)

And no colums are returned in the data set created.

Any help on this would be appreciated.

Thanks in advance

If possible, try using a table variable instead, or create a physical table first.

http://www.odetocode.com/Articles/365.aspx

Here are some workarounds for temp tables.

http://www.sql-server-performance.com/rd_temp_tables.asp

If you have to, try using set fmtonly off in stored procedure.

http://www.simple-talk.com/sql/database-administration/creating-csv-files-using-bcp-and-stored-procedures/

cheers,

Andrew

|||

I exceuted the proc as stored procedure. And latter I added a new field to same dataset, as it didnt had any field because it had thrown error. I refreshed the datset and I got all the dataset fields although initally it showed error and it worked.

But their is essentially problem the way datset are handled in reporting service.

Thanks

Problem while using stored procedures with temporary tables in dataset

I am trying to generate a report using SQL Server Reporting Service. The dataset is passed the results from a stored procedure. The stored proc contains a temporary table. On exceuting of proc, it fetches the result but when I try to save dataset I get following error message

Invalid object name '#AdditionalParams'. (.Net SqlClient Data Provider)

And no colums are returned in the data set created.

Any help on this would be appreciated.

Thanks in advance

If possible, try using a table variable instead, or create a physical table first.

http://www.odetocode.com/Articles/365.aspx

Here are some workarounds for temp tables.

http://www.sql-server-performance.com/rd_temp_tables.asp

If you have to, try using set fmtonly off in stored procedure.

http://www.simple-talk.com/sql/database-administration/creating-csv-files-using-bcp-and-stored-procedures/

cheers,

Andrew

|||

I exceuted the proc as stored procedure. And latter I added a new field to same dataset, as it didnt had any field because it had thrown error. I refreshed the datset and I got all the dataset fields although initally it showed error and it worked.

But their is essentially problem the way datset are handled in reporting service.

Thanks

Problem while navigating Report on server

Deploying to http://localhost/ReportServer

Deploying data source '/Report Project1/cnt_SDS_REQUEST'.

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file.

Are you reusing an existing report server database?

You get this error when the report server does not have access to the symmetric key that we use to protect sensitive data in the report server.

After a default installation, you should have access. If you chose to "install but not configure", then sometimes you need to manually restart the report server windows service for the initialization to occur.

If you are reusing an existing report server database, or are deploying in a scale-out configuration, you want to do use the report server configuration tool to initialize the report server. To do this, connect to a report server that is already initialized, go to the Initialization pane of the reporting services configuration tool, select the non-initialized instance, and press Initialize.

If you are reusing an exisitng report server database, but do not have another report server that is already initialized (it was uninstalled, you're restoring from backup, etc.), you will need to use the backup of your symmetric key (restore on the the Encryption Keys tab in the reporting servcies configuration tool).

If you don't have backed up symmetric key you'll need to delete encrypted content. Then you your report server should initialize itself after you restart your rpeort server windows service.

Hope that's simple enough :-).

-Lukasz|||I have just installed the lastest version of "Microsoft SQL Server 2005 CTP" and anytime I try to reach the ReportServer website, I get the following error message:

Reporting Services Error

---

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help|||Solution to this problem is

1) Open Configure Report Server Tool
2) Update 'Web Service Identity' tab to reflect Asp .Net account on the machine.
For Eg. machineName\ASPNET
3) Click Apply Button, This will update WebServiceAccount tag in your report server configuration file 'rsreportserver.config'.

Hope this helps.

Thanks,|||how do you delete it by command line? Do you type it at the "run" line?|||

There is no command line for this functionality. We provide a WMI interface you can call directly to perform the same actions as are undertaken by the configuraiton tool. You can find the reference to the WMI methods here:

http://msdn2.microsoft.com/en-us/library/ms152836(en-US,SQL.90).aspx

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

When I try to update the Web Service Identity field, it is greyed out and does not allow updates. Currently set to "NT Authority\Network Service"

|||

I am in the same situation as well. I'm not allowed to change the WebServiceAccount through the interface, it's disabled. Also when I change it manually through the rsreportserver.config file to something other than it's current setting, the "Web Service Identity" won't initialize until I change it back to 'NT Authority\NetworkService'. I've removed the Encryption Keys even though there shouldn't be any yet as it's a fresh install of Reporting Services.

When I attempt to deploy a Report to the Report Server, I get the following error:

"The Report Server Web Service is unable to access information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file."

What are the next several items we should check?

|||

Hi,

What OS are you on?

If you're using RS on windows XP the identity that the Report server web service runs as is the identity of ASP.Net as set in ProcessModel element in the machine.config file. If you change it there, you should be able to click the apply button in the configuration tool. (This also applies to Windows 2000 Server)

If you're on Windows Windows Server 2003, you can create a new application pool with the new identity you want. Use the "New..." button on the web service identity tab to create it.

The WebServiceAccount property in the rsreportserver.config file does not actually set the web service to run as that account. Rather it needs to contain the name of the account the web service is configured to run as, if this identity is different from ASP.Net machine account on XP, W2K, or Network Service on W2K3.

Hope that helps,

-Lukasz

|||I found the issue(s) First off, there were 2 application pools created by our Network Admin that were both configured for the same virtual Directory. This was causing me issues with the deploying issue. Second, They were both configured for either LocalSystem or NetworkService which would always tell me that I didn't have access to execute them. Once I stopped one of the 2 application pools and ensured that the Web service Identity matched the application pools security that was still running, then I could both deploy and execute. Thanks for the direction.|||

Hi - I am still having issues deploying.

WinXP

SQL2005

IIS5

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help

Issues with both reportserver and reportmanager.

Any ideas?

thanks.

vani

|||

This is a different issue:

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData

This error means the web service account as specified in the (for Windows XP or Windows 2000) Machine.config file in the <ProcessModel> element is not the same as the account specified in the <WebServiceAccount> element in the rsreportserver.config file. If the account specified by the <ProcessModel> is the ASP.NET account, then the value of <WebServiceAccount> can be blank. If it is something else, then you can either use the reporting services configuration tool to set the web service identity, or you can manually edit the <WebServiceAccount> element in the rsreportserver.config file. The account name must be in domain\alias format.

Just for completeness, on Windows Server 2003 and Vista, the web service identity depends on the application pool identity that is configured for the report server virtual directory. The default application pool identity is Network Service. In this case the <WebServiceAccount> element can be blank. If the application pool identity is another account, you'll need to ensure the WebServiceAccount element is set to that identity.

Hope that helps,

-Lukasz

|||

I have changed this in reportserver's rsreportserver file to reflect

<WebServiceAccount><machine_name>\ASPNET</WebServiceAccount>

another confusing part - looks like we cannot use localhost but rather need to use the computer_name to run reports?

Also - being new to 2.0 framework - for some reason it seems to be adding the port number to run file like -http://localhost:2794/ReportServer/Pages/ReportViewer.aspx

Thanks.

Vani

|||

The port number is determined by the website you chose in IIS. If you're not using the default web site, or have customized it to run on a different port, you need to specify the port explicitly.

-Lukasz

|||

Dear Lukasz,

your post was very helpfull, but I've a very strange bug. If I try to open a report all work fine. But if I click on a record (that should open a new sub-report) I've this: Not sufficient rights for the NT Authority\NetworkService account to complete this operation

If I try to do the same thing using then Report Builder all work fine.

What about?

Thanks in advance

Problem while exporting in MAPI

Hi,

I am using crystal report v8.5.
I click on the export icon & select Acrobat Format (PDF) as Format and MAPI as Destination.
But nothing appeared and i couldn't export report whereas i can succesfully save the same report when select Acrobat Format (PDF) as Format and "disk file" as Destination.
Please help me out?

Thanks,
JasIs this on you development machine or the Client machine? Did you make sure you had the correct MAPI dll installed on the computer?|||this is on my developing m/c. i use outlook express for mailing purpose, which works fine. how to check whether correct mapi dll is intalled?

thanks

jas|||I also use CR 8.5. On my computer (Win2k), all the Export dlls are located in C:\WINNT\Crystal. The MAPI one has the name u2dmapi.dll. If you can't find the right dll, maybe it wasn't installed when you installed Crystal Reports. You may be able to reinstall it or pull the dll from the installation CD.|||i use win xp professional, u2dmapi.dll is present in my C:\WINDOWS\Crystal folder but still i couldn't mail. when i click "ok" after selecting format as Acrobat and destination as MAPI, one window appeared titled as "Export options" which allows to enter page range. But after that nothing happened.|||Do you have Outlook or something setup on your computer? I'm not familiar with MAPI, but while researching one of my exporting problems, I read a post where someone was having trouble exporting with MAPI and it was because Outlook wasn't set up with a user profile.|||yaa, i m using outlook express to send n receive mails and it is working perfectly.|||Outlook express is not connected through MAPI, while Microsoft Outlook uses MAPI, to configure a profile follow these steps

1. Open Mail Control Panel
2. Configure Message Store and Internet mail account
3. then use Microsoft Outlook to send & receive mail, if it works then ur Export will also work.|||Thanx for ur help. I m off from work for 2-3 weeks, got chicken pox :( , will try later.
Thanks again
Jas|||Get well soon

Problem while exporting in MAPI

Hello everyone,

I m repeating my problem.
I am using crystal report v8.5.
After running report successfully, when I click on the export icon & select "Acrobat Format (PDF)" as Format and "MAPI" as Destination, dialog box appeared which ask for page range selection. But after that nothing appeared and i couldn't export report.
I m using "outlook express" for mailing which is configured properly.
Please help me out?

Thanks,
Jasafter setting outllook express as default mapi client this problem gets resolved

Problem while export report to Excel

When i export a report to Excel, there are created some coluns and line
that not appear in the report.
These lines and coluns are smaller than the normal ones, but if i need to
work with this file, a must have to delete each one.
And athis operation is not easy.
Thanks by your help.
Pedro Julião
Belo Horizonte - Brasil
--
Message posted via http://www.sqlmonster.comI have run into the same problem. I am just building Excel Macros to delete
the columns.
"Pedro Julião Moura Machado Coelho via S" wrote:
> When i export a report to Excel, there are created some coluns and line
> that not appear in the report.
> These lines and coluns are smaller than the normal ones, but if i need to
> work with this file, a must have to delete each one.
> And athis operation is not easy.
> Thanks by your help.
> Pedro Julião
> Belo Horizonte - Brasil
> --
> Message posted via http://www.sqlmonster.com
>|||Dear Eden,
Thanks by your help.
Can you send me some examples of this macros?
Best regards,
Pedro Julião
--
Message posted via http://www.sqlmonster.com

Problem while deploying Report on server

Deploying to http://localhost/ReportServer

Deploying data source '/Report Project1/cnt_SDS_REQUEST'.

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file.

Are you reusing an existing report server database?

You get this error when the report server does not have access to the symmetric key that we use to protect sensitive data in the report server.

After a default installation, you should have access. If you chose to "install but not configure", then sometimes you need to manually restart the report server windows service for the initialization to occur.

If you are reusing an existing report server database, or are deploying in a scale-out configuration, you want to do use the report server configuration tool to initialize the report server. To do this, connect to a report server that is already initialized, go to the Initialization pane of the reporting services configuration tool, select the non-initialized instance, and press Initialize.

If you are reusing an exisitng report server database, but do not have another report server that is already initialized (it was uninstalled, you're restoring from backup, etc.), you will need to use the backup of your symmetric key (restore on the the Encryption Keys tab in the reporting servcies configuration tool).

If you don't have backed up symmetric key you'll need to delete encrypted content. Then you your report server should initialize itself after you restart your rpeort server windows service.

Hope that's simple enough :-).

-Lukasz|||I have just installed the lastest version of "Microsoft SQL Server 2005 CTP" and anytime I try to reach the ReportServer website, I get the following error message:

Reporting Services Error

---

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help|||Solution to this problem is

1) Open Configure Report Server Tool
2) Update 'Web Service Identity' tab to reflect Asp .Net account on the machine.
For Eg. machineName\ASPNET
3) Click Apply Button, This will update WebServiceAccount tag in your report server configuration file 'rsreportserver.config'.

Hope this helps.

Thanks,|||how do you delete it by command line? Do you type it at the "run" line?|||

There is no command line for this functionality. We provide a WMI interface you can call directly to perform the same actions as are undertaken by the configuraiton tool. You can find the reference to the WMI methods here:

http://msdn2.microsoft.com/en-us/library/ms152836(en-US,SQL.90).aspx

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

When I try to update the Web Service Identity field, it is greyed out and does not allow updates. Currently set to "NT Authority\Network Service"

|||

I am in the same situation as well. I'm not allowed to change the WebServiceAccount through the interface, it's disabled. Also when I change it manually through the rsreportserver.config file to something other than it's current setting, the "Web Service Identity" won't initialize until I change it back to 'NT Authority\NetworkService'. I've removed the Encryption Keys even though there shouldn't be any yet as it's a fresh install of Reporting Services.

When I attempt to deploy a Report to the Report Server, I get the following error:

"The Report Server Web Service is unable to access information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file."

What are the next several items we should check?

|||

Hi,

What OS are you on?

If you're using RS on windows XP the identity that the Report server web service runs as is the identity of ASP.Net as set in ProcessModel element in the machine.config file. If you change it there, you should be able to click the apply button in the configuration tool. (This also applies to Windows 2000 Server)

If you're on Windows Windows Server 2003, you can create a new application pool with the new identity you want. Use the "New..." button on the web service identity tab to create it.

The WebServiceAccount property in the rsreportserver.config file does not actually set the web service to run as that account. Rather it needs to contain the name of the account the web service is configured to run as, if this identity is different from ASP.Net machine account on XP, W2K, or Network Service on W2K3.

Hope that helps,

-Lukasz

|||I found the issue(s) First off, there were 2 application pools created by our Network Admin that were both configured for the same virtual Directory. This was causing me issues with the deploying issue. Second, They were both configured for either LocalSystem or NetworkService which would always tell me that I didn't have access to execute them. Once I stopped one of the 2 application pools and ensured that the Web service Identity matched the application pools security that was still running, then I could both deploy and execute. Thanks for the direction.|||

Hi - I am still having issues deploying.

WinXP

SQL2005

IIS5

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData) Get Online Help

Issues with both reportserver and reportmanager.

Any ideas?

thanks.

vani

|||

This is a different issue:

The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount is specified correctly in the report server config file. (rsAccessDeniedToSecureData

This error means the web service account as specified in the (for Windows XP or Windows 2000) Machine.config file in the <ProcessModel> element is not the same as the account specified in the <WebServiceAccount> element in the rsreportserver.config file. If the account specified by the <ProcessModel> is the ASP.NET account, then the value of <WebServiceAccount> can be blank. If it is something else, then you can either use the reporting services configuration tool to set the web service identity, or you can manually edit the <WebServiceAccount> element in the rsreportserver.config file. The account name must be in domain\alias format.

Just for completeness, on Windows Server 2003 and Vista, the web service identity depends on the application pool identity that is configured for the report server virtual directory. The default application pool identity is Network Service. In this case the <WebServiceAccount> element can be blank. If the application pool identity is another account, you'll need to ensure the WebServiceAccount element is set to that identity.

Hope that helps,

-Lukasz

|||

I have changed this in reportserver's rsreportserver file to reflect

<WebServiceAccount><machine_name>\ASPNET</WebServiceAccount>

another confusing part - looks like we cannot use localhost but rather need to use the computer_name to run reports?

Also - being new to 2.0 framework - for some reason it seems to be adding the port number to run file like -http://localhost:2794/ReportServer/Pages/ReportViewer.aspx

Thanks.

Vani

|||

The port number is determined by the website you chose in IIS. If you're not using the default web site, or have customized it to run on a different port, you need to specify the port explicitly.

-Lukasz

|||

Dear Lukasz,

your post was very helpfull, but I've a very strange bug. If I try to open a report all work fine. But if I click on a record (that should open a new sub-report) I've this: Not sufficient rights for the NT Authority\NetworkService account to complete this operation

If I try to do the same thing using then Report Builder all work fine.

What about?

Thanks in advance