The following is happing in SQL 2008 R2..
I have a user that connect to SQL using a SQL account. I thought I'd granted this SQL account everything it needed, but I've missed something.
When he tries to create a new job, or edit an existing job this is what happens. When he creates a step that will execute a SSIS package, accessed via the file system, he can select a package. When he attempts to add a configuration file, he has no access to the file system.
Does SQL use one set of credentials to access the SSIS package, and another for the configuration files? He can't even see any drives listed when he attempts to do this.
