SSIS Package stops running due to "Digital Signature not trusted"

  • I am new to SSIS. I am building a package incrementally that has about two dozen "Execute SQl" tasks. After building each one, I pressed F5 to debug.

    Up until the last one I created, I got a green indicator indicating success. After the last one, I clicked on it and clicked "execute task". Five minutes later, the task is still yellow. The error list says "Error loading <my project>.dtsx: The digital signature is valid; however the signer is not trusted and therefore, authenticity cannot be guaranteed."

    It is now an hour later. There is no indication of a problem on the Progress tab. The task is still yellow.

    If I disable the one task and press the F5 button, everything but the subject task turns green. The SQL in the task runs fine in SSMS.

    Can anyone give me an idea of what is happening and how to fix it? It is driving me crazy: :w00t:

    Thanks ahead of time!

  • Not sure if this is what you are encountering but I ran into a problem similiar to yours and this was the cause.

    The package we where dealing with had a connection with a stored password. The password gets stored with the current security context. So if you are logged in as Tom on your machine it will work as long as you are logged in as Tom. However on the server the job executes as the service account and the security context has changed. So in the case of the stored password I had to edite the SSIS on the server under the same security context as the service accout so that it would work and not throw the error.

    Dan

    If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.

  • Thanks for your input, Dan.

    I don't think this is the case. All of this happened while logged on as the same user, same server, and same PC. When I disable the one task, everything runs OK. When I enable the task, I get the error ... it just stops execution 10 seconds into the process. I wrote the task that is the problem. I opened a new ExecuteSQL task and pasted the code in. Nothing else.

    Very bizarre ... :w00t:

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply