I have been creating reports that include drillthrough. It was successful, everything worked but then the next day it gives me an error...For example, a certain parameter is missing...but I did not make any changes after the report was successfully ran the previous day..Same thing happened to multiple reports at different times. It is quite frustrating because I even made screenshots that everything worked at first but the next day everything failed...Such a mystery...
If anyone has any ideas about it, it would be highly appreciated...
Thank you.
Related
I at my whits end.
I have spent the last couple of days building a very in depth and mildly interactive report in Visual Studio 2015 (yes, I know but SMT wont let me upgrade to later version).
The report work fine in VS2015 but when uploaded to Dynamics 365, it is empty. The very odd thing though - the 'blank' report has the right number (3) pages however they are empty other than the header and footer.
I have a few Parameters that the user can choose from and it is the first time using these (just to set viability for a few tablix).
I don't even know where to start with searching this - all the results I am getting relate to reports having extra blank pages at the end but nothing about just coming up empty but still having the right number of pages.
I'm sorry that this seem (is) a bit of a wishy washy question. I just dont even know where to start asking for help...
EDIT: The problem appears to be with EnablePreFiltering="True" If I disable this, the report will run and return many many many pages and they are all formatted correctly. I have built my report so that everything is inside a single List which I apply the current users record to. Again - the problem is here somewhere.
Edit: (Wine has just been opened and the laptop charger is out - going to be a long night)
I am having a strange issue with SSRS 2016. We setup a new server and uploaded some reports, the reports ran fine for few days. The issue is, randomly the report doesnt run, When I load the report page, the parameters appear blank and I am unable to select any parameters. If I try to run and click the view reports button, nothing happens. After few mins/hours, it automatically resolves.
We have contacted MS support and could not get anything to get this resolved
Has Anybody faced a similar issue ?
This does not constitute an answer but it won't fit in a comment!
Does this affect more than one report?
If more than one, do they all fail at the same time or will one work and another not when you try to run the at the same time?
If the situation is "all fail" or "all work" at any single point in time then try adding a new report with no parameters.
If this attempts to run when other reports fail then it sounds like the datasource cannot be resolved or a timeout connecting to the database.
If your parameters are populated by querying the database the report will 'hang' until it can complete the queries to populate the parameters so by running a parameter-less report you should see an error instead.
Try running a trace on the database server to see if you can see the queries being run at all.
A bit vague I know but it might help you understand where the problem lies a little better.
I have a problem with my paginated report and I need help. I have three parameters in my design and whenever I run it, the parameters don't ever appear on the reports. I have tried it in different ways but the result always comes back to me same way. Please could anyone help me with this? Even when I click the parameter pane, the parameters are nowhere to be found.
I have also deleted it several times but still does not work.
Do you just try to run it on the preview mode? if so you just need to close the SSDT and reopen it
I can't figure out what is going on with my report in Access 2010. When I run it, all the queries and recordsources are generated and the report shows up, perfectly full of data and formatted in print preview. If I try and print a hard copy or export to PDF, the subreports don't print. I have done compact and repair, closed and opened, and check everything I know, but it's not working. The only thing that I can think of is that the subreports are based on temp tables I generate and set within VBA after I pull all the parameters I need. But I don't see why this would cause it to preview but not print? Any help would be greatly appreciated!!
Here's the solution I found... when I moved the table creation code to the button that prompted the report rather than having it use the openargs in the open event of the subreport, it worked. Don't know why exactly it liked it one place better than the other, but I'm glad that it works now!
After many hours in research and experimentation the only solution was a third party print function: http://www.lebans.com/reporttopdf.htm. Leben’s function always produces a printable PDF with visible subreports.
No modification of the report’s properties was of any value, though this is suggested by various posts; it failed to work for me. Similarly, compact and repair failed to help, as did the creation of a wholly new MDB file and importing all the forms/tables/queries. I ran the MDB in Access 2003 and in Access 2010 on another machine and had the same failure.
This points of course to the issue being embedded within Access. Research shows this has been an issue plaguing Access for many years; in its inimitable lack of care for users getting work done Microsoft has failed to even comment on this, much less fix it.
I had a similar issue and thought that I should post my fix in case someone else runs into the same problem.
I had a report with two subreports on it. From a form, I would select from several combo boxes and then hit the button to run the report. When the report opened (in preview and in report-view) it looked fine, and the subreports worked fine. However, when I tried to print or save, the subreports would not show up.
My solution was in my queries and in the form. The report's source queries were pulling criteria from the combo boxes on the form. Once the report was run, the combo boxes would clear, thus clearing the criteria for the queries. After the report is run, the report looks at the queries again when you try to print/save.
If you have a similar setup, I would suggest checking your source queries again after the report is run to see if you are still getting results. You should see the same data in your queries and in your report. If not, there's where to start looking. Hope this helps anyone else struggling with the same issue.
Good day
I have problem that really puzzle me. I wrote a report in visual basic 2008 when I run it it works perfectly. When I copied the report to report sever and run it it works perfectly.
I coded my asp.net application and call the report on a small database with about 500 entries everything shows and doesn't time out.
Problem is when entries the report must show becomes more than 500 the report runs but it stop and just show nothing it is as if it times out. There is no error nothing just stops.
I have no idea what to do? Anyone with any advise please.
I have change in the report server web.config file this setting to longer like "30000"
<httpRuntime executionTimeout="9000" />
Then on the report it self on server change the setting to never time out.
Then in the asp.net web config file change the timeout to "30000" but still when data to much the report just stop like I said no error no warning nothing it just stop and there is no info displaying so if anyone have any advise please assist.
I would use SQL profiler to see what is being submitted to the database. Take that query and run it in SSMS. View the explain plan in SSMS. This may let you know why the query is becoming so slow with the larger data. I would also look at the report server logs - something will be in there.