November 25, 2019 at 12:25 pm
when i ran the package through sql agent job it got failed but i did not find any information in job history
Executed as user: . Started: 11:59:55 AM Finished: 12:00:43 PM Elapsed: 47.281 seconds. The package execution failed. The step failed.
How can we trouble shoot
November 25, 2019 at 12:42 pm
Hello,
I suppose you have access to the package, the only way to find out is downloading it and executing it and while you are at it, you can actually set up some logging for it inside Visual Studio.
November 25, 2019 at 1:52 pm
when i ran the package through sql agent job it got failed but i did not find any information in job history
Executed as user: . Started: 11:59:55 AM Finished: 12:00:43 PM Elapsed: 47.281 seconds. The package execution failed. The step failed.
How can we trouble shoot
The SQL Agent job history is not the best place to look, as you have seen. Instead, check the All Executions report in the SSISDB catalog.
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
November 25, 2019 at 2:11 pm
Its an sql 2016 developer edition 64 bit i did not find any SSIS DB i did not get any info in integration service catalogs
November 25, 2019 at 6:42 pm
How are you deploying your packages to the server? Are you using the project deployment model? If not, I suggest that you consider upgrading to it.
Please read here for more information.
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply