reportbuilder clickonce

Hello!
Does anyone know which permissions our users will need in order to let
reportbuilder install from the SSRS homepage?
I have read that the clickonce process should make this smooth, BUT when we
try this, the reportbuilder does not install unless "local
administrator"-permissions are assigned to the users. According to the log,
the deployment process is trying to write to the registry - and this is
probably what makes the app require admin-permissions.
Strange - since Ive read an MS-article stating that the users should not
need these permissions.
Anyone has any comments ?
DavidOn Feb 22, 8:49=A0am, "David"
<david_sundstrom_sandegard.nos...@.hotmail.com> wrote:
> Hello!
> Does anyone know which permissions our users will need in order to let
> reportbuilder install from the SSRS homepage?
> I have read that the clickonce process should make this smooth, BUT when w=e
> try this, the reportbuilder does not install unless "local
> administrator"-permissions are assigned to the users. According to the log=,
> the deployment process is trying to write to the registry - and this is
> probably what makes the app require admin-permissions.
> Strange - since Ive read an MS-article stating that the users should not
> need these permissions.
> Anyone has any comments ?
> David
David,
What I did was go into Site Settings and create a new System Role
called ReportBuilderUser with just the Execute Report Definition task
assigned. After that it was just a case of assigning that role to the
individuals or groups that need to see the Report Builder button in
Report Manager.
Don't feel bad about needing help on this. Unless it's changed, the
MS documentation for this is not clear.
HTH
toolman|||Hi toolMan, thx for answering!
Thing is that in order for ReportBuilder application to install, the user
seem to need some permissions on their LOCAL computer (not the server
site-wide settings-stuff).
The ReportBuilder app seems to write to some registry-keys and in order to
do this, the users seems to need to be local adminstrators of their
machines.
Does anyone recognize this?
"toolman" <timd@.infocision.com> wrote in message
news:d7250e41-06f3-45e4-bf04-fa4e1ccf0330@.41g2000hsc.googlegroups.com...
On Feb 22, 8:49 am, "David"
<david_sundstrom_sandegard.nos...@.hotmail.com> wrote:
> Hello!
> Does anyone know which permissions our users will need in order to let
> reportbuilder install from the SSRS homepage?
> I have read that the clickonce process should make this smooth, BUT when
> we
> try this, the reportbuilder does not install unless "local
> administrator"-permissions are assigned to the users. According to the
> log,
> the deployment process is trying to write to the registry - and this is
> probably what makes the app require admin-permissions.
> Strange - since Ive read an MS-article stating that the users should not
> need these permissions.
> Anyone has any comments ?
> David
David,
What I did was go into Site Settings and create a new System Role
called ReportBuilderUser with just the Execute Report Definition task
assigned. After that it was just a case of assigning that role to the
individuals or groups that need to see the Report Builder button in
Report Manager.
Don't feel bad about needing help on this. Unless it's changed, the
MS documentation for this is not clear.
HTH
toolman

Report Viewer web part in Sharepoint 2.0 site

Hello:
I'm running the SSRS 2005 web parts in a Sharepoint 2.0 site. I want
to display a report when a page loads using just the page viewer web
part.
In the properties of the web part, I have http://portal:81/Reports/Pages/Report.aspx?
in the Report Manager URL field and itempath=%2fRepVendorPortal%2fTop
+Sellers in the Report Path field.
When I hit apply, the web part displays "A required argument is
missing from the URL that opens this page: ItemPath".
What am I doing wrong here?
Any assistance is appreciated.
Thanks in advance.
-JoeNever mind. I had the report server URL incorrect (it should have
been just http://portal:81/reports) and the report path should have
just been /repvendorportal/Top Sellers. The + was causing a problem
too.
Thanks.
-Joe
On Nov 8, 1:14 pm, Joe <j...@.josephmarkovich.com> wrote:
> Hello:
> I'm running the SSRS 2005 web parts in a Sharepoint 2.0 site. I want
> to display a report when a page loads using just the page viewer web
> part.
> In the properties of the web part, I havehttp://portal:81/Reports/Pages/Report.aspx?
> in the Report Manager URL field and itempath=%2fRepVendorPortal%2fTop
> +Sellers in the Report Path field.
> When I hit apply, the web part displays "A required argument is
> missing from the URL that opens this page: ItemPath".
> What am I doing wrong here?
> Any assistance is appreciated.
> Thanks in advance.
> -Joe

Report Viewer Control to display reports

I have reports designed and deployed at the report server running Sql 2005
SSRS. I want to display those report in a vb.net Windows application using a
report viewer control and I have searched the internet for the past 2 weeks
and I still can not find anything or samples on how to do this. I wonder if
it is doable. Thanks.Paul,
You should find the report viewer reference at
http://msdn2.microsoft.com/en-us/library/microsoft.reporting.winforms(vs.80).aspx .
However, if you want just to show a predefined report for the end users,
Visual Studio offers the basic settings for the control, such as Report
server and report name. It is not a big magic :)
I got this sample, hope it will help for you.
http://www.devx.com/dotnet/Article/30424
Regards,
Janos
"Paul" <paul_mak@.shaw.ca> wrote in message
news:O2CwgFviHHA.5052@.TK2MSFTNGP05.phx.gbl...
>I have reports designed and deployed at the report server running Sql 2005
>SSRS. I want to display those report in a vb.net Windows application using
>a report viewer control and I have searched the internet for the past 2
>weeks and I still can not find anything or samples on how to do this. I
>wonder if it is doable. Thanks.
>|||Some great samples at http://www.gotreportviewer.com
--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@.(NOSPAM)lakeclaireenterprises.com
"Paul" <paul_mak@.shaw.ca> wrote in message
news:O2CwgFviHHA.5052@.TK2MSFTNGP05.phx.gbl...
>I have reports designed and deployed at the report server running Sql 2005
>SSRS. I want to display those report in a vb.net Windows application using
>a report viewer control and I have searched the internet for the past 2
>weeks and I still can not find anything or samples on how to do this. I
>wonder if it is doable. Thanks.
>

Report Throttling and Asynch Processing

My enterprise is looking into migrating to SSRS 2005 and I am trying to gather as much information as possible. One area that I've been unable to find much information is around the area of process (or report request) throttling inherent to SSRS. We are a large organization and the reporting technology that we choose must be able to process thousands of report requests a day. In our current solution, we have the ability to throttle the report requests so that a limit is placed on the number of report request that can be processed concurrently so that the reporting infrastructure is not overwhelmed during peak load times. Subsequent request are queued for processing at a period when there is less load on the servers. Does SSRS have this capability and is it configurable? Is there any detailed information (articles, whitepapers, books) available addressing this subject?

This leads me to a second question concerning an asynchronous reporting solution. Has anyone developed a solution using SSRS that allows long running reports ( that are requested online) to be processed on a background thread and has the background thread alert the user when the report has completed? This is a nice feature of our current solution but I have not been able to find a comparable solution utilizing SSRS.There looks like there might be possibility in the Subscription capabilities but I’m not sure how this would work online requested reports.

Any help would be appreciated. Thanks!!

You can have users subscribe to reports so they are processed and pushed out during down time - either to email, or say to an ftp server. If you want a queuing feature for on demand though, you would have to front-end that. And you would need a mechanism to determine long running reports.

You can scale the infrastructure of RS and setup farms. Throttling though..not likely.

Yes, in your second question...have the user setup a subscription to the report. Then either email as an attachment or send as a link so they can retrieve it. Again, you might want to front end this on an ASP page so the user makes their report selections and then a few lines of code creates the subscription for them...providing the appearance of a request queue.

|||Thanks David.

I will definitely research these options. On the surface, I don't think that attaching the reports to emails is a valid option for us because of the size of the files. In the situations where you include a link to the report, how is this being secured? Is the link to the Report Manager site with URL access? Or is the report output saved to a share with the link taking the user to a share? If it is persisted to a share, how are these files secured? How are the user and calling application notified of a failure?

Looks like a combination of subscription and custom delivery extension might be the answer.

Thanks for the help and sorry about all the questions.

|||

David,

In the case of Scheduling, does it do any throttling in that case? What if I schedule 200 reports for the same time? Will it run all 200 at once or will it be smart about it and do something to prevent this from hurting the performance of the entire system?

Mark

|||

swfranklin wrote:

Thanks David.

I will definitely research these options. On the surface, I don't think that attaching the reports to emails is a valid option for us because of the size of the files. In the situations where you include a link to the report, how is this being secured? Is the link to the Report Manager site with URL access? Or is the report output saved to a share with the link taking the user to a share? If it is persisted to a share, how are these files secured? How are the user and calling application notified of a failure?

Looks like a combination of subscription and custom delivery extension might be the answer.

Thanks for the help and sorry about all the questions.

You have a choice in output. You can send to a file share and manage the security on your own using Windows/AD / ftp folder...etc.
Or you can supply a link to the report in the email..in which case you'd be setting up security on the Report Server and the user gets authenticated when they click the link.

By failure..it depends upon what you mean. This would be report creation, not batch programming. Errors I have seen are email (address or server not being set up correctly)..in that case, no mail. Something like your dataset becomes unavailable? Other than that there really isn't much to subscriptions. A report is set to generate at 9AM and if I don't receive it in a timely manner I contact someone..If your report is first dependent upon say, a cube processing after a long ETL to a datawarehouse and that bombed...you would have to build some custom mechanism to alert your users. That would be outside of the scope of SSRS.

sql

Report Server Setup when query against terabytes of data

Hi all,

Can anyone point me to a resource on the best way to setup and use SSRS 2005 when reporting on tables that could have 1 billion rows. The database in question will have mulitple schema's each being at least 1 terabyte in size.

Thanks

-JW

The size of the database matters much less than the size of the data you want in the report. My advice is to push as much filtering and sorting logic as you can into the back end database and return only the result set you want to display into SSRS 2005. Assuming you filter the data down to 20-100 page reports, going against billions of rows and terabytes of data is not difficult.

Thanks.

Donovan Smith

|||

Thanks Donovan

report server service stopping unexpectedly

we run ssrs 2005 sp2 hotfix applied - how do we troubleshoot a problem where the report server service is stopping unexpectedly several times a day. When this happens please tell me what happens to the reports that are currently running. I believe that

1) a current subscription that is running will fail - not sure if it will try to restart itself 3 times or not

2) connection to the report server db cannot be made when that occurs

this is a huge problem for us and we dont know what is causing it or how to fix it. Any suggestions would help. I can tell you that our customers flood the server with subscriptions

Hi,

You can find detailed informaion about the SSRS service in the log files at this location:

<drive:>\Program Files\Microsoft SQL Server\MSSQL.<n>\Reporting Services\LogFiles\

It should help to identify the problem.

Regards,

Janos

|||

thanks - but I am already aware of the log files at that location and looking in them is not telling me the reason why the service is stopping unexpectedly. There isnt anything in the log file that I can see which would indicate that behavior.

Please ... if there is something I am missing that you are aware of ... a particular type of error that would cause the service to stop then let I would like to know about it. Thank you.

Report Server Not Responding

Hi ..
I installed SSRS on W2K Server machine also running SQL Server 2005; after
the install completion I keep getting the following message:
"The report server is not responding. Verify that the report server is
running and can be accessed from this computer"
when I type http://<serverName>/ReportManager into the Address box in IE 6
if I type http://<serverName>/ReportServer in I get the following:
"Reporting Services Error
An internal error occurred on the report server. See the error log for more
details. (rsInternalError)
For more information about this error navigate to the report server on the
local server machine, or enable remote errors"
All other virtual directories on the web server are working ok; one thing I
notice is that it looks like the configuration was set up to access SQL
Server Express in a connection string named "LocalSqlServer" ... I don't
have SQL Server Express installed on the machine .. and there is a
connection string pointing to an MDF file that I don't see anywhere; I
changed the connection string to point to my the SQL2005 instance but it
really seems kind of stupid and useless to do that since I don't know what
database ReportServer and ReportManager want to use ...
Right now, I'm baffled with this thing; it looks like it probably works
fine if you happen to have just the right original configuration anticipated
by the team that designed the installers ... otherwise, you have a headache
...
so if anyone has some suggestions or info links I'd really appreciate it
...
TIAHi,
I am also working on the installing reporting Services , getting a different
error .
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
did you replace <servername> with localhost ?|||"Reshma" <Reshma@.discussions.microsoft.com> wrote in message
news:3DBD066C-F341-4AE9-9FF3-70AA30621E77@.microsoft.com...
> Hi,
> I am also working on the installing reporting Services , getting a
> different
> error .
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> did you replace <servername> with localhost ?
replace it where? I've used it in the IE address box ... doesn't work with
<localhost> OR <serverName> ...
all I'm getting is, "The report server is not responding. Verify that the
report server is running and can be accessed from this computer" ... well,
I'm trying to "verify" and this is the answer ... kind of stuck in a loop
here ...
The underlying Windows Service IS running, at least according to Service
Manager ... but that's not helping ...