SSIS sql agent job failed

  • this job sync realtime between transacation database and reporting database

    Is this something network issue? please advise

    error

    Date6/22/2012 5:52:50 PM

    LogJob History (RealTimeETL_6_Dose)

    Step ID1

    Serverservername

    Job NameRealTimeETL_6_Dose

    Step NameDose

    Duration00:00:37

    Sql Severity0

    Sql Message ID0

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted6

    Message

    Executed as user: domain\service. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:52:50 PM Error: 2012-06-22 17:53:21.90 Code: 0xC0202009 Source: Dose Connection manager "ReportingMasterConn" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "TCP Provider: Only one usage of each socket address (protocol/network address/port) is normally permitted. ". End Error Error: 2012-06-22 17:53:22.11 Code: 0xC00291EC Source: GetTrackingVersions Execute SQL Task Description: Failed to acquire connection "ReportingMasterConn". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:52:50 PM Finished: 5:53:27 PM Elapsed: 36.61 seconds. The package execution failed.

  • If the package has been working and then failed this time then started working again, it is probably a network connectivity issue. It could also be that the remote instance was not online when the package ran.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • Can you connect to the instance that the package is hitting with SSMS?



    Twitter: @SQLife
    Email: sqlsalt(at)outlook(dot)com

  • Yeah server is accessible. Resolved.

    I cleared the job history and restarted the jobs. Now jobs are running fine.

    Looks like intermittent network connectivity.

    Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

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