SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Agent : Job Failure


SQL Server Agent : Job Failure

Author
Message
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6078 Visits: 2243
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
elhelalaoui
elhelalaoui
SSC Veteran
SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)

Group: General Forum Members
Points: 204 Visits: 103
I used TheNameOfTheComputer\Administrateur
Thanks sqlbuddy123 for your support
I'm in waiting :-)
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6078 Visits: 2243
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
elhelalaoui
elhelalaoui
SSC Veteran
SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)

Group: General Forum Members
Points: 204 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 :-)
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6078 Visits: 2243
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
elhelalaoui
elhelalaoui
SSC Veteran
SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)

Group: General Forum Members
Points: 204 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 Sad
elhelalaoui
elhelalaoui
SSC Veteran
SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)

Group: General Forum Members
Points: 204 Visits: 103
Is there any hope to resolve this issue ? Unsure
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6078 Visits: 2243
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
elhelalaoui
elhelalaoui
SSC Veteran
SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)SSC Veteran (204 reputation)

Group: General Forum Members
Points: 204 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 Ermm
Must I du something else ?
Thanks. :-)
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)SSCertifiable (6.1K reputation)

Group: General Forum Members
Points: 6078 Visits: 2243
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 Ermm
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search