August 27, 2024 at 2:51 pm
We're upgrading from SQL Server 2016 to 2022. The SSIS package project level connections don't work as expected. One queries the server as an anonymous logon instead of the domain account associated with the SQL Server Agent. One even affects both the original server and the new one to which it is pointed. I have tried resetting databases and servers. I created a small project moving data among all the servers and deploying it directly with project level connections and the project works as expected. The code for the connections that work and don't work is materially the same. I could probably just create new connections alongside the old and manually change them. But I wanted to ask if anyone had run into this and what solution worked (or didn't work) for you.
August 27, 2024 at 5:54 pm
The anonymous login is likely due to either incorrect SPN configuration or delegation being disabled. At least that is my guess as we can't see your system.
I suppose the next question is are you doing a migration upgrade or an in place upgrade? If it is a migration install, did you backup and restore the master key and any certificates? If not I believe all encrypted data (such as connection information) is lost during the migration. Mind you, it's been ages since I've done an SSIS upgrade. Others may have better/different advice.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply