Before I start, unfortunately I do not have access to the package design as the person who created this package has left and was stored locally on his office computer. However, this package is called "GenericReportExtract", and, as you can probably gather, was designed to be a multipurpose SSIS package which creates an SSRS report and then emails an Excel version to the recipients the report was designed for.
This package has worked perfectly for every single Job it has been used by except one, where, for some reason, will say the Job has run without any errors, but when you look in the output path of this report, it doesn't exist.
But, when I run it manually (i.e. right click job > Start Job at Step), the report is actually produced and you can see it in the output path for the report.
The job itself was run under Admin\SQL_Services, so I thought it maybe didn't like the owner and I changed it to under my log-in, seeming as it worked fine when I manually ran it. However, the next time the job was scheduled to run, the recipient still didn't receive the report and still didn't appear in the output path.
I do not wish to create a new package as there are too many packages that rely on this package, and I suspect it's something to do with the job. It's worth noting that this job ran successfully for about a year until last Christmas, and then in January it stopped doing what it was supposed to do, even though the Job history says it's working fine. I have been manually running the job since, but it does need attending to now.
Aucun commentaire:
Enregistrer un commentaire