C# - WinHost - Configuration Error - LocalSqlServer Wasn't Found In The App Config Or Connection String
Apr 2, 2010
I've ran into a weird issue when ever I deploy to my winhost account and try to login using membership provider it works fine locally but once it's on the intarnets it breaks. Configuration Error Description: An error occurred during the processing of a configuration file require to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: The connection name 'LocalSqlServer' was not found in the applications configuration or the connection string is empty.
How do i configure connection string for Asp.Net Membership Provider? Do i have to write it by hand or any tool is available in Visual Studio where i can specify connection string as well as algorithm used to store password? I read one article and it specifies this connection string :-
in MyWeb there are all the aspx page and some entites datamodel, in MyApp there are the class with function like "getter data from DB" and there is a entity data model.
afeter the deploy, I have only the web.config and the connection string for the entity datamodel....itīs run ok, read/write the data on the DB.
The problem is with MyApp.....after the deploy it is a dll file and I donīt have the app.config and the entity inside it donīt run, not read/write nothing on the DB.
There arenīt error or messager but not read/write the data in the MyApp project.
all run on the iis 7
now...the question is:
I lose the connection string (in app.config) after the deploy?
Can I put a entity in the MyWeb and read it in another project (myApp)?
I have been preparing for a conversion of an old application to an ASP.NET webapplication at beginning of the year. Generally, the development version of the webapp will also be the webapp that goes into production. We here make "clones" of the database server, assign new name, etc, which is then used for development, training, and so on without any threat of changing data on the real db (sql server 2005). I know it is possible to have more then one connection string in the web.config. My question centers around if there is a simple method for allow multiple connection strings and pick the one that is to be used for dev, production, training, and so on? I originally thought about constructing some type of admin form that the connection string can be selected from.
I have an app that is a bit old and will eventiall be rewritten but until I get the time it needs to continue to be patched. THe app is desgined broken into three layers (Web, DAL, BLL) The web site uses the DAL.DLL and BLL.DLL and the Website has some dataaccess and the sonnection string is saved in the web.config. For the DAL it is stored in the app.settings. Is there a way for the DAL to use the connection string that is stored in the Web.config even thought it is in DLL for the production site?
I have a solution in Visual Studio 2008 with 3 projects. One Web Application and 2 class libraries. The entity framework model is in a class library and the start project is the web application.
I used to have this problem:
"The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid."
I fixed it copying the connection string from the App.config of the class library where the entity model is located to the web.config of my web application (start project).
I found that workaround posted here:
[URL]
how can i avoid using the connection string from the web.config and use the one from the app.config where the entity model is located?
I have this in the web config file <connectionstrings> section. Why is there an add and then remove and then again an add...what is it trying to accomplish here? and in the second code section, I use that string in a sqldatasource control. Second question: Can I just use the name attribute value "localsqlserver" form web config file, in place of the connection string in the data source? is it why that attribute is for?
I have a Windows Service I have developed in Visual Studio 2005 (C#).
It accesses a database using a connection string in machine.config.
On my Windows XP Pro 32bit (SP3) machine, it works correctly.
On my new Windows 7 Pro 64bit machine, it throws "object not set to an instance of an object" when it gets to the line where it's trying use the connection string.
This is the 'object' which is not set in Windows 7:
The machine.config has the same connection string set up on both machines.
A .Net 2 website transferred to the Windows 7 machine has no problem accessing the same connection string.
I have tried a bunch of different permissions on the machine.config and its containing folders, and setting the service to log in as Admin, but I don't know exactly what permissions are required.
When I try to encrypt the "connectionStrings" section in the web.config file of my asp.net web application on Windows Server 2008, I'm getting the following error:
Administration utility (2.0.50727) to install and uninstall ASP.NET on the local machine. Copyright (c) Microsoft Corporation. All rights reserved. Note: This utility has limited capabilities on the Windows Vista operating system. It is recommended that you use the "Turn on or off Windows features" option of the "Programs" component of Control Panel to install or remove ASP.NET. It is also recommended that you use the IIS Manager component or the Appcmd.exe tool to configure ASP.NET applications.
The above information is followed by the list of valid options to aspnet_regiis.exe.
I have a database on Go Daddy and my VS2008 app can not access it via web.config connection string. Of course runs great locally in development. I copy/pasted the connection string information from Go Daddy exactly into my web.config file. Web site runs fine on the web but when I try to Login at my login page, i get :The SSE Provider did not find the database file specified in the connection string. At the configured trust level (below High trust level), the SSE provider can not automatically create the database file.
I used VS2008 to create the .sql script files and uploaded them to Go Daddy and the Go Daddy people say everything works as they and I can both Login to the database from within GoDaddy.The database i am trying to access consists of the a ASPNETDB.mdf and another Database.mdf together as one in the Go Daddy database.
here is what i used: <connectionStrings><add name="superskin" connectionString="Data
I have set up a small SQL Server database for users to login and also create accounts. There is a problem with the connection string though. Whenever I use the connection string below in the web.config file I get a server error page and cannot view the website. However when I take out this connection string I am able to view the website albeit the database doesn't work.
I have a db connection string 'ApplicationServices' defined in the connectionString section of web.config and 3 Entity Framework connection strings which have the provider connection string attribute with the same connection string as the one in 'ApplicationServices'. Is there a way to reference connectionString in 'ApplicationServices' for the provider connection string attribute of the EF connection string in the web.config, rather than providing the connection string all over again?
my webserver is in the DMZ. The Database in the intranet. For connection from webserver to database the following entry is made in the odbc connection "TCPIP BCAST=NO;HOST=Intranet.Firma.local,Intranet_Spiegel.Firma.local,Intranet_Arbiter.Firma.local;PORT=2639}"
how to get this options in the connection strings working, or how i must modify the entitiy framework connection string to use the odbc entry?
just for my testing purpose i know i can define both the connection's outside in a single web config file by different name's and access them in my front end according to it but what if i want to have seprate for both connection's web.config situation is like this see image so i want to access my connections from second web config file how i can do that.
I am preparing for an Access2007 db conversion at the beginning of the year and would like to know what the best process would be for connecting to the sqlserver2005 database. I have read about adding the connection string to the web.config file. I have also read about using ADO.NET and put the connection information into a class and not the web.config file.
I would like to hear from others as to what you have used, are using, or plan on using for a webapp (vs2010), and why so I can get an understanding.
I added a database to my project. When I did so an app.config file was added to my project. (Yes I know I have dangerous info in the connection string. I shall change that but for now I am messing around with test stuff.)
I did a google search on how to get the connection string value and found. string sConn = ConfigurationSettings.AppSettings["ConnectionString"]; I am getting a warning that this is obsolete. It has been replaced by ConfigurationManager.AppSettings. Ok Fine. According to the docs, it is also in System.Confiuguration which I already have a using statement for above. But when I attempt to use it, it is not part of the assembly.
