Viewing post 1 (of 1 total)
Note that when I received this error when trying to run an Import from within SSMS, I ran a repair on SQL 2016, and that fixed it.
From the...
January 20, 2017 at 4:03 pm
#1924166