![Microsoft ODBC Driver 11 for SQL Server: Named Pipes Provider: Could not open a connection to SQL Server - Database Administrators Stack Exchange Microsoft ODBC Driver 11 for SQL Server: Named Pipes Provider: Could not open a connection to SQL Server - Database Administrators Stack Exchange](https://i.stack.imgur.com/GZ9dN.png)
Microsoft ODBC Driver 11 for SQL Server: Named Pipes Provider: Could not open a connection to SQL Server - Database Administrators Stack Exchange
![Connect to an ODBC Data Source (SQL Server Import and Export Wizard) - SQL Server Integration Services (SSIS) | Microsoft Learn Connect to an ODBC Data Source (SQL Server Import and Export Wizard) - SQL Server Integration Services (SSIS) | Microsoft Learn](https://learn.microsoft.com/en-us/sql/integration-services/import-export-data/media/create-new-odbc-data-source.png?view=sql-server-ver16)
Connect to an ODBC Data Source (SQL Server Import and Export Wizard) - SQL Server Integration Services (SSIS) | Microsoft Learn
![FIXED: Installing Microsoft ODBC Driver 17 for SQL Server produces "A previous installation required a reboot of the machine for changes to take effect." - Access DB Gurus FIXED: Installing Microsoft ODBC Driver 17 for SQL Server produces "A previous installation required a reboot of the machine for changes to take effect." - Access DB Gurus](https://www.accessdbgurus.com/wp-content/uploads/2020/07/1146955.jpg)
FIXED: Installing Microsoft ODBC Driver 17 for SQL Server produces "A previous installation required a reboot of the machine for changes to take effect." - Access DB Gurus
After upgrading from Tableau Desktop 2019.4 to 2021.2, I received the error attached in a workbook saved under 2019.4. I uninstalled both versions of Desktop and the ODBC driver and reinstalled 2021.2
![FIXED: Installing Microsoft ODBC Driver 17 for SQL Server produces "A previous installation required a reboot of the machine for changes to take effect." - Access DB Gurus FIXED: Installing Microsoft ODBC Driver 17 for SQL Server produces "A previous installation required a reboot of the machine for changes to take effect." - Access DB Gurus](https://www.accessdbgurus.com/wp-content/uploads/2020/07/image-4.png)