October 25, 2024 at 6:10 pm
Hi, a peer asked me today to help on this ssrs error. There is a lot going on in this report but the dataset in question uses a table meant just for ssrs and is filtered in the report by the userid of the person running the report. When i run the query with a valid userid or without in ssms i get the expected results. But the report gets the error you see below even when i rig it to use the only userid currently present in the source table. i poked around on the internet and the only culprits i see have to do with data types. but i dont believe a data type has anything to do with this as the only variables are 1) userid passed from ssrs, 2) 2 table variable which dont appear to interfere when i run the query under ssms with and without a valid userid. does the community recognize this error as having anything to do with something other than data types?
October 26, 2024 at 7:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
November 7, 2024 at 9:06 pm
here is one of the posts i see on this subject. its hard for me to make the leap between a division and sql being unable to read a (next) row. https://stackoverflow.com/questions/57414474/rsprocessingerror-reporting-services-error-rserrorreadingnextdatarow .
here is another one. i'm going to look closer at my report for some sort of intentional or unintentional cast. https://www.sqlteam.com/forums/topic.asp?TOPIC_ID=180809 .
i started dividing and conquering and believe i found the culprit. i ...
so my take away was that ssms was forgiving the divide by zero but partnered with ssrs, sql wasnt. disturbing to say the least. i think there is a way in sql to be stricter on what is forgiven, i believe it is called exact abort or maybe arithmetic abort..
my plan after comparing notes with my peers is simply to either cast that value to more decimal places or show a blank in the report when the divisor is so small and causing the division to generate a value that is too high to be useful to our business.
November 7, 2024 at 9:18 pm
Got some details? Like the parameter values you're trying to pass, the parameter definition, the stored procedure text, the related column types and sizes... you know, something so we can actually help?
Maybe show us the parameter values and types you're trying to pass and some data maybe?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply