July 2, 2014 at 7:49 am
Afternoon all,
I have an SSRS report that is designed to query data from a database and produce an xml document with the information so gathered. We are using an xlt transform to clean up the resulting data (mainly ignoring some unwanted levels to the hierarchy), everything appeared to work fine (and continues to work on a 2005 server, but on our 2012 server I am now getting an essentially blank document. (I am just getting the <?xml version="1.0" encoding="UTF-8"?> line and the root element with no children).
We need to run this in 2012 as we need to use a data driven subscription to generate the required file name (2005 is standard edition).
Has anyone come across a similar situation and if so, how did you resolve the problem?
Thanks in advance.
JST
Assumption is the mother of all F***ups
July 2, 2014 at 8:48 am
Going through the execution log in the report server I've found that all the executions since the problem surfaced have had a status of "rsServerConfigurationError" and all the times for data retrieval, processing and rendering are all 0, even though the report has rendered in report manager with data.
something for me to look into and I'll post if I get to the bottom of it, but if someone reads this and thinks "Ah, I know what's going on..." please share! 😉
Assumption is the mother of all F***ups
July 3, 2014 at 2:36 am
OK, the configuration error was a red herring, I hadn't ordered the query to show timestart descending so was looking at the first handful of runs while we sorted out the execution account (oops) :blush:
The actual problem was caused by the xslt file having become corrupted, hence the only part of the match that was being found was the root node. Replace this and all is well again.
JST
Assumption is the mother of all F***ups
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply