May 2, 2011 at 10:33 pm
Hi
I have an exe which updates the records in table.
When I run this exe through package and double clicks the package, exe run and table gets updated.
But when i run the same package through Sql Job then exe invokes but table does not get updated.
The package are built in Sql Server 2008 R2.
Also, I am trying to edit the command line in the Sql Job, it allows to edit but when I come back again the old command line is visible.
Please help.
Thanks
Kapil
May 3, 2011 at 2:21 am
This is probably a permissions-related issue. I am guessing that when you run it manually, it accesses the db via Windows authentication and your account has the necessary permissions to perform the update, unlike the SQL Agent account.
If this is the case, you'll need to either
1) Upgrade the privileges assigned to the user running the SQL Agent service, or
2) Use an appropriately configured SQL Agent proxy.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 3, 2011 at 3:10 am
Thanks for the reply.
But, this information won't help as the job is already running with some proxy account. And this account has the privileges to access the database.
However, I would like to add more points:
1. This exe is vb6 which refreshed the excel and updates some timestamp in the database.
2. Also I tried with my account by making proxy then also same problem is there.
3. Job invoked this exe as it is visible int the system processes but it immediately went off. This means that exe is invoking but it could not able to process anything. On the same side, when this a single package is executed then the exe invoked and it gets processed also.
Regards,
Kapil
May 3, 2011 at 3:52 am
kaps.manshani (5/3/2011)
Thanks for the reply.But, this information won't help as the job is already running with some proxy account. And this account has the privileges to access the database.
However, I would like to add more points:
1. This exe is vb6 which refreshed the excel and updates some timestamp in the database.
2. Also I tried with my account by making proxy then also same problem is there.
3. Job invoked this exe as it is visible int the system processes but it immediately went off. This means that exe is invoking but it could not able to process anything. On the same side, when this a single package is executed then the exe invoked and it gets processed also.
Regards,
Kapil
Just to be clear:
1) You have created a package in BIDS and can run it manually, in BIDS, logged in as yourself.
2) You have created a SQL Agent job to run the package but the job does not run, even if you use your own credentials to run the job.
Are the above statements correct?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 3, 2011 at 4:13 am
The job runs fine, it execute a package. In the package there is a Execute Process task which executes an exe. This exe is invoked but it does not process anything. And job gets successfully completed.
When the same package is running manually, then exe is invoked and it process everything.
May 4, 2011 at 1:24 pm
if it's in vb6.... do you own the code? If so, you could put some logging into it to tell you which pieces run OK. You're probably going to find a db access routine that's failing due to insufficent rights.
May 5, 2011 at 7:32 am
Uripedes Pants (5/4/2011)
if it's in vb6.... do you own the code? If so, you could put some logging into it to tell you which pieces run OK. You're probably going to find a db access routine that's failing due to insufficent rights.
I found the problem where it is generating error:
its when we try to open the workbook...we are using Excel 2007
objExcel.Workbooks.Open (file name)
But, I dont understand that this problem is not coming when it runs from package only. This problem is coming when job is executed and calls the same package.....
Please help...
May 5, 2011 at 7:39 am
kaps.manshani (5/5/2011)
Uripedes Pants (5/4/2011)
if it's in vb6.... do you own the code? If so, you could put some logging into it to tell you which pieces run OK. You're probably going to find a db access routine that's failing due to insufficent rights.I found the problem where it is generating error:
its when we try to open the workbook...we are using Excel 2007
objExcel.Workbooks.Open (file name)
But, I dont understand that this problem is not coming when it runs from package only. This problem is coming when job is executed and calls the same package.....
Please help...
Is Excel installed on the machine running the package?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 5, 2011 at 11:11 pm
Phil Parkin (5/5/2011)
kaps.manshani (5/5/2011)
Uripedes Pants (5/4/2011)
if it's in vb6.... do you own the code? If so, you could put some logging into it to tell you which pieces run OK. You're probably going to find a db access routine that's failing due to insufficent rights.I found the problem where it is generating error:
its when we try to open the workbook...we are using Excel 2007
objExcel.Workbooks.Open (file name)
But, I dont understand that this problem is not coming when it runs from package only. This problem is coming when job is executed and calls the same package.....
Please help...
Is Excel installed on the machine running the package?
Yes it is installed..office 2007.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply