This package has ran fine for 2 months. Now it is doing this error thing. I've read so many articles I'm blue in the face and none of them
I want to know specifically what permission losses would cause this error? Changing protection levels doesn help. Running no protection with
passwords in a config table doesn't work. Nothing works. No matter what changes I make, the same error occurs. This is frustrating. Don't want to read anymore articles about anything. I am looking for a smart savvy person who
understands where these passwords are stored, registry?, a file?, a folder?, a top secret device? What the heck is going on?? SQL Server Agent runs the job that starts the package.
Can't change that. What kind of anamoly would start causing these errors to just start up? Changes in OS permissions? Changes in REGISTRY
View Complete Post