November 3, 2016 at 11:29 pm
I am getting the above error in a report, that did run fine. The sql statement is embedded in the report. Due to the report being uploaded to 3rd party software I cannot use a stored procedure. The original report was built in report builder directly on the Server where SSRS resides. There is no date conversion within the sql with the exception of converting datetime to date. The field in the table is a datetime datatype. The report ran perfectly.
I downloaded the .rdl to a workstation with report builder installed. That is when the error started occurring even though nothing within the sql statement had changed. I thought maybe the meta data got hosed up somehow, so even went as far as to build a new report; yet still get the same error.
The report has 2 parameters: @StartDate and @EndDate used in the WHERE clause.
Any thoughts as to what might cause this behavior would be greatly appreciated.
November 28, 2016 at 1:59 pm
Try sticking a textboxes in the report header or footer (as a quick and dirty debugging tool) and display the values that are going into the @StartDate and @EndDate parameters.
It sounds like you're getting a bad value that SSRS doesn't know how to interpret as a date. When you see the value on screen, it may give you more of a clue as to what's going on.
I hope this helps,
Rob
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply