title: Can't connect to my database (RDS) using mySQL and EF 5
body: <p>I have the following problem:</p>
  
  <p>I want to start my WPF application from an EC2 instance. This application should connect to a mySQL database located on an RDS instance.
  Unfortunately I can't connect to the database.</p>
  
  <p>The error message (inner exeption) that pops up is:</p>
  
  <blockquote>
    <p>Unable to find the requested .Net Framework Data Provider. It may not be installed.</p>
  </blockquote>
  
  <p><strong>Using @ AWS:</strong></p>
  
  <ul>
  <li><p>MySQL 5.6.27  (RDS; AZ: eu-central-1a)</p></li>
  <li><p>Windows Server 2012 R (EC2, AZ: eu-central-1b, t2.micro)</p></li>
  </ul>
  
  <p><strong>Using @ Application:</strong></p>
  
  <ul>
  <li><p>EF 5.0</p></li>
  <li><p>.NET Framwork 4.5.2</p></li>
  </ul>
  
  <p><strong>On AWS site:</strong></p>
  
  <ul>
  <li><p>connection between EC2 and RDS works fine</p></li>
  <li><p>can connect to the database with mySQL Workbench (on server)</p></li>
  <li><p>direct connection to the database starting the WPF application on my local PC works fine</p></li>
  </ul>
  
  <p><strong>Edit:</strong></p>
  
  <p>I guess it might be an issue with the .NET Framework
  I've already took a look into the machine.config in the tag "DBProviderFactories". Originally no special provider was given. I tried to add the mySQL Provider entry I have in my machine.config on my local  machine.
  Now I got some other error message (not related to .NET Framework) and try to figure out why it is thrown.</p>
  
  <p>Provider I entered:</p>
  
  <p><code>&lt;add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.9.9.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" /&gt;</code></p>
  
  <p>I really wonder what I can do here additionally? It is driving me nuts.
  Did I forgot to instal something for .NET Framework or mySQL on the Server?</p>
  
  <p>Thank you so much for your help!</p>
  
  <p><strong>Edit 2:</strong>
  The problem could be solved by configure the  client application correctly (there was a missing reference to MySQL). It was done by a colleague.</p>