New errors on old reports

Question

New errors on old reports

ritteranc

SSC Enthusiast

Points: 150
More actions
December 7, 2016 at 2:08 pm

#319607

Hi, all. Odd problem. My reports were working fine 2 weeks ago, but now I'm getting the much loved "Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;" error.
If I delete EVERYTHING (all tables, textboxes, parameters, etc) from the report and create a dataset that "SELECT 'test' AS Test FROM tablename" and just put a textbox on the report to display the 'text' field, I still get an error message (Invalid length parameter passed to the RIGHT function).
On other, completely unrelated reports, I am getting:
An error occurred during client rendering.
Unsupported RPL stream version detected: 101.116.1047292257. Expected version: 10.6.
There is no sharepoint integration on this server. These reports are pretty complex, with many subreports, but they don't take a very long time to render (10 seconds max).
This is in SQL 2012, and the reports run fine in SSDT, but not once deployed. I think that this server was hardbooted during a power failure last week. Some less complicated reports are working fine.
Can anyone point me in a direction here?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

doug.brown SSCertifiable Points: 5607 More actions · Answer 1

I don't know about the second error, but when I've encountered "Invalid length parameter passed to the RIGHT function" it usually means I've got some anomalous data that's smaller than expected. So if the function is something like RIGHT(FieldX, LEN(FieldX) - 6), there is some record in FieldX shorter than 6 characters.

ritteranc SSC Enthusiast Points: 150 More actions · Answer 2

That's what I've seen too, and what I expected to be causing the error. However, if I remove all data from the report, but still get the error.... I just don't know what the cause of that could be.

doug.brown SSCertifiable Points: 5607 More actions · Answer 3

I would still expect to get this error with empty data, because LEN(0)-6 will still result in the RIGHT function being passed a negative number. Both examples below will return the invalid length error:

DECLARE @a VARCHAR(10)

SET @a = 'abcde'

SELECT RIGHT(@a, LEN(@a) - 6)

SET @a = ''

SELECT RIGHT(@a, LEN(@a) - 6)

Have you tried searching the field in question for records where LEN(FieldX) < X, where X is whatever number of positions your RIGHT function is looking for?

ritteranc SSC Enthusiast Points: 150 More actions · Answer 4

For starters, I just want to say thanks so much for assisting.

Referencing your above reply, my dataset right now is:

SELECT 'Test' AS Test

FROM tIncident

So I'm not really applying any functions to it at all. I just tried to create a new report using the reportbuilder. Added the above as my dataset. Selected a matrix report. So one column, one row. And the only bit of data on the entire report is "Test". No parameters or special code of any kind. And I still get the RIGHT function error. Has my installation been corrupted? It's odd that some reports can still run without giving me this error, but I cannot even create a brand new one.

doug.brown SSCertifiable Points: 5607 More actions · Answer 5

Maybe there's an expression hidden in a textbox/cell/table that has a RIGHT function? With that dataset I agree you shouldn't be getting the error you're getting. Ain't compooters fun? 🙂

ritteranc SSC Enthusiast Points: 150 More actions · Answer 6

Ha Ha Ha! Indeed. MS isn't terribly helpful with error messages, either.

I fixed it by reinstalling SSRS and redeploying my solution. My guess is that when the server lost power, some kind of subtle corruption happened to the ReportServer db. Thanks again for your help!