|
We are unable to send an excel file as attachment using dbmail.
The above script results in
However, we can send a different excel file with exact same script (just change file name to e4345pc1.xls) in the same folder with no problems (mail queued). Files have same permissions; only difference is that the first file is 1296 KB and the 2nd is 219 KB. However, the databasemail is configured for max file size of 7,000,000, well above 1296 KB. Any ideas on how to get this to work?
(comments are locked)
|
|
Similar issue described here on MSDN forums. May be worth opening a case with MS support, to track down the memory issue for your scenario?
(comments are locked)
|


whats in the event log??
Source SQLAgent$SQL2005 Category Alert Engine Event 3221225794 Message The data portion of event 17052 from MSSQL$SQL2005 is invalid. Source MSSQL$SQL2005 Category Server Event 1073758876 Message The description for Event ID '1073758876' in Source 'MSSQL$SQL2005' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'Severity: 16 Error:0, OS: 0 [Microsoft][SQL Native Client]Memory allocation failure'
and both files are not locked (i.e. opened) by anyone?
No it's not locked; since posting yesterday, we have changed the file attachment to a csv file (268 kb) instead of xls and we're now able to send the attachment.