The backup job generated by the tool is running normally for many months, but was told by another database engineer that it was not running for a while, so it was disabled. The history log is as follows:
There is a key in the error prompt, and so on, but I have not generated a key or something. The cause is that the protection level specified by the package is incorrect.
Solution:
1. log on to the server, click Register Server, and find the SSIS server.
2. Select the faulty package
3. Select the export package. By default, the user key is used to protect sensitive data at the protection level. You can choose to rely on the server .... You can.
4. Rename the exported new package
5. Locate the faulty job on the SQL Agent and point it to the new package path again. Delete the problematic package and run the job.
Although there are related fault handling instructions on the Internet, it is still quite good to run it by yourself.
The next time the old lady goes on a business trip, who will be down to the job of the old lady and kill him?