So appears that’s the ODBC drivers in the click-to-run Office 2016 doesn’t install properly or it’s possible it’s incorrectly setup by default. I haven’t figured that part out yet but it was causing one of my clients trouble.
They were getting the following error when refreshing the data in some of their spreadsheets after their Click-to-Run O365 installs updated to Office 2016 from Office 2013.
The Infosec Noob 