locked
DTExec: The package execution returned DTSER_FAILURE RRS feed

  • Question

  • Hi

    I have Maintance plan ,it is weekly maintance plan,from the last two weeks it was failed.The error message shows below.

    Message
    Executed as user: (Security group). Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4000.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  2:00:01 AM  Error: 2014-05-10 02:00:08.83     Code: 0xC0202009        Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.  An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80040E4D  Description: "Login failed for user '(login).".  End Error  Error: 2014-05-10 02:00:08.83     Code: 0xC020801C     Source: AgentInstaller_AP OLE DB Destination (AgentInstall) 1 1 [45]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "REPT.DSM_Reporting_AP.sa" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error  Error: 2014-05-10 02:00:08.83     Code: 0xC0047017     Source: AgentInstaller_AP SSIS.Pipeline     Description: component "OLE DB Destination (AgentInstall) 1 1" (45) failed validation and returned error code 0xC020801C.  End Error  Error: 2014-05-10 02:00:08.83     Code: 0xC004700C     Source: AgentInstaller_AP SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2014-05-10 02:00:08.83     Code: 0xC0024107     Source: AgentInstaller_AP      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  2:00:01 AM  Finished: 2:00:08 AM  Elapsed:  7.395 seconds.  The package execution failed.  The step failed.

    Please help on that..

    Thanks,

    Kaseeswar Reddy.


    Wednesday, May 14, 2014 7:02 AM

Answers

  • HI,

    Thanks for your quick responce.

    Yes we did ths password change. After the pwd change the job failed.

    can you kelp me..

    Thanks,

    Kaseeswar.


    Hi Kaseeswar Reddy,

    Usually we can create SQL Server maintenance plans by using the maintenance plan wizard or the designer. It let you configure connection parameters for maintenance plans in the designer, but in the maintenance plan wizard , it uses the current session login for the maintenance plan connection without prompting for any connection parameters . According to your description, when you change the password for that specific login, you also need to update the password in the connection settings for the maintenance plan, otherwise the maintenance plan will not work.

    To fix this issue, we can synchronize the password in the maintenance plan connection parameters via providing username and new password in the designer view. You can also create a separate login to use for your maintenance plans. Either create maintenance plans using that login or use the connection properties of each maintenance plan to alter settings for that specific login. This will ensure that changing passwords for other logins does not impact your connection properties for your maintenance plans. For more information, see: http://www.mssqltips.com/sqlservertip/1973/changing-passwords-for-logins-used-with-sql-server-maintenance-plans/

    Regards,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    • Marked as answer by Sofiya Li Wednesday, May 21, 2014 1:35 AM
    Thursday, May 15, 2014 9:08 AM
  • HI,

    Thanks for your quick responce.

    Yes we did ths password change. After the pwd change the job failed.

    can you kelp me..

    Thanks,

    Kaseeswar.

    • Marked as answer by Sofiya Li Wednesday, May 21, 2014 1:35 AM
    Thursday, May 15, 2014 4:40 AM

All replies

  • Did someone change password for the user  _TGAV-DSMSSvc?

    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

    • Proposed as answer by Sofiya Li Thursday, May 15, 2014 7:08 AM
    Wednesday, May 14, 2014 7:12 AM
  • An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80040E4D  Description: "Login failed for user '_TGAV-DSMSSvc'

    Logs says the issue is with login used for the Maintenance plan, which can be due to multiple reason as mentioned in the below KB article:

    http://support.microsoft.com/kb/555332/en-us


    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Wednesday, May 14, 2014 8:45 AM
  • Hello Kaseeswar -

    Please check if the user _TGAV-DSMSSvc has access to REPT.DSM_Reporting_AP.sa connection - check the data base access as well.

    Looks like there is an OLEDB source connection to an sql server for which the user does not have access.

    Thanks - Deepak.


    Happy to help! Thanks. Regards and good Wishes, Deepak. http://deepaksqlmsbusinessintelligence.blogspot.com/

    Wednesday, May 14, 2014 9:22 AM
  • HI,

    Thanks for your quick responce.

    Yes we did ths password change. After the pwd change the job failed.

    can you kelp me..

    Thanks,

    Kaseeswar.

    • Marked as answer by Sofiya Li Wednesday, May 21, 2014 1:35 AM
    Thursday, May 15, 2014 4:40 AM
  • HI,

    Thanks for your quick responce.

    Yes we did ths password change. After the pwd change the job failed.

    can you kelp me..

    Thanks,

    Kaseeswar.


    Hi Kaseeswar Reddy,

    Usually we can create SQL Server maintenance plans by using the maintenance plan wizard or the designer. It let you configure connection parameters for maintenance plans in the designer, but in the maintenance plan wizard , it uses the current session login for the maintenance plan connection without prompting for any connection parameters . According to your description, when you change the password for that specific login, you also need to update the password in the connection settings for the maintenance plan, otherwise the maintenance plan will not work.

    To fix this issue, we can synchronize the password in the maintenance plan connection parameters via providing username and new password in the designer view. You can also create a separate login to use for your maintenance plans. Either create maintenance plans using that login or use the connection properties of each maintenance plan to alter settings for that specific login. This will ensure that changing passwords for other logins does not impact your connection properties for your maintenance plans. For more information, see: http://www.mssqltips.com/sqlservertip/1973/changing-passwords-for-logins-used-with-sql-server-maintenance-plans/

    Regards,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    • Marked as answer by Sofiya Li Wednesday, May 21, 2014 1:35 AM
    Thursday, May 15, 2014 9:08 AM