What does this log error mean? "The requested functionality is not currently enabled"
library!ReportServer_0-193!46ac!08/14/2018-13:04:15:: i INFO: Call to GetReportParametersAction(/XYZ/ABC/MyReport).
library!ReportServer_0-193!46ac!08/14/2018-13:04:15:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.NotEnabledException: , Microsoft.ReportingServices.Diagnostics.Utilities.NotEnabledException: The requested functionality is not currently enabled.;
My report runs find in VS and in SSRS intranet server!
So what is the issue?
Result from the server says: "Processing: 0 processed of 52 total; 0 errors."
So if there is no error here what does the log error mean and why is not the front-end in sync with the back-end.
My report has three parameters CustomerNo and a date range Start and End dates.
All of which I set in the Data Driven Subscription. There is nothing wrong with the inputs as I have checked all of these.
The path and filename are all correct, no nulls.
I created the destination sub folder so I assume it inherits the security of the parent so I don't believe it is permission issue, if it is surely the log would tell me!?
I have also deleted my subscription and started again to no avail.
I am lost to even no where to start looking.
I managed to find a work around perhaps somebody else could share there experience! To let me know if you had a similar issue and how you resolved it if you did that was different to what I am about to describe that is move away from dataset to use defaults.
Might I add the log didn't update until would you believe an hour later to show the actual error as I checked the timestamp and the error mentioned was "... Default value or value provided for the report parameter 'FromDate' is not valid." So Got nothing to say other than ##$%^&.
It seems the problem was one or perhaps both of my date parameters as set in the data driven query were not compatible. So I ended up changing from using the option from "Get value from dataset" to "Use default value", then in my proc called by the report I set the default to NULL, then wrote script code that checked if the value of the date parameter was NULL then change to the desired default value, which is fine for what I needed that is to base it on first day of the month using GETDATE().
I didn't bother investigating further so I am not sure if it is locale issue since I am running on a Australian DMY server and perhaps input gets sent in MDY order or this is a SSRS bug! Who knows that was a few hours of time I will never get back over something that should have just worked.
Related
I have been trying to figure this out for a while now and I cannot seems to get it to work. I am trying to pass 2 date parameters to an SSRS report. I am using SSRS 2016. The link that gets you to the report is
http://ServerName/Reports/report/SomeFolder/ReportName I have tried following the unanimously agreed upon approach of simply appending &StartDt=01/01/2020&EndDt=01/31/2020 and other combination and listed below.
http://ServerName/Reports/report/SomeFolder/ReportName&StartDt=01/01/2020&EndDt=01/31/2020
http://ServerName/Reports/report/SomeFolder/ReportName&StartDt=01-01-2020&EndDt=01-31-2020
http://ServerName/Reports/report/SomeFolder/ReportName&rs:Command=Render&StartDt=01/01/2020&EndDt=01/31/2020
http://ServerName/Reports/report/SomeFolder/ReportName&rs:Command=Render&StartDt=01-01-2020&EndDt=01-31-2020
In all cases I get the almost the same error, with the only difference being how I added the dates. The path of the item '/SomeFolder/ReportName&StartDt=01-01-2020' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath) I have confirmed the parameters match StartDt and EndDt appear exactly that way in my report, just for SAG I even made the prompts match and they are Non null able Date/Time fields. None of available values or default values. If nothing is selected it has the calendar icon to pick a date and everything runs perfectly.
I actually think I saw something on this back in a .Net explanation but it came out to be the link below. As usual I never mark my answer as correct, but leave it for the next person.
http://ServerName/ReportServer/Pages/ReportViewer.aspx?%2FFolderName%2FReportName&rc:showbackbutton=True&StartDt=01/01/2020&EndDt=01/31/2020
I didn't create the report, but there is a (not data-driven) subscription. There is one parameter with a default value (no issues). Then there are two multi-value parameters. When modifying the (mysteriously empty) multi-value parms (after the report failed to run) I can select ALL for each and set to run once--and the process succeeds. A file is written out to the folder per my intentions.
But when the date to run is set to the next morning, the execution fails with a message about invalid parm values. When I go in to check, those multi parms are empty again.
How do I fix this? (dumb question, I know)
What am I doing wrong? (also, very non-specific)
What am I leaving out? (of this question)
How do I search for this issue on SO? (I tried, but I couldn't find anything similar; maybe I'm missing some terminology; my search terms were "ssrs subscription multi value parameter not saved")
This is a problem in DEV with the following configuration:
SSRS 2012
Reports configured to the language en-gb
I have recently noticed that all of my date time parameters are getting transposed when i click "View Report". So for example a GB date 08/01/2015 gets transposed to 01/08/2015 on clicking "View Report". This results in having to click the button twice for the report to show me the correct data. I have used SSRS on and off for many years and I have never noticed this before. Can anyone shed some light on this?
Obviously the parameter is switching between en-gb and en-us but why and how do i stop it?
I found a post where some one is suffering from the same problem as me but their solution seems a little overkill issue with DateTime datatype in SQL Server Reporting Services. They recomend changing your regional settings and IIS settings which may fix and or break all sorts.
I believe that the problem can be how do you set up the default value in the parameter definition. If instead of a fixed date, you use a dataset with a date time funtcion (something like " Select dateadd(month,-1,current_timestamp) as [Default Date]") and a default value based on that dataset, your problem could be solved, because you're not specifying any date format in the dataset's field and it should contain the right value.
Hope this helps.
I am using Sql Server Reporting Services 2008 R2. When "previewing" my current report, I see everything appearing as it should. The displayed query values are correct in my table, which reads straight from the single dataset.
However, I see this as a warning:
Warning 1 [rsRuntimeErrorInExpression] The Value expression for the textrun ‘Textbox20.Paragraphs[0].TextRuns[0]’ contains an error: Input string was not in a correct format. E:\SSRS_Projects\Custom Reports\Attendance\Attendance\MIA_1B_Math_Absence_Detail.rdl 0 0
The puzzling thing is that I have no objects named "Textbox20."
I tried browsing thorough the object list on the "Properties" panel
and didn't see it.
I did a Ctrl+F search for "Textbox20" and couldn't find anything.
I'm not sure what else I can describe at this point.
Does anyone know how I can isolate the cause of this warning?
Thank you
If I understand correctly, the warning message was caused by the incorrect previous expression, however, the warning message persists although the values displays correctly in the report after you modified the expression. Besides, the warning message came out even though you create a new report and use the right expression.This is a known issue in Report Designer. When there is a warning message generated in the "Error List" pane of the Report Designer, the warning message still pops up after we correct the previous error. Actually, it always pops up whenever we preview any report in the same project. To avoid the issue, we only need to close the project and reopen the project. That way, the previous error lists will be cleared and the warning message won't pop out unless there is still an error in the report design.And your table's columns and rows are here text box.so please select the table column and see the property name.
Try Using this code
=IIF(IsNumeric(Fields!Data.Value),CSTR(FormatNumber(IIF(IsNumeric(Fields!Data.Value),Fields!Data.Value,0),2)),Fields!Data.Value)
I have a strange phenomen I can't explain nor reproduce and I'm hoping you have an idea how it was possible for the user to enter an invalid value.
I have an Access-MDB with a form containing an edit field that should only accept time values without any date-information.
The relevant properties of that edit field are as below:
bound to a Date/Time database value (since access know no time-only datatype)
Format: "Time, 24hrs"
Input Format: "99:99"
(I use the german version of Access, so the property names may be a little different, but you see the pattern)
Now I found out that a user was able to enter a date value into that field. I'm nearly 100% sure that it was an accident and no "clever hack" in the form of directly opening the table and editing the corresponding Date/Time field. Since the entry was made back in 2009 (nobody spotted the error), I have no chance to ask the user how it was done.
I found two wrong entries with the dates "01.06.2000" and "01.07.2000" and I guess the user wanted to enter the times "06:00" and "07:00".
I tried every input I can imagine (like "6.0", "6;0", "6,0", copy&paste) but I was unable to trick access and enter anything except digits and the colon.
Do you have any idea what is going on and how the user was able to enter these dates accidentially?
A Jet/ACE Date/Time value is never stored "without any date information". If you attempt to store only the time component, it will actually be stored with the same time on day zero (Dec 30, 1899).
We can only speculate how the incorrect data was added back in 2009. If you want the database engine to require your Date/Time values to be stored with day zero as the date component, you can add a table-level validation rule. From the table property sheet, try this for Validation Rule:
DateValue([your_date_field])=CDate("1899/12/30")
If you want to allow Null for your_date_field, try this version:
IsNull([your_date_field]) Or DateValue([your_date_field])=CDate("1899/12/30")
Several possibilities:
A developer (you?) did it by accident when looking at the raw table
The client Access software went momentarily crazy and corrupted the entry. This has happen to us (fortunately very rarely) where our Access tables will end up with non-ASCII characters in a string field.
A bug in Access runtime allowed the problem in the past, but has been corrected in a service pack.
Finally, if you put in 90 hours, does it overflow into 4 days and something? That might do it.