The text "error in destination connection that SQL is Lock" doesn't sound familiar, but I am assuming you are paraphrasing. It helps to post the exact error message.
Nonetheless, getting an error message is expected. Because you did not store passwords (which is OK), you will now need to open the conenction Managers node in BIDs and give the password/username to each connection that needs it so the connection(s) can be established.
it may be that you're using sql authentication for destination. in such cases do not store sensitive will not store password details for sql account in package. If thats case, you've to use package configuration to store the senstive details and pass it onto package at runtime