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 Sunday, March 23, 2014 6:37 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
Hello,
I wish to put the result of a query in Excel then send it to a number of persons at a specified moment. I've started by the configuration of all this on a SSIS package, till then everything is all right, all steps are going well. The problem appears when I tri to schedule this work via the SQL Server Agent.. You'll find below the steps i've done :

1- On the general part, I name the job and put the account sa as owner.
2- On the Steps part, i create a new step and then I set :
2.1 the name of the step.
2.2 Run AS = SQL Agent Service Account
2.3 On the general tab, I put the source of the package as a System File, I browse the package, then i save all.

When I tri to execute the Job, I receive this error (On job history) : "The JOB Failed. The Job was Invoked by user NomDuServeur\Administrateur. The last step to run was Step 1." ==> "Executed as user : MonDomaine\Système. The package executon failed. The step failed." :|

FYI : I'm using SQL Server 2005 with the OS Windows Server 2008 R2 64bit.

Could you help please ?

Thanks and regards.
Post #1553810
Posted Sunday, March 23, 2014 11:46 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:56 AM
Points: 2,603, Visits: 2,061
There are two approach:

one is you can use notification feature of the job to send e-mail notification when job completes i.e. success or failure.

Second is you periodically check the job history table in MSDB database to send result via e-mail attachment.

HTH


---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #1553862
Posted Tuesday, March 25, 2014 2:34 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
Thanks free_mascot.
The problem is that all my jobs never succeed
Do you have any idea about that error ?
Post #1554685
Posted Wednesday, March 26, 2014 12:17 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, July 21, 2014 2:56 AM
Points: 2,603, Visits: 2,061
Check the permission. Is there any permission issue? All jobs are failing with same error?

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #1554782
Posted Wednesday, March 26, 2014 12:52 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 9:57 AM
Points: 1,194, Visits: 2,234
Create a credential with your ID and a SSIS agent proxy with that credential. Then run the job using that credential.

http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/

--
SQLBuddy
Post #1555141
Posted Wednesday, March 26, 2014 3:50 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
Thanks free_mascot, thanks sqlbuddy123. All my jobs are going with the same error.
I've just tried the solution of the proxy, and getting this error now : Could not get proxy data for proxy_id = 10
Please help I'm executing all my packages manually everyday
Thanks
Post #1555198
Posted Wednesday, March 26, 2014 5:08 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 9:57 AM
Points: 1,194, Visits: 2,234
elhelalaoui (3/26/2014)
Thanks free_mascot, thanks sqlbuddy123. All my jobs are going with the same error.
I've just tried the solution of the proxy, and getting this error now : Could not get proxy data for proxy_id = 10
Please help I'm executing all my packages manually everyday
Thanks


Change the job owner to SQL Agent Service account or your ID and run it. Lets try that ..

--
SQLBuddy
Post #1555217
Posted Thursday, March 27, 2014 6:49 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
It Doesn't working, I'm getting the first error now
Post #1555399
Posted Thursday, March 27, 2014 8:07 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 9:57 AM
Points: 1,194, Visits: 2,234
elhelalaoui (3/27/2014)
It Doesn't working, I'm getting the first error now


Did you run it like this ...

Change the job owner to SQL Agent Service account or your ID and run the job step as SSIS Proxy that you created before.

--
SQLBuddy
Post #1555445
Posted Sunday, March 30, 2014 4:10 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 3:30 PM
Points: 12, Visits: 103
I'm still having this error : Could not get proxy data for proxy_id = 11
Post #1556269
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse