June 27, 2017 at 12:30 am
We are getting communication link failure error for a direct loading package in SSIS frequently with errors like
1) Shared Memory Provider: Timeout error [258]. Code: 0xC004701A and failed the pre-execute phase and returned error code 0xC0202009.
2) Shared Memory Provider: Timeout error [258]. Code: 0xC002F210. Failed with the following error: "Communication link failure".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
any suggestions regarding this issue will be greatly appreciated.
Thanks in Advance
June 28, 2017 at 12:12 pm
What, exactly, is your SSIS package suppose to do? We need a lot more detail than just the error messages.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 3, 2017 at 4:48 am
sgmunson - Wednesday, June 28, 2017 12:12 PMWhat, exactly, is your SSIS package suppose to do? We need a lot more detail than just the error messages.
It is doing a direct load from source to destination on the same server. But the data is very high
July 3, 2017 at 10:46 am
upendar.dilytics - Monday, July 3, 2017 4:48 AMsgmunson - Wednesday, June 28, 2017 12:12 PMWhat, exactly, is your SSIS package suppose to do? We need a lot more detail than just the error messages.It is doing a direct load from source to destination on the same server. But the data is very high
Very high? High what, exactly? Row Count? Data volume? What kind of data source and what kind of destination?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 3, 2017 at 12:49 pm
Does it sometimes work OK, or does it fail every time?
July 4, 2017 at 11:10 pm
Phil Parkin - Monday, July 3, 2017 12:49 PMDoes it sometimes work OK, or does it fail every time?
It is happening for sometimes, not every time but frequently.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply