If you look at InnerException, it is possible that you really have a problem with Login.
What I needed to do to fix this, change the account that DefaultAppPool runs as NetworkService (go to "Advanced Settings" and change "Process Model", "Identification"), and then select the account that has access to your database.
Assuming your application is running in IIS using DefaultAppPool.
I did this NetworkService and granted NT AUTHORITY \ NETWORK SERVICE user access to my existing database.
This allowed me to connect. My case may be specific, but I thought I would share it just in case.
Gareth oates
source share