How this is configured is we have an SSRS report that needs to render check images into PDF files. Because there are many checks to render, each into separate files we must use a data-driven subscription report. To this subscription we provide the report parameters as well as the file name and path via the following script:
SELECT xxDatabase, CpnyID, CheckNum, CheckBatch, FileName, FilePath FROM database.dbo.vCheckDetailRunSo in "Step 4 - delivery extensions" we use the FileName and FilePath columns to name the files. Then in "Step 5 - parameter values" we use the first four columns for the required parameters.
The trick was when I provided the FilePath in all lower case I received errors for all the records processed in the Subscriptions > Status of the report - and no files rendered.
Oddly in the SSRS Execution Log it happily reported "rsSuccess" as the Status. And of course the job reports success too. You just get no results.
Going one step further we can look at the ReportServerService log in the SSRS data folder on the server. To do that with today's log you have to cycle the SSRS service, otherwise the log is still open and cannot be read. The log gives a clue as to what's happening with the following messages for every attempt to write a file:
notification!WindowsService_3!11b4!07/10/2014-12:43:27:: i INFO: Handling subscription ee8fc032-c6a1-419a-be10-b5dc9d10b084 to report CheckImage, owner: INVENERGY\BPS, delivery extension: Report Server FileShare. notification!WindowsService_3!11b4!07/10/2014-12:43:27:: e ERROR: Error occured processing subscription ee8fc032-c6a1-419a-be10-b5dc9d10b084: The path is not valid. The path must conform to Uniform Naming Convention (UNC) format.To resolve this I took the FilePath column off the subscription and pasted in the UNC path from Windows Explorer. This allowed the report to work and I noticed the only difference between the UNC path I pasted and the UNC path in the FilePath column is capitalization.
I then pasted the proper capitalized UNC path into my FilePath column in the database and the report then ran. Conclusion: Your UNC for a Subscription report in SSRS is CASE SENSITIVE!
No comments:
Post a Comment