Hi everyone,
For the last week, our SSRS scheduled Report is not sending emails. This is the error we are getting, " error sending email for request id XXXXX". Please advise, if you have run into this issue. we are self-hosted. on the Tessituraweb log, I found this,
Date|Component|Logger|Location|WindowsLogin|UserId|UserGroup|Level|Message2022-04-21 19:01:00.2376|TessituraWeb|*|INTREPID-TESSAP|IIS APPPOOL\TessituraServicesSite|||Error|There was an error processing request with id '159289'.2022-04-21 19:01:00.2566|TessituraWeb|*|INTREPID-TESSAP|IIS APPPOOL\TessituraServicesSite|||Error|Server was unable to process request. ---> Access to the path 'E:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\RSTempFiles\RSFile_88f601af-d3bb-4922-895d-27232b560f52' is denied. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Tessitura.WebReports.Reports.ReportExecution.ReportExecutionService.Render(String Format, String DeviceInfo, String& Extension, String& MimeType, String& Encoding, Warning[]& Warnings, String[]& StreamIds) at Tessitura.WebReports.Reports.ReportRenderingHelper.RenderReportSnapshot(Int32 requestId, String reportServerUrl, String fileFormat, String scheduleName, String report, String historyId, String deviceInfo, String& fileExtension) at Tessitura.WebReports.Reports.ReportService.ProcessSnapshotRequest(Int32 requestId)
thank you in advance.
Sharon Choondassery
This sound a bit familiar to me. Our situation is that some scheduled reports would sent while others would not. They were SSRS reports like the ones you seem to be having challenges with. We opened a support ticket and discovered that there was a defect such that if we had a hyphen “-“ in the subject line of the scheduled job name, the report would not send. We simply changed the hyphen “-“ to a tilde “~” and the emails started sending. This is a strange defect. But, it is what worked for us. I’m not at all clear if this is the problem you are facing, I’m on RAMP Tessitura Hosting Services so do not have direct access to my SSRS error logs. However, I thought I would share in case this might help you or someone else.
If this is not your situation and does not resolve your situation, I’d definitely put in a support ticket if you have not already done so.
Thank you, Tom, was the report running before and stopped suddenly? For us, the report was sent out emails until April 12 and stopped suddenly.
I will check the subject line for our reports.
I've run into hyphen in subject line issue as well. Thanks for the tip on ~.
The reports had run for maybe years. However, I think that a service pack install or change made buy the RAMP team might have triggered the change of behavior for us. I never got to the bottom of the root cause. I just know that this silly change has made things better for us. I also know that it is easy for my end users to fall into the trap of creating new scheduled report with a character beyond [a-z][A-Z][0-9]. There are definitely some characters like ~ That are not causing problems. I don’t know the full list of problematic character. However, I know that hyphen has caused us problems on several occasions over the past 6 months.
Hope that helps.