I'm interactively running a package, locally (on one device), to import records from flat-files to a SQL Server Express 2012 database.
The package will usually fail, displaying error messages of :
"Login timeout expired" or
DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER or
"Time-out occurred while waiting for buffer latch type 2”
depending on what property I've changed.
I'm running Windows 7 Pro; 64-bit; SQL Server 2012 Express (64-bit); the package was written in Visual Studio 2008.
On the Control Flow tab, I'm using a Foreach Loop container to repeatedly run a Data Flow task which is importing and processing flat-files, one at a time, and some File System tasks to Rename the error-files associated with each imported flat-file.
On the Data Flow tab, I use four components to perform some data validations and conversions before using an OLE DB Command component which executes the Stored Procedure that does the INSERT. Crude but it's been working. Intermittently. Which is the problem.
Sometimes it'll successfully import and process a couple of files and fail. Sometimes it'll process nearly 20 files and fail. Sometimes it'll do 10 or 20 and not fail.
Here's the portion of the text from the Output panel that's relevant:
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Error: 0xC0202009at ReWriteLoadVoterHistoryTable, Connection manager "MYSERVERNAME\SQLEXPRESS_INST1.GRP_VoterDBv5_JH": 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 11.0" Hresult: 0x80004005 Description:"Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Unable to complete login process due to delay in login response".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Shared Memory Provider: Timeout error [258]. ".
Error: 0xC020801Cat Data Flow Task, LookupToVerifyElectionType [9]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "MYSERVERNAME\SQLEXPRESS_INST1.GRP_VoterDBv5_JH" failed witherror code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC004701A at Data Flow Task, SSIS.Pipeline: component "LookupToVerifyElectionType" (9) failed the pre-execute phase and returned error code 0xC020801C.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "component "Err_NoMatchElectionType" (199)" wrote 0 rows.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "component "Err_NoMatchingElectionID" (318)" wrote 0 rows.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "component "Flat File Destination" (447)" wrote 0 rows.
Information: 0x40043009 at Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Error: 0xC0010202 at Data Flow Task, LookupToVerifyElectionType [9]: Failed to mark the cache as filled with data.
Error: 0xC004701B at Data Flow Task, SSIS.Pipeline: component "LookupToVerifyElectionType" (9) failed the cleanup phase and returned error code 0xC0010202.
Task failed: Data Flow Task
Warning: 0x80019002 at Foreach Loop Container: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Warning: 0x80019002 at ReWriteLoadVoterHistoryTable: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "ReWriteLoadVoterHistoryTable.dtsx" finished: Failure.
Some of the Properties of the Connection Manager in question are:
Initialization / Connect Timeout: 0
Initialization / General Timeout: 0
(I tried Pasting-in and image-snippet of this Connection Manager / Property window, but I'm not permitted.)
In reference to some of the suggestions I've read in other threads:
I don't think setting Run64BitRuntime to False is relevant since both the OS and database are 64-bit;
when the Connection Manager's RetainSameConnectionwas set to True, the package failed with"Time-out occurred while waiting for buffer latch type 2 for page (1:103), database ID 7."
though it also didn't seem relevant, I tried setting the package'sDelayValidation property to False; it didn't help. It failed with the same “buffer latch type 2” error as above.
The Server's Remote Login Timeoutwas set at 10.I changed it to 0 (infinite wait), and ran the package again. It successfully processed 5 input-files this time, then croaked, with this from the Output panel:
Error: 0xC0202009 at Data Flow Task, OLE DB Command [340]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description:"Time-out occurred while waiting for buffer latch type 2 for page (1:247), database ID 7.".
Error: 0xC0209029 at Data Flow Task, OLE DB Command [340]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Command Input" (345)" failed because error code 0xC020906E occurred, and the error row disposition on "input "OLE DB Command Input" (345)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.
Error: 0xC0047022 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Command" (340) failed with error code 0xC0209029 while processing input "OLE DB Command Input" (345). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
Any suggestions of what else to try will be much appreciated. Thanks.