Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS package scheduled as job fails after about 20-40 minutes executing Expand / Collapse
Author
Message
Posted Wednesday, April 23, 2008 8:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 21, 2010 3:07 PM
Points: 1, Visits: 33
I have SSIS Package scheduled to run as a job. This job has been running sucessfully for months. Recently, the package is failing after 20-40 minutes executing. If I start the job from SQL Server Agent myself, it runs sucessfully. Every failure errors out at different spot in the package. I am totally at a loss why this job would suddenly quit working from a schedule.

Here is the error log from today:


Step ID 1
Server SQL02
Job Name Update Report Manager
Step Name Update database
Duration 00:40:54
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: NCF\sqlservice. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:50:00 AM Error: 2008-04-23 07:30:02.57 Code: 0x80004005 Source: Data Flow Task 1 DTS.Pipeline Description: Unspecified error End Error Error: 2008-04-23 07:30:02.58 Code: 0xC0208265 Source: Data Flow Task 1 lot [2099] Description: Failed to retrieve long data for column "restriction_memo". End Error Error: 2008-04-23 07:30:02.60 Code: 0xC020901C Source: Data Flow Task 1 lot [2099] Description: There was an error with output column "restriction_memo" (4000) on output "OLE DB Source Output" (2109). The column status returned was: "DBSTATUS_UNAVAILABLE". End Error Error: 2008-04-23 07:30:02.60 Code: 0xC0209029 Source: Data Flow Task 1 lot [2099] Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "output column "restriction_memo" (4000)" failed bec... The package execution fa... The step failed.


Here is the error log from yesterday

Step ID 1
Server SQL02
Job Name Update Report Manager
Step Name Run SSIS
Duration 00:46:09
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: NCF\dmatthews. ...sion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:45:00 AM Error: 2008-04-22 07:29:23.66 Code: 0xC0202009 Source: Data Flow Task 1 address [76] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. End Error Error: 2008-04-22 07:29:23.68 Code: 0xC0047038 Source: Data Flow Task 1 DTS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "address" (76) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. End Error Error: 2008-04-22 07:29:23.68 Code: 0xC0047021 Source: Data... The package execution fa... The step failed.

Post #489297
Posted Wednesday, April 23, 2008 9:52 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,661, Visits: 23,078
You need to configure logging and get the entire error messages. Everything you need is being covered up by the elipsis (...) areas of what you posted.

I would guess that you are either getting some bad data that is being fixed before you re-run the package, or you have some other activity running during the schedule that is conflicting with your package.

However, you need the actual error messages.
Post #489389
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse