"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

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

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

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

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

"Report is being generated"

Hi

I have a windows application. I am using following code right after setting the LocalReport ReportPath. Report rendering is too slow if use following line of code and Report viewer does not show spiny and the text that says “Report is being generated.”

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

As to the spiny thingy, I believe that setting the zoom on the report viewer changes the zoom of the report once it is rendered. From what I can tell, the spiny thingy is rendered prior to the report being rendered.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

I am using a Report Viewer for Windows application and I guess by default AsyncRendering is True. I did not find any way to make it false to give a try. I am still not able to figure it out why "SetDisplayMode(DisplayMode.PrintLayout)" making report rendering so slow and also it is making spiny to disapear.

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

You probably haven't touched it at all. And I don't think that setting display mode to false would automatically set ShowProgress False, but it *might* have that effect -- test its value, just in case, after you use the SetDisplayMode method.

Can you verify a couple of things about this report -- what is the interactive page size versus the standard page size? If the two are different, this might explain why you don't see the progress feedback in one case but you do in the other (if the page sizes are significantly different, I mean).

Alternatively, if you have been omitting the zoom-setting lines after the SetDisplayMode line when you don't set display mode, then Greg's explanation completely maks sense: the original zoom value shows enough of the page to show the progress feedback, while your chosen zoom value here does not.

>L<

"Report is being generated"

Hi

I have a windows application. I am using following code right after setting the LocalReport ReportPath. Report rendering is too slow if use following line of code and Report viewer does not show spiny and the text that says “Report is being generated.”

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

As to the spiny thingy, I believe that setting the zoom on the report viewer changes the zoom of the report once it is rendered. From what I can tell, the spiny thingy is rendered prior to the report being rendered.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

I am using a Report Viewer for Windows application and I guess by default AsyncRendering is True. I did not find any way to make it false to give a try. I am still not able to figure it out why "SetDisplayMode(DisplayMode.PrintLayout)" making report rendering so slow and also it is making spiny to disapear.

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

You probably haven't touched it at all. And I don't think that setting display mode to false would automatically set ShowProgress False, but it *might* have that effect -- test its value, just in case, after you use the SetDisplayMode method.

Can you verify a couple of things about this report -- what is the interactive page size versus the standard page size? If the two are different, this might explain why you don't see the progress feedback in one case but you do in the other (if the page sizes are significantly different, I mean).

Alternatively, if you have been omitting the zoom-setting lines after the SetDisplayMode line when you don't set display mode, then Greg's explanation completely maks sense: the original zoom value shows enough of the page to show the progress feedback, while your chosen zoom value here does not.

>L<

"Report is being generated"

Hi

I have a windows application. I am using following code right after setting the LocalReport ReportPath. Report rendering is too slow if use following line of code and Report viewer does not show spiny and the text that says “Report is being generated.”

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

As to the spiny thingy, I believe that setting the zoom on the report viewer changes the zoom of the report once it is rendered. From what I can tell, the spiny thingy is rendered prior to the report being rendered.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

I am using a Report Viewer for Windows application and I guess by default AsyncRendering is True. I did not find any way to make it false to give a try. I am still not able to figure it out why "SetDisplayMode(DisplayMode.PrintLayout)" making report rendering so slow and also it is making spiny to disapear.

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

You probably haven't touched it at all. And I don't think that setting display mode to false would automatically set ShowProgress False, but it *might* have that effect -- test its value, just in case, after you use the SetDisplayMode method.

Can you verify a couple of things about this report -- what is the interactive page size versus the standard page size? If the two are different, this might explain why you don't see the progress feedback in one case but you do in the other (if the page sizes are significantly different, I mean).

Alternatively, if you have been omitting the zoom-setting lines after the SetDisplayMode line when you don't set display mode, then Greg's explanation completely maks sense: the original zoom value shows enough of the page to show the progress feedback, while your chosen zoom value here does not.

>L<

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B) (rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?
Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B)

(rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1

"...report server cannot access internal information..."

I've been unsuccessful getting Reporting Services 2005 to work after reinstalling SQL 2005. The RS service cannot connect to its database, as reported in the Event Log. If I visit http://localhost/Reports, I get the error "Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B) (rsRPCError)"

I've used the RS Config Mgr to create a fresh database for it named SSRS (and SSRSTembDB), and it is set to use Service Credentials in the db connection. The RS service is running using the same admin account as MSSQL, .\SQLExec. I have confirmed that .\SQLExec is in the RSExecRole role in the SSRS database.

When I created the SSRS database, the Config Mgr had a green check for every step except the last. For "Setting Connection Info for the Reporting Server" there was a yellow '!', with the explanation, "Although saving the database connection succeeded, the report server cannot access internal information about this deployment to determine if the current configuration is valid for this edition. ..."

I examined rsreportserver.config to look for any issues. The <dsn> element has an encrypted string, the <ConnectionType> element says "Default", and the logon elements are empty. I could not find the db names, SSRS and SSRSTempDB, anywhere in the file. Where are these kept? I don't know what else to look for.

Also, in RS Config Mgr, the 'Encryption Keys' page has a blue '!', and only the 'Restore' and 'Delete' buttons are enabled. The 'Initialization' page has a red 'X'. The local RS is not listed (the grid is empty), and clicking the 'Initialize' button does nothing.

How can I diagnose and fix this installation?
Check and see if you had changed your password on your Administrator account for your server after installing Reporting Services. This will cause the problem if you have.|||I posted the solution in another thread. See:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1258874&SiteID=1