Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Not Working Under Credential Expand / Collapse
Author
Message
Posted Tuesday, January 8, 2013 10:17 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, May 12, 2014 8:57 AM
Points: 56, Visits: 290
Hi guys

Hoping someone can point me in the right direction.

I have an SSIS package that reads in a number of flat files and dumps the data into database tables. This is running as a SQL Job (SQL 2008 R2 server) under a credential which has db_owner access to the db it connects to. The credential has the necessary access to the file path location. However, the job doesn't run under the credential.

If I open the package in visual studio under my login and run it, it runs fine, if I open it as the credential the package runs fine but no error is dropped into the tables. The package step itself appears with a green progress indicating that there were no errors.

The flat file connection string is set by an expression, a variable contains the location of the file path.

When I run the package in the job, the job fails with the error "The file name property is not valid. The file name is a device or conatins invalid characters".

This doesn't make sense if the package runs under my account. This would appear to be a permissions issue but I've given the credential sa access on the db server and given it full access to the file location.

Just as a side note, the package was initially a 2005 package but was upgraded to 2008 as part of a project. In the test environment everything with the package running as the newly created credential ran fine
Post #1404363
Posted Wednesday, January 9, 2013 7:19 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, May 12, 2014 8:57 AM
Points: 56, Visits: 290
All down to permissions alright, permission had to be explicitly allocated at the root folder into a read/write group.

Fairly misleading error message when ran as a job, also seems very strange that the account was able to run the first step that renamed the files but couldn't run the step to open the file and copy the data.
Post #1404774
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse