March 4, 2009 at 9:05 am
Hi all
So I've deployed my package to the SQL server and I've tried to run it via job. There is only one step in the job and it is to exectute the SSIS package.The Type is set to 'SQL Server Integration Services Package'. Run as is set as: 'SQL Agent Service Account'. The user (mine) that is scheduling the job or manually running the job has ful admin permissions. In Data sources I have the one DB connection and the HTTP connection manager ticked.
When I run it manually or via a schedule I get the same error:
03/04/2009 15:26:06,Darwin,Error,0,MACHINE,Darwin,(Job outcome),,The job failed. The Job was invoked by Schedule 48 (Test Run). The last step to run was step 1 (Run Darwin).,00:00:00,0,0,,,,0
03/04/2009 15:26:06,Darwin,Error,1,MACHINE,Darwin,Run Darwin,,Executed as user: MACHINE\SYSTEM. The process could not be created for step 1 of job 0x09CC112CDDF7F94BA0D6CFA373327ED1 (reason: 2). The step failed.,00:00:00,0,0,,,,0
As you can see, it doesn't really give me a description as to whats happened "(reason: 2)".
Anyone got any ideas at all?
Thanks
G
March 4, 2009 at 9:45 am
Check that the SQL Agent service has sufficient privileges to run this package - maybe a privileged domain account is needed and currently it is set to local system ...
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
March 4, 2009 at 10:45 am
Okay, I tried using a proxy:
First I created a new credential using my user as an identity. Then I created a proxy using that credential and ticked the SQL Server Integration Services Pakaged was ticked in the Subsystem Section.
Once the proxy was created, in the job, I selected it to run as the proxy that I had created.
This seems to sorta work, but the job is failing now for other reasons.
I decided to connect to the SQL Server and run the SSIS package manually via a remote desktop connection. Seems it is failing cause it can't find .xsd files on the file system. My mistake for not including them, but now after looking at it, is my only solution to copy .xsd files over to the server, or point the XML Source component to look in a shared directory that both my development machine and the server can see?
There doesn't seem to be a way to read the .xsd file from a variable or pull the data from the DB. What are my options for this sort of thing?
Thanks
G
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply