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

Cant run SSIS Package from "SQL Server" Expand / Collapse
Author
Message
Posted Wednesday, March 13, 2013 4:08 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 10:24 AM
Points: 16, Visits: 98
Newbie having an issue. I have job configured in sql agent to run a package on the file system.... Works fine

* uses a proxy account to query some table and output the results to a flat file on network. Proxy has ssisadmin privledges

But when i upload the package to integration services (msdb) and tell the job to access it via "SQL server" is fails. I get this error, Seems like the account permissions arent getting passed.

The owner, run as (proxy) stays the same while i switch back and forth between "File System" & "Sql Server" for testing


Executed as user: domain\user. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 3:04:38 PM Error: 2013-03-13 15:04:38.73 Code: 0xC020200E Source: Export records to text file Output File [2] Description: Cannot open the datafile "". End Error Error: 2013-03-13 15:04:38.73 Code: 0xC004701A Source: Export records to text file SSIS.Pipeline Description: Output File failed the pre-execute phase and returned error code 0xC020200E. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:04:38 PM Finished: 3:04:38 PM Elapsed: 0.234 seconds. The package execution failed. The step failed.
Post #1430662
Posted Wednesday, March 13, 2013 4:31 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 10, 2014 2:17 PM
Points: 124, Visits: 485
Make sure the proxy account has db_ssisoperator role in the msdb.

Post #1430672
Posted Wednesday, March 13, 2013 4:37 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 10:24 AM
Points: 16, Visits: 98
Added

db_ssisltduser
db_ssisoperator

In addition to already having db_ssisadmin, still no worky ?
Post #1430674
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse