I have a dataset created in SSRS using VS 2017. After the initial code created in query builder, I go the text window to add in a COUNT function. As soon as I do this, I start getting a text window with the old code intermittently blinking with the new changes. A warning triangle appears in the top cell of the row selector column that says "Query changed from last execution" once I hover over the triangle. Once this happens, the window will not allow any changes.
This is, no doubt, a bug. I also experienced this in VS 2019. Since I can close out of VS 2017, reboot, re-open the report, the intermittent blinking still occurs. What I have is a corrupted report and have to delete it. I want to avoid having to create and delete projects based on a bug that I cannot find any resolution for.
Does anybody have any experience with this?
Faced the same problem.
Was able to fix it by using "Stored procedure" instead of "Text" in Dataset properties window.
Related
My question is about the following scenario:
In SSRS 2015 one report keeps refusing to render(hangs on a blank report) under specific circumstances.
Here is the scenario.
Open the report, which automatically renders (Functions perfectly)
Alter one parameter (it doesn't matter which one), render the report (Functions perfectly)
Alter a another parameter (It could be the same one or a different one), render the report. It hangs. There is no actual error shown, but the report just hangs with nothing displayed.
Specifically; The parameters are all greyed out and no report is rendered. The "View report" button is still visible and appears active, but nothing happens when you click on it.
The only way to make the report function again is to back completely out of it and re-enter the report from the beginning.
It is important to note that none of the sub-reports are effected. You can drill through to them as much as you like and nothing will hang.
Also, this functions perfectly on our 2012 server and that no other reports on either server have encountered this error.
I can't even replicate it in Visual Studio.
Has anyone ever seen anything like this?
Any insight would be appreciated.
I've never seen this problem before.
The report elements are not updating from changes made in the Design mode in Visual Studio (2015). It's not a data issue - even static text box changes are not appearing.
I had removed the Member ID column, combined the last and first names into a single Member Name column, added a couple of columns and renamed SEX to Gender. Here's the Design view.
These changes should appear when I click on Preview but Visual Studio displays the old report.
As I mentioned, I haven't seen this before and haven't found any similar issues when using Google-Fu. I have tried restarting VS but that was no help. The only thing I did to get from the first pic to the second is to press the Preview button in Visual Studio. I've been trying to make it update for over half an hour now. I've updated and created hundreds of SSRS report over the last 15 years but have never seen or heard of this issue.
Is there some new preview caching that SSRS is now doing? It seems similar to the dumb data caching issue but I don't see where the report would be cached. This is completely ridiculous - what moron would create a caching for something being developed so changes can't be viewed?
How can I see the correct preview in my SSRS report in Viusual Studio?
Background:
We recently migrated to SSRS 2014; our source database is SQL Server 2008 R2. We ran into some performance problems on a report where it simply would stop responding and ultimately timeout after 30 minutes when rendering the report. Reviewing the execution log on the reporting server indicates that the data retrieval time is low, while the report rendering time is high. The solution our DBA discovered after a month of this problem, is to set READ_COMMITTED_SNAPSHOT ON.
This seems to have cleared up the very strange performance problem with a single report. This report would seemingly become deadlocked when users attempted to generate it. The deadlock appears to be on the temp report server database, occurs only when returning the report to the browser (IE or Chrome), and does not occur every time the report is generated, but may be occurring when multiple users are attempting to generate the report around the same time frame. The report has 3 levels of grouping, and returns a variable amount of rows for the entered parameters.
This setting (READ_COMMITTED_SNAPSHOT) seems to now have caused a secondary problem: in the navigation bar of the report, where the user can navigate through the pages on the report, initially displays 0 of 0 when an active "Next page" button. When the user clicks the "Next page" button, the browser performs a post-back (like it would if you were navigating to the next page) and refreshes the screen with the first page. Now, the navigation bar displays 1 of X.
All of our SSRS servers received READ_COMMITTED_SNAPSHOT ON, so I had asked the DBA to update my DEV server to OFF. When this was done, I re-generated all of the reports (about one dozen), and each of them initially displayed 1 of X pages, as I would have expected. Now, I question whether setting this property to ON was the correct approach for fixing the report.
I thought about whether creating a report snapshot would be a good solution, unfortunately, I don't think it is as we have users which have differing parameter selection.
Questions:
Was there a better way we should have solved the report performance problem above rather than setting READ_COMMITTED_SNAPSHOT to on?
Does READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION need to both be set to true/on if one is?
Has anyone encountered this problem related to the Navigation Bar in SSRS, and how were they able to resolve the issue?
Update:
We ultimately had to roll-back the READ_COMMITTED_SNAPSHOT setting, as it caused an entirely different error to occur. The problem outlined above, also seemed to clear itself up, with no issues reported two months in a row. Unfortunately, no one knows what was causing the issue in the first place, or what may have fixed it (possibly a hardware change).
I'm assuming you changed these settings on the source database of the reports, not the SSRS server itself (unless they are the same server). Changing the settings of READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION can have wide-ranging effects on your systems, so should be done with caution. See https://dba.stackexchange.com/questions/5014/what-risks-are-there-if-we-enable-read-committed-snapshot-in-sql-server for potential issues related to changing these settings (and also an answer to your second question).
To me it sounds like the problem is in your report query or queries, so changing these database level settings to resolve a performance problem in one report is probably overkill. I would first look at analysing your report queries and tuning them (and possibly adding missing statistics or indexes to the source database) before altering row versioning settings.
As to the navigation bar issue, perhaps the changes made to the row versioning mean the SSRS is unable to calculate the number of pages available when the page is initially loaded. However I don't know why that might happen.
I am taking over a SSIS package which was developed and running on another server, say Server-01. I am working on this package with MS Visual Studio 2008.
Now, I am trying to run it on my server Server-02.
So I changed the settings of some SQL Task boxes and their related data sources from Server-01 to Server-02, then pressed the OK. After this, I closed the setting panel and reopened it, it looks fine, all my changes have been recorded.
Then I run the boxes in Development mode. As it stopped, I open the boxes which I've changed, then find everything was changed back to its initial status.
May I know what is wrong with my operation, and how can I over come it?
Thanks.
After wrestling with the problem for a while, here are two methods I found. They may not formal, but it suits my case.
Method 1: I went to SSIS->Variables, then change the value of the variable there.
Method 2: I had one variable which cannot be changed via above method, so I opened its property panel, and changed the expression and assigned a new value to it.
Please correct me if my understanding is wrong, or if there are better ways to settle this.
Thanks a lot.
I am building a report with one "go to report" and in that new report I have one subreport. Now, when I´m sitting and working with the report and for instance changing the format for a cell the report doesn´t view the new changes directly. Sometimes it does. Sometimes I have to wait a while, sometimes I restart BIDS. Has anyone experienced this problem before?
I think the way VS maintains subreport data when designing means the definitions can get stale; does a Rebuild Solution before previewing help?
This should hopefully make sure everything is up to date and for a Report project/solution it should be quick to rebuild.