title: SQL Server connection error - Data source name not found and no default driver specified
body: <p>When running a third party developed EXE located on the shared folder of Windows Server 2012 R2, which connects to SQL Server 2012 Express, the following error occurs:</p>
  
  <blockquote>
    <p>[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.</p>
  </blockquote>
  
  <p>When the EXE is 'Run as Administrator' it works fine. But this application interfaces with Office and other programs, so running as administrator puts it into protected memory space that conflicts with other applications. I need it to open normally, as before.</p>
  
  <p>This error has only occurred since client workstations had Windows 10 1803 and higher installed. Bizarrely, workstations that updated to 1803 and higher are unaffected. Only on new installs has the problem occurred.</p>
  
  <p>There was something about 1803 which changed the network stack, client side, that caused a lot of different problems for SQL connections and I have seen a hundred different solutions but none work in our case.</p>
  
  <p>Client machines connect to Server 2012 using domain login accounts. Each domain user account is given local admin rights and full administrator rights. The client workstations are normal Windows 10 Pro install with ESET antivirus. When testing the ODBC connection, it is successful and works. Only when running the program does the error occur.</p>
  
  <p>On the Server side I have.... Enabled Named Pipes, Disabled and Removed SMB1.0</p>
  
  <p>So what is going on here? Why from 1803 on must we run as administrator to get a connection?</p>