January 7, 2011 at 12:43 am
It seems like your package include a step like file access or the like.
You have several choices: set up a proxy that's allowed to do it or rewrite your DTS package so it can be run using the permissions the user has (which is equal to remove the file access step, so rather unlikely), allow the user to use xp_cmdshell and rewrite your package (I'd recommend the proxy approach before considering open xp_cmdshell) or write a CLR that will cover the tasks where you need admin permission.
This is all based on the assumption your package deals with file access on a drive. If that's not the case, please briefly describe what the package does.
January 7, 2011 at 7:49 am
Lutz, the problem is that no package executes, it doesn't care which neither that it has. It's something in the configuration of the job or in the properties of the package, because the same package runs perfectly as a job in my sql server agent. Another thing, in the configuration of the package I have to configured as File system.... do you understand me now?. I read many things and documents about that, I even change the Protection Leven in the properties of the package to DontSaveSensitive, but does anything happen.
Thanks for your help.
😉
January 7, 2011 at 8:08 am
If I read your original post correctly, you say that you cannot create a jobstep without a proxy, but a bit later you say that you cannot use a proxy.
Seems like a dead-end to me.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply