| Author |
Topic |
|
mufasa
Yak Posting Veteran
62 Posts |
 Posted - 2003-09-08 : 09:55:42
|
| I would like to know if someone could tell me why, that when I run a local package in DTS, it runs fine, when I schedule it as a job it always fails.I am part of the sa, and the dbo.I have other jobs that run but can not understand why this one will not.ThanksMufasa |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-09-08 : 10:00:17
|
| More than likely, down to NT file permissions.. If you are exporting data to, for example, a remote directory, then the NT user that the SQL Agent service is running as must be able to access the remote directory.-------Moo. :) |
 |
|
|
mufasa
Yak Posting Veteran
62 Posts |
Posted - 2003-09-08 : 10:02:29
|
| If that were the case, then I should not be able to execute the package in DTS?Mufasa |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-09-08 : 10:04:41
|
| No, because when you run it manually under DTS it runs as the currently logged in user. It is only when scheduled that it runs under the service login. Hence the difference.-------Moo. :) |
|
|
|
mufasa
Yak Posting Veteran
62 Posts |
Posted - 2003-09-08 : 10:08:21
|
| OK, but when I execute the job inside Jobs section, it still fails, listing me as the user trying to run the job.. |
|
|
|
rharmon
Starting Member
41 Posts |
Posted - 2003-09-08 : 10:11:03
|
| When you set yourself to the job owner, that gives the job privlages within the SQL server itself (the privlage to run the DTS package), however, the dts package is still running as the sqlagent service account which may or may not have permissions to all of the resources outlined in the package. |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-09-08 : 10:27:23
|
quote:
OK, but when I execute the job inside Jobs section, it still fails, listing me as the user trying to run the job..
In that case, what is the error message? Right click on the job, choose show history, then tick the box to show step details and tell us the error.-------Moo. :) |
|
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-09-08 : 10:33:31
|
quote:
Originally posted by mr_mist
quote:
OK, but when I execute the job inside Jobs section, it still fails, listing me as the user trying to run the job..
In that case, what is the error message? Right click on the job, choose show history, then tick the box to show step details and tell us the error.-------Moo. :)
Yeah, I go for what's the error...But my blind vote is for....When you run DTS manually it looks at you and your mapped drives. When it's scheduled, it looks at the servers mapped drives.If the mapped drives are not mirrored (so your mapped drives look like the servers mapped drives) then it'll fail because it can't find the file...That's my guess...But the error message would be a big help...Brett8-)SELECT @@POST=NewId()That's correct! It's an AlphaNumeric! |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-09-08 : 11:14:09
|
| TBH, if you're intending scheduling a job, you'll need to use the full thingumy path to the network share, and not a mapped drive letter which are only relevant to a login. Yah.-------Moo. :) |
|
|
|
mufasa
Yak Posting Veteran
62 Posts |
Posted - 2003-09-08 : 11:19:20
|
| Hi Well it was a problem with permissions, for some reason I could not add the SQL_Service user from the SQL Server to the group that had permission to the folder that I was importing the information.Our DC has a SQL_Service user, but it is not the same one from the SQL_Server. We are running a mixed mode of NT4(DC) and Server 2K(SQL).I'm sure it could have been resolved easily if we had Active Directory.I finally created a folder on the SQL Server and created a short-cut in the IS Directory to this folder.It worked ;)This was the message from the job history:The job failed. The Job was invoked by User Domain-Name\me.user. The last step to run was step 1 (Excel Employ).Thanks for the help.Mufasa |
|
|
|
|
Failing Jobs