Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Inconsistent behaviour with rendering engine Expand / Collapse
Author
Message
Posted Friday, October 25, 2013 4:29 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, March 31, 2014 9:19 AM
Points: 314, Visits: 677
Guys,

I'm having some real grief this morning, I'm hoping if I explain it someone might have experienced similar and could provide some clues to help me get to the bottom of it.

There's basically two situations:

1. Working - a procedure I've had on the go for over a year, delivers a fairly sizable XML file of over 30mb, a file share subscription works just fine and has been for ages.

2. Not working - I've copied the above procedure, removed one column (a varchar typically about max 20 characters in length) and added one other column, a primary key, so just a column of ints), other than that the new procedure is identical to the working one in case 1.

I was first alerted to an issue last night when I saved XML output directly from the report, it was only 10mb, which striked me as suspicious. This morning I've attempted to create a subscription of said report, this fails with the following error:

Failure writing file <Report Name> : An error occurred during rendering of the report.


That's not especially helpful, needless to say I tried it again, I then tried the following:

Changing format from xml to csv - same result
Changing the underlying proc to reduce the data set from @ 150,000 rows to 50'000 rows - same result
Setting up a new subscription for the working case (it still worked)
Creating a brand new report with a different name using the procedure which seems to be causing grief - same result

So I Googled the issue, it turns out you can view a log file on the server SSRS resides, so I've done this:

Microsoft.ReportingServices.ReportProcessing.HandledReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.ArgumentException: ' ', hexadecimal value 0x0B, is an invalid character.


So I'm thinking there's some dodgy stuff in some of the fields, however, the new and old procs are reading the same data except for an additional ID field, which is just an identify field created on the table, so as simple as it gets. So this puzzles me.

A second oddity is occuring too, if I run the report from Report Manager and select XML and dowload I'm getting a file of about 3mb, what's more odd is if I repeat this the file size changes - sometimes 2.5mb, sometimes 2.8mb, that's running hte same report within seconds of each other. Sure it's a live database but it's not using tables which will be changing *that* much - and at any rate if it was you'd expect a growth in the filesize.

Any assistance much appreciated, I'm going round in circles and making no progress :/

Thanks in advance.
Post #1508399
Posted Friday, October 25, 2013 4:40 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, March 31, 2014 9:19 AM
Points: 314, Visits: 677
Not that I thought it would, however, I've run this against every column in the output (dumping it to a table)

SELECT * from TableName where ColumnName like '%' + ' ' + '%'


And it didn't yield any results...
Post #1508400
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse