June 18, 2012 at 9:53 am
Hi guys,
I'm getting the following error when running scheduled SQL Agent job -
Microsoft (R) SQL Server Execute Package Utility Version 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:33:06 PM Error: 2012-06-18 16:33:07.73 Code: 0xC002F304 Source: Send Mail Task Send Mail Task Description: An error occurred with the following error message: "Failure sending mail.". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:33:06 PM Finished: 4:33:07 PM Elapsed: 1.235 seconds. The package execution failed. The step failed.
Everything works other than the SendMail part.
What i think it might be is that - until recently SSIS packages were developed and run on the same server. However NOW... I create my packages locally in a development area and then promote them to the reporting server.
- When developing I run VS 2005 as the service account that i use on the reporting server to actually run them.
- This account has access to all the necessary areas, including the SMTP server as there are other jobs on there that run fine.
The only difference is since I have started developing and promoting on 2 different servers the newly created ones always fail on the 'SendMail' task.
Is there something simple I am missing?
Cheers,
Dan
June 20, 2012 at 2:26 am
have the new servers been granted the nessesary access on the mail realy (smtp) server to send mail?
the account might have access, but does the server?
June 21, 2012 at 2:11 am
Cheers for the reply - turns out that the name of the smtp server had been changed - and I hadn't been told!
Corrected the smtp name/address - and voilá!
Knew it wouldn't be any fault of mine!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy