SSIS Log Provider fails to write log file

[lnidba]

We have a series of jobs which report success; however the Log Provider fails
to write to the log file. "The SSIS logging provider has failed to open the
log. Error code: 0x80070005. Access is denied." There was a security issue
which did not allow the job to write to the directory, so that is correct.

However it also said "The package execution returned DTSER_SUCCESS (0)." We
were not alerted to the missing log file and so we had no way to troubleshoot
the package after a failure.

Is there a way to configure the package to report a failure of any kind?

[Uri Dimant]

SQL Server Agent runs under account that does not have access to the folder?

Post by lnidba
We have a series of jobs which report success; however the Log Provider fails
to write to the log file. "The SSIS logging provider has failed to open the
log. Error code: 0x80070005. Access is denied." There was a security issue
which did not allow the job to write to the directory, so that is correct.
However it also said "The package execution returned DTSER_SUCCESS (0)."
We
were not alerted to the missing log file and so we had no way to troubleshoot
the package after a failure.
Is there a way to configure the package to report a failure of any kind?

[lnidba]

Yes, that was the original issue and has been corrected. My question is why
the package returned a status of "Success" when one of the components of the
package failed. I would prefer to get a message of failure if the log was
not written. As it is, this happened for a few months without us knowing
because the package was reporting success. Is there a way to configure the
package so that it will report failure, no matter how small the error may be.
Thank you.

Post by Uri Dimant
SQL Server Agent runs under account that does not have access to the folder?

Post by lnidba
We have a series of jobs which report success; however the Log Provider fails
to write to the log file. "The SSIS logging provider has failed to open the
log. Error code: 0x80070005. Access is denied." There was a security issue
which did not allow the job to write to the directory, so that is correct.
However it also said "The package execution returned DTSER_SUCCESS (0)."
We
were not alerted to the missing log file and so we had no way to troubleshoot
the package after a failure.
Is there a way to configure the package to report a failure of any kind?