package scheduled through a job

Question

package scheduled through a job

swatianand83

SSC Eights!

Points: 930
More actions
April 7, 2009 at 11:49 pm

#219890

I have a SSIS package. When executed through the solution, the package executes fine as per the expected functionality.
But when scheduled through a job, the package executes successfully, but no data is getting loaded to the tables.
Any suggestion as what could be the reason for tables not getting populated through the job run.
please reply ASAP. it's urgent.
Thanks

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Aparna-1 SSCrazy Points: 2339 More actions · Answer 1

Are you testing it on the same server? check your configuration files, may be they both are pointing to different servers.

swatianand83 SSC Eights! Points: 930 More actions · Answer 2

Servers are same. the configuration file is in form of a database table.

I have deployed the package also on the server. the deployed package also runs fine whren ran manually....

But the job is still failing... 🙁

suggestions please...!!

Aparna-1 SSCrazy Points: 2339 More actions · Answer 3

May be it is an authentication issue . Please test by creating a simple sp that inserts data into the table and schedule it as a job and test if it works fine. Now call the sp from an sql task (by connecting to your database using the same login credentials) in a sample ssis package without any configuration table and test.

Phil Parkin SSC Guru Points: 246986 More actions · Answer 4

APARNA (4/8/2009)
May be it is an authentication issue . Please test by creating a simple sp that inserts data into the table and schedule it as a job and test if it works fine. Now call the sp from an sql task (by connecting to your database using the same login credentials) in a sample ssis package without any configuration table and test.

If your source data is coming from a file on a network drive, your test should also include importing a sample file from there ...

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

swatianand83 SSC Eights! Points: 930 More actions · Answer 5

How can we check the service account under which Sql agent runs?

I am having a flat file as a source that loads the data to the table. The same operation is happening through teh package also thats been scheduled through the job. So how can i check:

1. Which service account sql agent runs with

2. Access of that service account on the flat file source.

Suggestions please.

Thanks

sriram979 Old Hand Points: 300 More actions · Answer 6

Hi,

Just type services.msc in RUN command and go to SQL Server Agent Service and then right-click properties.

There, go to the tab "Log On". Chevk if it is running on local system account. If it so, then you may need to change it to "This account" and pass your credentials and restart the service.

Then try to run the SQL agent job which executes the SSIS pacakge.

This account which you are providing should have access to the input folder where the input file is being palced, output folder/ database if any.

Hope it helps.

swatianand83 SSC Eights! Points: 930 More actions · Answer 7

swatianand83

SSC Eights!

Points: 930

April 9, 2009 at 3:11 am

#974899

Tried that but of no use. 🙁

Mukti SSCrazy Points: 2826 More actions · Answer 8

Are you using environment variable (indirect configuration) to point to your config table? If yes, then it might be possible the value is not reflecting and still pointing to your dev enviroment.

sriram979 Old Hand Points: 300 More actions · Answer 9

Could you please post the exact error message you are getting? Get the error message either from the Job history or from the log file /the log table if you have logging enabled.