SSIS runs in debug but not from job

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » SSIS runs in debug but not from job

SSIS runs in debug but not from job

Rate Topic

Display Mode

Topic Options

Author

Message

tanyadavidg

Posted Sunday, September 09, 2012 7:25 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, September 10, 2012 4:17 AM
Points: 1, Visits: 6

We have this SSIS where one of its components, reading a flat file and writing to a database table, runs fine when I execute the package in VS (debug) but when I run it using a job this specific step fails on the error:

Error: 2012-09-09 15:31:58.43
Code: 0xC0204026
Source: Copy date from Folder file into FolderTable Save the file in the database [14]
Description: The metadata for "[dbo].[FolderTable]" cannot be retrieved. Make sure the object name is correct and the object exists.
End Error
Error: 2012-09-09 15:31:58.43
Code: 0xC004706B
Source: Copy date from Folder file into FolderTable SSIS.Pipeline
Description: "component "Save the file in the database" (14)" failed validation and returned validation status "VS_ISBROKEN".
End Error

I've looked around and tried various suggestions fixing the problem,like redefining the column and its length, changing the ValidExternalMetadata.

Didn't help.
What could help me with the problem ?
How come it runs fine within VS but from a job it fails ?

Thanks
David

Post #1356472

robert.gerald.taylor

Posted Sunday, September 09, 2012 9:30 PM

Right there with Babe

Group: General Forum Members
Last Login: Today @ 11:10 AM
Points: 740, Visits: 785

I'd guess a permissions issue. What account is the SQL Agent job running under? Does that user have permissions to see the folder where the flat file is?

HTH,
Rob

Post #1356543

Brandie Tarvin

Posted Monday, September 10, 2012 5:56 AM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 10:58 AM
Points: 6,655, Visits: 5,678

We've had the same issue due to permissions and we've had the same issue due to missing or out of date dll files on our server.

Was this package developed by you? Are there any special "accessory" files (like dlls, webservice calls, etc) that are required to go along with it that perhaps don't live on the server?

What account is running the job? Does it have access to both the database and the file share location?

Brandie Tarvin, MCITP Database Administrator, MCDBA, MCSA

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Post #1356676

Ignacio A. Salom Rangel

Posted Monday, September 10, 2012 10:57 AM

Hall of Fame

Group: General Forum Members
Last Login: Friday, May 10, 2013 2:49 PM
Points: 3,051, Visits: 1,356

Have you check the permissions of the account that runs the SQL Server Agent as already suggested? In order to be sure it is a permission issue you can also try to set your account to run the SQL Server Agent on a development Server and run the package from there.

My blog

Post #1356891

« Prev Topic | Next Topic »

Permissions