Evan Cutler
asked on
why does ssis transfer object stage return smo failure
I am trying to copy a database using SSIS Transfer SQL Server Objects Task.
I hit test connection and prove that I have the right server name and password.
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "An exception occurred in SMO.".
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Value cannot be null.
Parameter name: server".
I hit test connection and prove that I have the right server name and password.
I guess you're transferring a NULL value to a field that doesn't accept nulls.
The error is stating that the server name is null, not one of the fields. I just ran into this error also after using this method for 10 years without incident.
ASKER
Thanks Kvoolk....how did you solve it?
I haven't been able to solve it. My best guess is that it is a bug with SSDT 2017, which I recently upgraded to and never had this issue until now. As a workaround, I guess I am going to have to code up the transfer logic in SQL.
ASKER
ok. guess we're waiting for upgrades in SSDT 2017. Thanks!
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.