July 22, 2012 at 11:23 pm
Hi,
I have a job scheduled on my production server for Data insertion sometimes it produces an error, the error description is mentioned below-
"Error: 2012-07-16 23:31:14.83 Code: 0xC020844B Source: Distributor1 TempDistributor1 [152]
Description: An exception has occurred during data insertion, the message returned from the provider is: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Code: 0xC0047022 Source: Distributor1 SSIS.Pipeline Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "TempDistributor1" (152) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (155). 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. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:30:08 PM Finished: 11:31:14 PM Elapsed: 66.156 seconds. The package execution failed. The step failed."
please suggest me what may be the reasons for this failure.
regards
rahul
July 23, 2012 at 12:21 am
It seems that you got timeout issues? Busy server? Network latency/issues? It could be a lot of things that cause this issue.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 23, 2012 at 1:21 am
please suggest me what are the necesary steps to do to avoid such issues?
thanks
rahul
July 23, 2012 at 1:27 am
First of all you should take a look at your environment when the timeout occurs. Is the netwerk down? Did one of the servers crash? Is another process eating away all the memory of the server? You need to establish what causes the timeout, before you can fix the issue.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 23, 2012 at 3:52 am
check the properties of your object for a timeout property, it's probably set to 60 seconds, set it to 0
July 23, 2012 at 4:13 am
which objects property r u talking about (The Job?) can u tell me in detail?
thanks
July 23, 2012 at 4:27 am
the object stated in the error
[ADO NET Destination Input].[TempDistributor1]
i take it it's a Data Flow task...check the properties of the destination
which bit fails in debug?
July 23, 2012 at 7:46 am
This could also be caused by waiting for a lock on all the tables in the query.
Depending on what you are doing with the data you may want to consider a 'dirty read' where you would set the transaction isolation level to 'read uncommitted'.
I would only explore this option if the timeout value modification does not fix the problem.
July 24, 2012 at 3:20 pm
change the time of the job run to see if the problem goes away. Could be you are bumping up against a process already running and your process times out waiting for access to the preoccupied object.
July 25, 2012 at 2:06 am
I have changed the time of job to run let's see what happen...
Thanks for your reply.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply