refer this link for latest fixes in SQL Server 2005...
http://support.microsoft.com/kb/933508
SP2 Release version was --9.00.3042.00
Latest version with this fix(Mar 05) is -- 9.00.3050.00
Madhu
refer this link for latest fixes in SQL Server 2005...
http://support.microsoft.com/kb/933508
SP2 Release version was --9.00.3042.00
Latest version with this fix(Mar 05) is -- 9.00.3050.00
Madhu
Someone please help me with a workaround on this issue:
I have created three reports: (ReportA, ReportB and ReportC).
ReportA includes a subreport (ReportB). ReportB consists of one list. The list is bound to a dataset. The list consists of one subreport (ReportC). ReportC is an empty report.
What is the problem:
When running Report A,The report generation fails when the dataset that is used in ReportB returns zero rows and the report is rendered across two or more pages.
The same problem also occurs when the dataset returns one or more rows and every row are filtered away using a filter expression on the list in ReportB
To make sure that the report is rendered across two or more pages, just add some dummy data to reportA.
When reportB is run, the problem does not occur.
The first page is genereted correctly, but when I navigate to the second page, the error occur.
Anyone experienced the same issue?
This sounds similar to something I am experiencing. I am using SQL 2005.
I have 5 levels of nested reports.
The first page always displays as expected.|||Microsoft has confirmed to me that this issue is a bug and that this should be solved in Service Pack 1.|||Wow, that's great.
My PM actually solved this on for us with a work around. It's a problem related to a common business issue "asymetrical heirarchy". If there is no data in the 3rd level, it affects the turn down control on the top level. We are currently re-writing our queries to always produce results, and then hide the display when the childID = parentID.
Microsoft SRS 2005 already handles this issue better than most others, but if they're going to fix it all the way, that's great!
|||Hello,
when RS2005 SP1 wil be released?
Thanks in adavnce
Someone please help me with a workaround on this issue:
I have created three reports: (ReportA, ReportB and ReportC).
ReportA includes a subreport (ReportB). ReportB consists of one list. The list is bound to a dataset. The list consists of one subreport (ReportC). ReportC is an empty report.
What is the problem:
When running Report A,The report generation fails when the dataset that is used in ReportB returns zero rows and the report is rendered across two or more pages.
The same problem also occurs when the dataset returns one or more rows and every row are filtered away using a filter expression on the list in ReportB
To make sure that the report is rendered across two or more pages, just add some dummy data to reportA.
When reportB is run, the problem does not occur.
The first page is genereted correctly, but when I navigate to the second page, the error occur.
Anyone experienced the same issue?
This sounds similar to something I am experiencing. I am using SQL 2005.
I have 5 levels of nested reports.
The first page always displays as expected.|||Microsoft has confirmed to me that this issue is a bug and that this should be solved in Service Pack 1.|||
Wow, that's great.
My PM actually solved this on for us with a work around. It's a problem related to a common business issue "asymetrical heirarchy". If there is no data in the 3rd level, it affects the turn down control on the top level. We are currently re-writing our queries to always produce results, and then hide the display when the childID = parentID.
Microsoft SRS 2005 already handles this issue better than most others, but if they're going to fix it all the way, that's great!
|||Hello,
when RS2005 SP1 wil be released?
Thanks in adavnce
sql
Someone please help me with a workaround on this issue:
I have created three reports: (ReportA, ReportB and ReportC).
ReportA includes a subreport (ReportB). ReportB consists of one list. The list is bound to a dataset. The list consists of one subreport (ReportC). ReportC is an empty report.
What is the problem:
When running Report A,The report generation fails when the dataset that is used in ReportB returns zero rows and the report is rendered across two or more pages.
The same problem also occurs when the dataset returns one or more rows and every row are filtered away using a filter expression on the list in ReportB
To make sure that the report is rendered across two or more pages, just add some dummy data to reportA.
When reportB is run, the problem does not occur.
The first page is genereted correctly, but when I navigate to the second page, the error occur.
Anyone experienced the same issue?
This sounds similar to something I am experiencing. I am using SQL 2005.
I have 5 levels of nested reports.
The first page always displays as expected.|||Microsoft has confirmed to me that this issue is a bug and that this should be solved in Service Pack 1.|||
Wow, that's great.
My PM actually solved this on for us with a work around. It's a problem related to a common business issue "asymetrical heirarchy". If there is no data in the 3rd level, it affects the turn down control on the top level. We are currently re-writing our queries to always produce results, and then hide the display when the childID = parentID.
Microsoft SRS 2005 already handles this issue better than most others, but if they're going to fix it all the way, that's great!
|||Hello,
when RS2005 SP1 wil be released?
Thanks in adavnce
...anywhere in the folder structure a person must be set up as a Content Manager at the Reporting Services ROOT (and at every level of the folder hierarchy down to the level that they are moving/renaming)?
Sure, you can remove them from the role in other folders where they should not be moving or renaming objects, but it seems you still have to have them at the root (and down the chain), which gives them far more capabilities than you might intend.
Jeff
After further examination into this problem, it appears in order for someone to move or rename a report or file, they need two things:
1) Content Manager role for the folder they are moving to/from or renaming files
2) Content Manager role for the root RS folder, but not up or down the chain between the root or the folder above.
This has really got to be a bug, as I can't imagine Microsoft doing this on purpose.
Jeff
Good Morning:
There may be a number of issues (postback's, IIS, etc.) and I have deployed DNN in a similar way to your above example. This "thread" from the DNN forum may lead you in a direction that may help.
http://forums.asp.net/781505/ShowPost.aspx - Persistent Scrolling!
Best Reagrds,
Joe
Hi All,
I have created a Report that include 10 other sub reports. The problem is that if there is not enough space for that sub report on the page, it goes to the next page. Also, if the content of sub report is huge, it removes the page header details so that it can fit into one page.
Is there any way that the sub report breaks on its own and there is no wastage of space? I guess that will solve my problem of page header details as well.
If anyone has worked on such issue, please let me know.
Any help will be greatly appreciated.
TIA!!!
Hi,
Anyone has got any clue?
Regards!!!
HI ,
Although I am setting the Border Style for each & every cell and /or Merge cells ,But it is not reflected in the Reports Pre-view for Bottom ,Top & Right Sides in the Reports?Any clue why this is happening & for removing this & getting the right results would be helpful .
Thanks
I had an issue where the BorderStyle did not seem to change. I was attempting to set the border to None on the Bottom of a cell but did not change the BorderStyle of the cell below it. Once I changed the Top BorderStyle to None of the cell below then I saw the desired affect.
Hope this helps.
Sql Server,Boot.ini file