Viewing 2 posts - 1 through 2 (of 2 total)
May 31, 2018 at 8:23 am
#1992482
Was anyone able to solve this issue?
we are having this same issue with SQL 2016 sp1.
Thank you in advance.
May 30, 2018 at 4:07 pm
#1992411