Hi there,
We are having quite a bit of trouble with the report server failing to send emails out using sql database mail.
The report sever creates the pdf files fine and as far as I can tell the permissions on the folder is ok however we get the following error each time which seems to be coming from the database mail component.
Error sending email:
SQLSTATE = 42000
Microsoft OLE DB Provider for SQL Server
C:\impftp\report\SystemTableListing_14032.pdf is not a valid file or the process is unable to access the file.
The report server application runs as the same user account as the SQL server service account with both on the same box. I have tried using a network share and a local path for the reports folder but both have the same issue.
The tessituraservices application pool runs on a different server under the applicationpoolidentity and I have tried allowing the machine account of this server to access the reports folder but the same issue occurs.
Strangely it broke after we moved the live DB to another SQL server but I got it working however it stopped on the weekend and I have no idea why it won't work.
Any help would be much appreciated
Thanks
Mike Cornthwaite
Hi Mike,
On the off-chance that this issue is similar to some of the issues I've seen and troubleshooted with the Report server, try the following:
In the Report Server configuration (gsrbatch.ini, or the window in gsrbatch.exe), set Maximum Concurrent Jobs to 1.
In T_DEFAULTS, set EMAIL REPORT DELETE FILE to No.
I haven't the slightest idea why this is the case, but changing EITHER of those settings in our environment causes PDF emails to fail randomly. They've been consistently successful (except one time when the windows print spooler service died*) since I started running that configuration.
Just to remove some other variables, I assume you've tested sending database mail manually? If the file is being written to the folder properly, what happens when you run the sp_send_dbmail (pointing to the file as an attachment) yourself in SSMS? If that fails with the same error, then you know it's a permissions issue.
----
*Print Spooler Service Issue -- By default the recovery options for this service is set to "Take no action" on "subsequent failures". Might be a good idea to set this to "restart the service", else you may find that all of your infomaker reports fail to do PDF email one day because the Sybase Datawindow PS printer has disappeared.
Hi,
We had the same problem here. I followed some of the suggestions listed here, and still got the error.
Right before I was about to pull my hair out, jump out the window, etc., I tried changing the T_DEFAULTS email report path and email attachment path from our t:\attachmentfoldername to \\servername\c$\...\attachmentfoldername.
That worked. I don't know why. I don't know enough about permissions and whatnot to know what's up with our network, that our t_defaults hates our T drive so much. But... another thing one could try, if this problem's encountered.
Hello,
I am having a similar issue with setting up our v12 report server . I wanted to know is there a script that needed to be run on the SQL side that enabled report server emailing to work in v12. I vaguely remember doing this in earlier versions of Tessi.
Jason
JAson