December 28, 2010 at 9:13 am
HI All,
We have a job that is failing over the last few days this job was running fine over the last 10 days or so. We have freeze going on and we did not make any changes to the production environment and the package is same as it is, the way it was running before the failure. The one thing I have observed on the server is there is no blocking or deadlock happening on the server and one thing I have been seeing is, there is OS DISK queue length on the server with 50-60% at the time of the execution of the job.
The package is written such a way that its going to other server and exporting some data from the dev server and at this dataflow task I have been seeing this below error:
Executed as user: XXXX\XXXX. ...ion 9.00.4035.00 for 32-bit 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rig
hts reserved. Started: 4:00:02 AM Error: 2010-12-28 04:00:37.74 Code: 0xC0047062 Source: Data Flow Task QA
Permission Data Pull [1] Description: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elaps
ed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlConnection.OnEr
ror(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlExcep
tion exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateO
bject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader
dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDat
aReader.ConsumeMeta... The package execution fa... The step failed.
This is the error I’m getting and this package is executed as SQL Job and this job has 37 steps and this package is at step 1 and this step causing the failure.
The job is schedule to run each day at 4 am except on Saturday and on this Sunday the job ran successfully. Its quiet strange.
The XXXX\XXXX is present in production as well as in the DEV environment and when I looked at the sysdtslog90 folder I don’t see any failure regarding the failure of the job.
Thanks,
Ravi
December 28, 2010 at 11:21 am
The job is timing out. Check the resource utilization and sessions on the server referred to in Step 1.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply