SSRS asking for credentials while reports running for long time.

Posted By:Posted Date:April 10, 2011Points:0Category :

We have a report which executes a stored procedure and it runs for 10 minutes. After running for 5 minutes, the report keeps asking for username and password for 3 times and redirects to unauthorized page. The website uses WIDE IP for crash and
recovery handling, so it has two nodes. Could some one please help me to figure out what problem it is ? The SP data is not huge, which produces only 300 odd rows and 20+ columns.

I have an MDX query which runs fine in the MDX Sample Application. It runs against an SSAS 2000 cube. In my query there is a recursion kind of a logic. It takes about 1-2 sec to run in the MDX Sample Application. My sample application is in the same server
as my AS 2000 cube is. However when I run the same MDX from another server through BIDS (2008) it takes an unusually long amount of time to run. Most of the time it times out. :(

As a workaround I created 4 calculated members in my Cube itself (Initially these were used as members in my MDX). I thought that maybe the recursion logic is the culprit so I modified my MDX, removed the recursion part. But still from my SSRS it is taking
a long time.

Firstly, I implemented a background worker process to handling looping through the 2,800 reports. I found to run the SSRS report viewer to export the report results in a slow memory leak. See Red-gate Ants memory profiler 6 image in the link above. I'm not
sure what I need to do to remove weak references with this combination of technology. Any ideas?

Secondly, the following code runs on the background worker process, designed so the user can monitor the progress of the a large batch of report files getting generated. The catch here is involves using the SSRS viewer to export a reports results requires
the Dispatcher.Invoke method to ensure that ReportViewer.xaml screen gets a UI thread, but in the process it interferes with the background workers report progress methods, so the UI doesn't see the progress.

Firstly, I implemented a background worker process to handling looping through the 2,800 reports. I found to run the SSRS report viewer to export the report results in a slow memory leak. See Red-gate Ants memory profiler 6 image in the link above. I'm not
sure what I need to do to remove weak references with this combination of technology. Any ideas?

Secondly, the following code runs on the background worker process, designed so the user can monitor the progress of the a large batch of report files getting generated. The catch here is involves using the SSRS viewer to export a reports results requires
the Dispatcher.Invoke method to ensure that ReportViewer.xaml screen gets a UI thread, but in the process it interferes with the background workers report progress methods, so the UI doesn't see the progress.

We have developed a SharePoint- FBA site and published it through ISA. The site, among many features, displays SSRS reports through Performance Point Monitoring dashboards. SSRS is using windows integrated authentication (Kerberos). Through intranet, the reports are getting displayed without any issue, but, through internet, its getting prompted when we try to access the reports for the first time after logging into the site using FBA credentials. When we enter valid domain credentials after being prompted, it starts displaying reports without any issues and never prompts again for that FBA session.

We have been trying to eliminate the prompt through internet, but couldn't do so.

First of all, thanks for the good information that usually all of us can find here to solve our problems with SQL.

Now I'm going to try to explain my problem. Following some of the Q&A published here, I have installed a SSRS Scale-Out environment with 2 SSRS Web instances and an external SSRS DB repository. After that, I have published some rdl files without
any kind of problems.

I am unable to schedule report am getting following error when trying to schedule an SSRS report from ReportViewer Webpart in SharePoint 2010.

The current action cannot be completed. The user data source credentials do not meet the requirements to run this report. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to
require credentials but the unattended execution account is not specified. (rsInvalidDataSourceCredentialSetting)

I wanted to know how to prevent more than one user from
uploading the report at a time .I am new to .net ,plss help with the
code that would be great.Details are below:

This is a Windos based
app written in c# . When User A clicks Upload option on one server
from the menu to upload the files and at the same time when User B
clicks Upload option on different server , User B should be alerted a
message saying "User A's uploading is in progress,pls wait" . How to
achieve this, plsss help with the code..I am thinking this logic should be kept in a stored proc, How do I write that proc? plss help

Our client has a SharePoint (moss2007) site on Windows 2008, SQL2008 R2 Enterprise, and Reporting service is integrated with SharePoint

The authentication on the share point integration is set to windows, else the authentication for the SSAS datasource gives and error

The extranet zone ( forms) and intranet (Customer Forms) and default (Windows) zones are all access from inside the firewall and the reports render in each with no issues, as the datasources are configured to pass a sql username and password.

However, report rendering is a problem from the internet (external site), the following error is displayed:

An unexpected error occurred while connecting to the report server. Verify that the report server is avai

Hi, I want to my workflow do some action when server lose connection with client and at the same time client get exceptions about it. It is possible to implement some session mechanism or something like that with workflow service ?
Regards
Marcin

I am trying to get a handle on the fact that applications have to manage the persistance of workflows directly. in 4.0. If I set a workflow to run every night at 3:00 AM and then be persisted, how will I know that my application will be awake
and ready to do the job.
I know that SharePoint currently uses a timer on the server which fires off every 5 minutes (default).