DTS Job xp_sendmail command fails with mail error

  • I am using the following xp_sendmail command in an Execute SQL Task within a DTS Package.

    USE Master

    EXEC xp_sendmail @recipients='kgoodwyn;jcollins;bgardiner;bpontius',

    @query = 'Server.DBO.VSP_CreateReport',

    @subject = 'SQL Data Integrity Report for Indicative Table',

    @message = 'The contents of the Data Integrity Report for the Indicative Table',

    @attach_results = 'TRUE', @width = 600, @separator='|'

    The Package has been set up as a Job and the Job is scheduled as the 8th step of a main job. This 8th step has run successfully more often than not. But every now and then I received the following error (within the Job History of the main job):

    Error = -2147217900 (80040E14) Error string: xp_sendmail: failed with mail error 0x80040115 Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 18025 (4669) Error string: xp_sendmail: failed with mail error 0x80040115 Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: 0 (0); Provider Error: 5701 (1645) Error string: Changed database context to 'maste. The step failed.

    When I try to restart the main job from the 8th Step I get the following error:

    Errror 22022: SQLServerAgent Error: Request to run job Main_Job (from User NT_DOM\UserName) refused because the job is already running from a request by Schedule 189 (Tuesday thru Saturday at 0555).

    And the Job Status says "Performing completion actions."

    The main job runs daily and in order to get around this problem in the past I have deleted the main job and rescheduled it. I do not want to have to keep doing this. Thanks in advance for you help.

    Kevin

  • The error you are getting is due to a network error connecting to the exchange server. This could be because mail was stopped and the period for mail to start again exceeds the timeout value for mail, or that your exchange server was unavailable at the time.

    Check that you're mail server is accessible when the job runs and fails. If that's the case put a step in to check that the server is alive before sending the email.



    Shamless self promotion - read my blog http://sirsql.net

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply