April 9, 2018 at 5:45 pm
Hello,
I am seeing the below error coming from SSIS package at random times. There are around 15 data flow tasks within one package which run parallel. The task is to copy data from one SQL server and insert it in another SQL server. The package runs perfectly through SQL job but I get the below error at random times. I did a ping test and confirmed that there is no packet loss when this error occurs. The package error occurs at random task within those 15 and is different each time.
These 3 errors are shown in execution log every time the package fails:
| Error: <Sproc> failed validation and returned error code 0xC020801C. |
| Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DB_Name" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. |
| _Master:Error: 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: "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 11.0" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". |
I searched online and there no issues here with 32-bit vs 64-bit since there is no excel or other databases involved other than SQL server as source and destination. No packet loss using ping test during the error. The job runs successfully 95% of the day but fails at random times.
April 10, 2018 at 12:41 pm
could be DNS. For some reason it can't connect to the database.
Was SQL restarted during the error?
April 10, 2018 at 12:58 pm
No, the sql server was not restarted during the error. It occurs at random times.
No, there aren't any other errors. But these 3 errors come every time.
April 10, 2018 at 5:24 pm
I even tried adding connection timeout to 120 sec in the connection manager. The jobs fails within 60 seconds. So it's not a query timeout issue.
Retain Same connection wont work as I have 15 tasks running in parallel and will cause deadlock issue.
Any other ideas?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply