We Keep Coding

IIS seems to not being able to connect using Entity framework provider

I've being trying in vain to solve a problem on a newly created windows server with IIS hosting an ASP.NET application that was copied from another environment. The issue is that I cannot manage to connect to the database when the application tries to open a connection via entity framework.
If this is off topic for SO let me know so I can move to another channel, I thought it belonged here as seems specific to EF.
In detail, I have the following connection strings:
<connectionStrings>
<add name="ApplicationServices" connectionString="Data Source=LOCALCOMPUTER\SQLEXPRESS;Initial Catalog=xxx;Persist Security Info=True;User ID=yyy;Password=zzz" providerName="System.Data.SqlClient"/>
<add name="MembershipConnection" connectionString="metadata=res://*/App_Code.Membership.Membership.csdl|res://*/App_Code.Membership.Membership.ssdl|res://*/App_Code.Membership.Membership.msl;provider=System.Data.SqlClient;provider connection string="Data Source=LOCALCOMPUTER\SQLEXPRESS;Initial Catalog=xxx;Persist Security Info=True;User ID=yyy;Password=zzz;MultipleActiveResultSets=True;Application Name=EntityFramework"" providerName="System.Data.EntityClient"/>
...
xxx, yyy, zzz of course have the proper values. LOCALCOMPUTER is the FDQN of the local computer, which is not on a domain
The first connection string is for the Microsoft login library, while the second uses entity framework from our code.
When I browse to the site, I can successfully access the login form, and if I try to insert a wrong password i get a message saying so, meaning the application managed to check the database using the first connection string, but when i insert a correct one, i land on an exception as soon as the code tries to create a context.
The underlying provider failed on Open.:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.)
In the event viewer it tells me that the user has been authenticated via Authentication Type: Forms , which I assume it means the auth system (the one using ApplicationServices connection string) is working, the stack trace confirms that the error occours when I try to use EF in code, meaning the DB has been used succesfully to check user credentials
note that:
The web app works in other environments
I can connect to the sql server using the credentials via SSMS
I've assigned a local windows account to the app pool that can also access the database, and tried changing to Integrated Security=SSPI
Both .Net 3.5 and .Net 4.8 are installed
The database is on the local machine and has been restored from a dump of the other one, its users have been mapped, and to rule out issues i gave it ample authorisations with dbowner datawriter and datareader
I've been trying to fix this since a couple days checking similar issues on SO with no avail and I don't really know how to proceed, is there something I can do to troubleshoot the issue?

Apologies, I've found out the answer, and it's specific to the code base. Apparently the connection string was being ignored (despite being perfectly usable) in favour of data saved in a table.
Had to contact the previous developer to find out, guess it's a good example of how important is to document your code
I'll close the thread, thanks for all who tried to help

How to connect to SQL Server Express using EntityFramework

I tried to find information about this on the web and Stack Overflow, but none of the responses could help me solving my problem.
I'm working with C# and SQL Server. I'm using code from an existing project, which project connects to an SQL Server instance to manage data. This project uses EntityFramework.
Now I want to use a local instance of SQL Server, precisely SQL Server Express, for development purpose. But I can't figure out how to connect to this local instance.
Connecting to the remote SQL Server works perfectly, using this connection string:
<add name="ProjectEntities" connectionString="metadata=res://*/Project.Project.csdl|res://*/Project.Project.ssdl|res://*/Project.Project.msl;provider=System.Data.SqlClient;provider connection string="data source=111.111.111.666\(local), 1433;initial catalog=PROJECT;persist security info=True;user id=user;password=password;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
But if I modify it to use my local instance:
<add name="ProjectEntities" connectionString="metadata=res://*/Project.Project.csdl|res://*/Project.Project.ssdl|res://*/Project.Project.msl;provider=System.Data.SqlClient;provider connection string="data source=.\PROJECT, 1433;initial catalog=PROJECT;persist security info=True;user id=user;password=password;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
it doesn't work.
I tried with putting the source in "MAC\PROJECT" also, it does not change anything. Using the udl file workaround to test connection parameters is totally OK both with "MAC\PROJECT" and ".\PROJECT" and the right credentials.
I can't figure out why my project connect to the database perfectly using the remote server but not the local one. Am I missing something?

Right after posting this question I found the answer.... The old connection string gives a port number, which is not needed when connecting to the local instance.

Publish remote server [Win32Exception (0x80004005)]

I'm wondering if my connection string is wrong because when I publish this on a server it doesn't work, otherwise when I test it on debug mode it works.
<add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-app-20130122205025;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-app-20130122205025.mdf"
providerName="System.Data.SqlClient" />
<add name="SiteSourceContext" connectionString="Data Source=(localdb)\v11.0; Initial Catalog=SiteSourceContext-20130125171153; Integrated Security=True; MultipleActiveResultSets=True; AttachDbFilename=|DataDirectory|SiteSourceContext-20130125171153.mdf"
providerName="System.Data.SqlClient" />
Can someone help out? Im relatively new and trying to learn, so I dont know what Im doing but this is the error I get:
[Win32Exception (0x80004005): The specified file is not found]
[SqlException (0x80131904): A network-related error or instance-specific occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (Provider: SQL Network Interfaces, error: 52 - Could not locate installation of a runtime database locally. Verify that SQL Server Express is installed and the runtime functionality of local database is enabled.) ]
System.Data.SqlClient.SqlInternalConnection.OnError (SqlException exception, Boolean breakConnection, Action `1 wrapCloseInAction) 6675286
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning (TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) 688

Verify that SQL Server Express is installed and the runtime functionality of local database is enabled.

Try Changing This :
Data Source=(LocalDb)\v11.0
To This :
Data Source=.\v11.0
Or This :
Data Source=.\SQLExpress

Keep in mind that using Data Source=(LocalDB)\v11.0 limits the credentials to the user that created/owns the database. If you are publishing this as an ASP.NET service, your code will be running under a different user; likely NETWORK SERVICE.
Further, it looks like the connection string is specifying a file that probably only exists in your development environment, not on the server you are publishing to. You'll need to install SQLExpress on that server and set up the connection string to access that. I wouldn't use Data Source=(LocalDB)\v11.0;; instead I'd use Data Source=localhost\SQLEXPRESS; or Data Source=.\SQLEXPRESS to maintain consistency between your development environment and deployment.

Probably, the instance name of SQL server installed in your development computer and server have different names. So you need to change the connection string. If you have installed SQL Server, if not you need to install it.
Other possibility is, the instance of the SQL Server might not be running. You can go to Windows Services from control panel and check if SQL Server service you stored your database started or not. There might be multiple services, if you have multiple instances of SQL Server. Make sure that you are using the connection string for the correct instance.
Also, in your database, you should give access priority to related IIS user (e.g. IIS APPPOOL\DefaultAppPool), if you decide to use Windows Authentication. Or you can use SQL Server authentication.
In a nutshell, I believe that you have problem with referring to SQL Server Instance. When you solve it, if you do not try to access to DB with valid credentials, you will have a authentication problem.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found,etc

I'm just publishing my website to my domain name and when I try to access it in my browser I get the Following error:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: SQL
Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
I think the problem is into my connection String ==>
<configuration>
<connectionStrings>
<add name="ApplicationServices" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />
<add name="TennisOnlineContext" connectionString="Data Source=|DataDirectory|Tennis.sdf" providerName="System.Data.SqlServerCe.4.0 " />
</connectionStrings>
...
</configuration>
Sorry but it's my first web site where I try to publish... So, please what I'm doing wrong ? Thanks in advance...

Have you tried localhost\SQLEXPRESS? Ensure all of your connection keywords abide by those outlined by Microsoft here.
You can check if a connection string is valid, or indeed build a valid connection string that you can copy, by using the SQL/Database Connection utility that ships with VS2010. In VS2010 goto Tools, Connect to database. This will launch the connection dialog; here you can build and test connection strings. For advance connection features, once in the dialog click Advanced. From the advance dialog you can copy and paste connection strings.
Microsoft have also released this dialog to be freely used and distributed in .NET applications. If you interested in this it can be found here.
I hope this helps.

If you are connecting from Windows machine A to Windows machine B (server with SQL Server installed), and are getting this error, you need to do the following:
On machine B:
1.) turn on the Windows service called "SQL Server Browser" and start the service
2.) in the Windows firewall, enable incoming port UDP 1434 (in case SQL Server Management Studio on machine A is connecting or a program on machine A is connecting)
3.) in the Windows firewall, enable incoming port TCP 1433 (in case there is a telnet connection)
4.) in SQL Server Configuration Manager, enable TCP/IP protocol for port 1433

If you look into your release version of web.config you will find <roleManager enabled="false"
Change this configuration setting to True
You can find details here at this link below
http://dotnet1blogger.blogspot.com/2012/04/network-related-or-instance-specific.html

please check once TCP/IP properties in SQL server configuration manager
for more details here

Enable TCP/IP and Named Pipes in SQL Server Configuration Manager.
From SQL Server Configuration Manager, select SQL Server Network Configuration, then select the appropriate instance (if you have multiple). Right click and select enable for Named Pipes and TCP/IP.

Entity framework 4 Underlaying provider failed on Open

I am trying to connect to the database but I am getting this exception:
A network-related or instance-specific error occurred while establishing a connection to
SQL Server. The server was not found or was not accessible. Verify that the instance name
is correct and that SQL Server is configured to allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I've googled a lot, but I could not find the answer.
Here's my configuration:
I use MS SQL Server 2008 Express. Both Sql Server and Sql Server Browser use my account (I am an administrator). I've also used local system and local service. Without success.
Here is my connectionstring in app.config:
<?xml version="1.0"?>
<configuration>
<connectionStrings>
<add name="EventManagerEntities" connectionString="metadata=res://*/Entities.RelationModel.csdl|res://*/Entities.RelationModel.ssdl|res://*/Entities.RelationModel.msl;provider=System.Data.SqlClient;provider connection string="Data Source=martijn-laptop\sql2008;Initial Catalog=EventManager;Integrated Security=True;MultipleActiveResultSets=True"" providerName="System.Data.EntityClient"/>
</connectionStrings>
<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/></startup></configuration>
I've also tried to use the sql server username and password, also without success.
I am using winforms. What else can I try?
When I check netstat -an I get this:
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
I don't think this is correct, right? But how do I set it right?

It cannot find instance/server. Telnet the 1433th or the configured port of martijn-laptop\sql2008 to verify its accessible

Go into the SQL Server Configuration Manager and make sure you have the protocols you want to use enabled under "SQL Server Network Configuration" > "Protocols for Sql2008"

From the error it seem like there is connectivity to database issue. Assuming this solution has been working elsewhere have you setup and connected to a different database?
Is so validate that the code generated with edmx has the correct default database connection name or that you are overriding it:
var context = new EventManagerContext("EventManagerEntities");
Or whatever the correct systax for EF is.