Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS job failing intermittently, connectionmanager failing Expand / Collapse
Author
Message
Posted Thursday, June 13, 2013 7:35 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 11:10 AM
Points: 7, Visits: 31
I have an SSIS package running fine 90% of the time, but for stretches of the day it fails over and over with 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 Native Client" Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".
End Error
Error: 2013-06-13 15:13:26.13
Code: 0xC020801C
Source: 03) Asset - RDP Link Update RdpFirstLinkCallLogId [14273]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "E2Prod2" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Every time it fails it's different. Different task flow, different connection manager failing, different times of the day

Using a config file
<ConfiguredValue>Data Source=localhost;User ID=sa;Initial Catalog=RdpTransactionServer;Provider=SQLNCLI.1;Persist Security Info=True;</ConfiguredValue>
Password is kep on a separate line.

But, the rest of the day it works fine.

It also only fails when running from SQL agent, never fails from BIDS.

Anyone have any ideas?
Post #1463090
Posted Sunday, June 30, 2013 11:00 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 8:51 PM
Points: 7,140, Visits: 12,763
It sounds to me like the server is too busy to service the request from the SSIS Package at various times of the day, likely during peak usage or during a heavy batch process, so the login times out. Try extending the timeout period (called Connect Timeout in SSIS terms) on all your connection managers that connect to the database instance and see if that helps.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1468877
Posted Friday, July 12, 2013 11:32 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 5:13 PM
Points: 456, Visits: 1,060
I concur with opc.three comment above. Are the package, job on different machines? What about the target server of the ole db connection ?

Post #1473164
Posted Friday, July 12, 2013 11:37 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 11:10 AM
Points: 7, Visits: 31
Thanks, but the time out is set to infinite so it should never time out.

It happens less than 2 minutes into the job each time.
Post #1473168
Posted Friday, July 12, 2013 11:38 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 11:10 AM
Points: 7, Visits: 31
Everything is run on the same box, two different ole db connections for two different databases on the same server.
Post #1473170
Posted Friday, July 12, 2013 11:40 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 8:51 PM
Points: 7,140, Visits: 12,763
SKKO (7/12/2013)
Thanks, but the time out is set to infinite so it should never time out.

It happens less than 2 minutes into the job each time.

Are you thinking of the command timeout? The login timeout is a separate setting that is not infinite by default. You would have had to change it explicitly.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1473173
Posted Friday, July 12, 2013 11:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 11:10 AM
Points: 7, Visits: 31
They're both set to that.
Post #1473175
Posted Friday, July 12, 2013 12:08 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 5:13 PM
Points: 456, Visits: 1,060
It also only fails when running from SQL agent, never fails from BIDS.


Just to be sure, is the config file with the user credentials stored in the same directory as the package? Are the package and config files in a shared folder that both agent and the user credentials in the config file have access to? I ask because when it works in BIDS and not under agent (not sure if this is all the time you mean or part of the time)... you have to rule out that the solution you created is still not in the visual studio projects folder under your name.. ie...
C:\Users\yourUserName\Documents\Visual Studio 2008 ... where an agent or other user may not have access.
Post #1473199
Posted Thursday, July 25, 2013 2:02 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 11:10 AM
Points: 7, Visits: 31
They're stored in different directories, but both the agent and the user have credentials. The job works 75% of the time though so I don't know how it could be a permisisons issue.

I actually had it fail with BIDS for the first time he other day, so it may not be an agent issue.

Post #1477721
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse