October 8, 2015 at 10:21 am
I have an SSIS package that extracts from Excel and loads to Informix db. The package uses a config file. If I run the package manually (package utility) it works just fine. But when I run the SQL Agent job used to execute this package on the same server it fails to load some of the columns. I have found nothing to explain this. Maybe one of you have had the issue.
The job reports no errors.
October 8, 2015 at 10:49 am
garfieldlandry (10/8/2015)
I have an SSIS package that extracts from Excel and loads to Informix db. The package uses a config file. If I run the package manually (package utility) it works just fine. But when I run the SQL Agent job used to execute this package on the same server it fails to load some of the columns. I have found nothing to explain this. Maybe one of you have had the issue.The job reports no errors.
If you change the target to a SQL Server table, does it work OK?
Do the columns which fail to be populated have anything in common? Same datatype, space in column name etc etc – look for any pattern at all.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 8, 2015 at 11:01 am
I am using a config file. The same config file manually as I use when running as SQL Job. The SSIS package moves data to an Informix table. It works perfectly when I execute the package manually but the exact same package fails to load properly when executed from the job.
October 8, 2015 at 11:07 am
garfieldlandry (10/8/2015)
I am using a config file. The same config file manually as I use when running as SQL Job. The SSIS package moves data to an Informix table. It works perfectly when I execute the package manually but the exact same package fails to load properly when executed from the job.
Is the config file stored in a directory that job has rights to?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 8, 2015 at 11:09 am
garfieldlandry (10/8/2015)
I am using a config file. The same config file manually as I use when running as SQL Job. The SSIS package moves data to an Informix table. It works perfectly when I execute the package manually but the exact same package fails to load properly when executed from the job.
As you have chosen to completely ignore my questions, I shall ignore your responses.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 8, 2015 at 11:09 am
Yes, the job has no problem running. It just doesn't load the second column. There are two columns, col1 int, Col2 varchar(80).
October 8, 2015 at 11:11 am
1. It loads to Informix not sql server.
2. It has 2 columns, only 1 doesn't load. One is int and one is varchar.
Keep in mind it works when manually executed.
October 8, 2015 at 11:16 am
garfieldlandry (10/8/2015)
Yes, the job has no problem running. It just doesn't load the second column. There are two columns, col1 int, Col2 varchar(80).
Which question are you answering here? Remember, we're not mind readers.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
October 8, 2015 at 11:25 am
Alvin Ramard (10/8/2015)
garfieldlandry (10/8/2015)
I am using a config file. The same config file manually as I use when running as SQL Job. The SSIS package moves data to an Informix table. It works perfectly when I execute the package manually but the exact same package fails to load properly when executed from the job.Is the config file stored in a directory that job has rights to?
OK, let me try again. I never used this forum and I thought I was replying directly so please excuse any confusion.
To your question, yes, the job has the rights to the config file.
October 8, 2015 at 11:28 am
If you change the target to a SQL Server table, does it work OK?
Do the columns which fail to be populated have anything in common? Same datatype, space in column name etc etc – look for any pattern at all.
Apologies if you felt slighted or ignored.
1. I have not tried changing the target table because the package works manually.
2. The two columns are of different data type. Only one fails to load under SQL job
October 8, 2015 at 11:43 am
garfieldlandry (10/8/2015)
If you change the target to a SQL Server table, does it work OK?
Do the columns which fail to be populated have anything in common? Same datatype, space in column name etc etc – look for any pattern at all.
Apologies if you felt slighted or ignored.
1. I have not tried changing the target table because the package works manually.
2. The two columns are of different data type. Only one fails to load under SQL job
Apology accepted. As you have no idea what the problem may be (and neither do I), my suggestions were merely an attempt to try to narrow down where the error is happening. When you run the job manually, are you executing it on the server or on a different PC? If on a different PC, could your Informix driver be a different version?
I think that Alvin was more likely to be on to something than I. 95% of the time, when a job works manually but not in SQL Agent, the reason is down to permissions (though you should have got an error).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 8, 2015 at 11:50 am
Phil Parkin (10/8/2015)
garfieldlandry (10/8/2015)
Apology accepted. As you have no idea what the problem may be (and neither do I), my suggestions were merely an attempt to try to narrow down where the error is happening. When you run the job manually, are you executing it on the server or on a different PC? If on a different PC, could your Informix driver be a different version?
I think that Alvin was more likely to be on to something than I. 95% of the time, when a job works manually but not in SQL Agent, the reason is down to permissions (though you should have got an error).
Yes, I am thinking maybe some sort of driver issue. I checked permissions left and right and it does work if executed using the Package Utility. I am hoping someone has heard of or had this issue dealing with Informix or perhaps DB2.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply