Problem with users when publishing application

Question

I am using SQL Server 2012, and when publishing my application, both on the client server and on my pc everything works well. As connection strings for the BD are correct, everything looks good. Now where is the problem? When trying to authenticate a user I get the 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. (Preview: SQL Network Interfaces, error: 50 - Local Database Runtime error occurred. Cannot create an Automatic instance. See the Windows Application Event log for error Details. )

In my file Authconfig.Cs have:

WebSecurity.InitializeDatabaseConnection("Server=" + ConfigurationManager.AppSettings["Server"] + ";Database=" + ConfigurationManager.AppSettings["Database"] + ";Integrated Security=False;User ID=" + ConfigurationManager.AppSettings["UserID"] + ";Password=" + ConfigurationManager.AppSettings["Password"] + ";MultipleActiveResultSets=true;",
                        "System.Data.SqlClient", "Users", "UserId", "UserName", autoCreateTables: true);

Where will I get the data (Server, Database, Userid and Password) to my Web.config

Web.config:

  <connectionStrings>
    <add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-MvcTesteLayout-20131023143453;Integrated Security=False;AttachDBFilename=|DataDirectory|\aspnet-MvcTesteLayout-20131023143453.mdf" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="webpages:Version" value="2.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="PreserveLoginUrl" value="true" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
    <add key="Server" value="CPSI0024\SQLEXPRESS" />
    <add key="Database" value="OleoTorres" />
    <add key="UserID" value="OleoTorres" />
    <add key="Password" value="oleotorres" />
    <add key="ServerArtSoft" value="OLEOTORRES2014" />
    <add key="UserServerArtSoft" value="Admin" />
    <add key="PassServerArtSoft" value="passServ" />
    <add key="pathFiles" value="D:/uploadsOleotorres"></add>
    <add key="pathFilesGerarPDF" value="D:/gerarPDFOleotorres"></add>
  </appSettings>

I’ve looked for several ways to solve it, but I couldn’t find a solution to solve the problem...

Answer 1

If the database is on a separate machine (as the machine suggests CPSI0024) using an SQL Server Express instance, you need to make an additional configuration to allow remote connections:

1. Initiate > All Programs > Microsoft SQL Server (version) > SQL Server Configuration Manager (as an administrator);
2. Expand SQL Server Network Configuration;
3. Click on Protocols;
4. Enable the TCP/IP. Optionally, also enable Named Pipes.

Also check that Firewall is enabled to allow Inbound and Outbound Connections to the SQL Server instance.

Answer 2

What is the version of Sql Server? Will it be 'Localdb'? And what is the format of the Server value on web.config? (do not write your own name here, use a dummy name). This location or remote?

If you have 'Sql Server Management Studio' (SSMS) you can open, right click on the node above that represents the BD, choose 'Properties/Connections', and see an option "Allow remote Connections to this server" - this must be marked.

A suggestion on the side. If you write the connectionString in full on the web.config within "connectionStrings" section then it will be sharper to search simply with ConfigurationManager.ConnectionStrings[chave].ConnectionString

Answer 3

Well, after a few hours back from this problem I found the solution. I commented on my connectionString in the web config.:

  <connectionStrings>
<!--<add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-MvcTesteLayout-20131023143453;Integrated Security=False;AttachDBFilename=|DataDirectory|\aspnet-MvcTesteLayout-20131023143453.mdf" providerName="System.Data.SqlClient" />-->

And I deleted the file Initializesimplemembershipattribute.Cs that when creating the project in Visual studio.

As far as I can tell, he was logging into a database called localDb instead of being in mine CPSI0024 SQLEXPRESS. Until now I thought that by using the localDb was making reference to CPSI0024 SQLEXPRESS and not a separate local database...

Nevertheless, thank you for your replies :)