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 ««123»»

SQL Server Agent : Job Failure Expand / Collapse
Author
Message
Posted Monday, March 31, 2014 10:28 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
elhelalaoui (3/30/2014)
I'm still having this error : Could not get proxy data for proxy_id = 11


When creating the credential were you using DOMAIN\USERNAME or just USERNAME ?

--
SQLBuddy
Post #1556585
Posted Monday, March 31, 2014 12:44 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
I used TheNameOfTheComputer\Administrateur
Thanks sqlbuddy123 for your support
I'm in waiting
Post #1556648
Posted Monday, March 31, 2014 2:24 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
elhelalaoui (3/31/2014)
I used TheNameOfTheComputer\Administrateur
Thanks sqlbuddy123 for your support
I'm in waiting


You are welcome, elhelaloui. Could you import the package into MSDB, select the SSIS package in the job step and then execute ?

Also please post the error message that you see in the job history ..

--
SQLBuddy
Post #1556703
Posted Wednesday, April 2, 2014 3:20 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
I've imported the package onto MSDB and here what i'm having now in both cases :
Case 1 : Running the step with the proxy :
errors ==> Job outcome : The job failed. The Job was invoked by User ServerName\Administrateur. The last step to run was step 1 (Test_Proxy2). Test_Proxy2 : Unable to start execution of step 1 (reason: Could not get proxy data for proxy_id = 11). The step failed.
Case 2 : Using SQL Agent Service Account :
errors ==> Job Outcome : The job failed. The Job was invoked by User ServerName\Administrateur. The last step to run was step 1 (Test_Proxy2). Test_Proxy2 : Executed as user: DomaineName\Système. The package execution failed. The step failed.

| Test_Proxy2 is the name that I gave to the step. |

Thanks
Post #1557714
Posted Thursday, April 3, 2014 9:01 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
elhelalaoui (4/2/2014)
I've imported the package onto MSDB and here what i'm having now in both cases :
Case 1 : Running the step with the proxy :
errors ==> Job outcome : The job failed. The Job was invoked by User ServerName\Administrateur. The last step to run was step 1 (Test_Proxy2). Test_Proxy2 : Unable to start execution of step 1 (reason: Could not get proxy data for proxy_id = 11). The step failed.
Case 2 : Using SQL Agent Service Account :
errors ==> Job Outcome : The job failed. The Job was invoked by User ServerName\Administrateur. The last step to run was step 1 (Test_Proxy2). Test_Proxy2 : Executed as user: DomaineName\Système. The package execution failed. The step failed.

| Test_Proxy2 is the name that I gave to the step. |

Thanks


Check 3 things :

1. If the proxy got created successfully.

2. Package protection level of the SSIS package.

3. Check if you see any error messages in the SQL Agent error log when the job was run.

--
SQLBuddy


Post #1558033
Posted Monday, April 7, 2014 2:00 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
1- The proxy i created is based on a credential attached to my local admin account, wich have full access to my databases.
2- The Protection level of the package is on "DontSaveSensitive".
3- In the Job history I'm getting only the errors above
Post #1559261
Posted Saturday, April 12, 2014 8:50 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
Is there any hope to resolve this issue ?
Post #1561210
Posted Saturday, April 12, 2014 3:19 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
First try running the job using and see if it works then we can schedule it as a job ..

USE msdb ;
GO

EXEC dbo.sp_start_job N'Job_Name' ;
GO


--
SQLBuddy
Post #1561242
Posted Monday, May 5, 2014 9:19 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
Hello,
Sorry for the delay, I had personal difficulties so I could'nt do this test.
I've just launched that query and it appears that it goes well (Message : Job 'Test' started successfully.), but no email was generated
Must I du something else ?
Thanks.
Post #1567562
Posted Friday, May 9, 2014 1:01 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
elhelalaoui (5/5/2014)
Hello,
Sorry for the delay, I had personal difficulties so I could'nt do this test.
I've just launched that query and it appears that it goes well (Message : Job 'Test' started successfully.), but no email was generated
Must I du something else ?
Thanks.


Create a job and within a TSQL Job step use this command

USE msdb ;
GO

EXEC dbo.sp_start_job N'Job_Name' ;
GO

Let the job run under your account i.e Owner of the job ..

--
SQLBuddy
Post #1569431
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse