i have made a project that has an access database.
i have manage to connect and retrive data from the database at aspx and at code behind.
the problem is that i do not want to write the connection string at code behind again and again but to get it from the web.config as i am doing to the aspx pages.
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 need a connection string to connect the microsoft 2003 database with my ASP.NET webserviceWhen just making a website I used to use the following connection statement
OleDbConnection dbconn = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0; data source=" + + Server.MapPath("~/db/SalesCentral.mdb"));
Now as I am using a webservice the Server.MapPath function is giving an error
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?
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.
I am making use of 3-Tier architecture while making my project. And in Data Access Layer I am making use of application block, but application gets a connection string from web.config; but ClassLibrary of Data Access Layer doesn't contain web config file. How can I access connection string from Data Access layer?
i am making an application in which i have stored connection string in security.cs file under app_code folder...all is my application is going well except update panel of gridview using sql datasouce..i dont know what to write in connection string .. i mean i have connection string in class file.. so what to write in aspx page so that it will get the connection string from app_code
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
Background: I use SQL server 2005 developer edition and visual studio 2008. Visual studio 2008 is running on a local machine with Vista business edition. SQL server is running on a remote server using Windows server 2003. Both computers are within the same domain.
Problem: First, I used the server explorer to connect to the SQL server. Everything works as desired. Then I write code to do the same thing. I keep getting the following error message:
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: 25 - Connection string is not valid)
However, I used the exactly identical connection string as the one used in the server explorer. So connection string should not be the problem. In addition, I tried the test code in MSDN, which tells whether my domainusername can flow the network. It turns out the user name is fine. I also went to the SQL server management studio and found the login for my computer is NVCWeihao while my computer login name is NVCweihao. I am wondering if this uppercase letter really affects the connection.
and this database lmslive is in a system next to mine connected via proxy.... And i executed this query on that system,
GRANT ALL PRIVILEGES ON lmslive.* TO 'lmslive'@'10.1.1.15' IDENTIFIED BY 'lmslive' WITH GRANT OPTION; I get the error, Access denied for user 'root'@'XAVY-PANDIYA' (using password: YES).. what am i missing?
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 have an ASP.Net website running on IIS7. The Application Pool is set to ASPv4 Classic.
Authentication Mode is set to ASP.Net Authentication & Windows Authentication
My question is, when I want to connect to SQL using a "trusted connection" in the Connection String, what user will actually be passed into SQL?
I thought it would pass my logon details, but it is coming back with an NT AUTHORITYANONYMOUS LOGON error, which seems to point towards it not passing in my logon.
on VWD 2005 this code works fine, but on 2008 it says I haven't created an instance of the object. I want to convert the object connString (a connection string) into a string.
'This acceses the virtual directory web.config file for connection strings 'We have to convert the object to a connection string Dim rootWebConfig As System.Configuration.Configuration rootWebConfig = System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration("/VirtualDirec") Dim connString As System.Configuration.ConnectionStringSettings connString = rootWebConfig.ConnectionStrings.ConnectionStrings("ConnectString1") Dim strConnString As String = connString.ToString().......
I have got a small website with MS Access Database. I have used access membership provide with it. i bought hosting with Discountasp.net when i uplaoded my web to the server it gives me following error. It works perfect on my local machine. i have contacted the support guys they say there is somthing worng with my web config there is nothing pointing to sql server in my web config. here is my error message. I have a hosting with iis 6 it does work on that but it does not with with iis7.
Server Error in '/' Application.
Configuration Error Description: An error occurred during the processing of a configuration file required 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.
Source Error:
[Code]....
Line 158: <roleManager>Line 159: <providers>Line 160: <add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" applicationName="/" type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>Line 161: <add name="AspNetWindowsTokenRoleProvider" applicationName="/" type="System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>Line 162: </providers> Source File: C:WindowsMicrosoft.NETFrameworkv2.0.50727Configmachine.config Line: 160 Version Information: Microsoft .NET Framework Version:2.0.50727.4016; ASP.NET Version:2.0.50727.4016
I'm having a terrible time being able to connect my access database to my website. I'm using 1and1.com as my host. The database resides in my App_Data folder. I checked everything I could think of on the host side. I cannot query from the database through VWD Express nor create a typed dataset .xsd that will allow quering the database.p.s. - I don't need any sophisticated security on the database, just a homegrown sign in I put together that works fine for my site which is mostly xml file data.
I have an ASP.NET project which gives me the following exception if I try to run it Where should I "call" it before I can use it ?There is no global.asax in my solution
Project 1: Web Application (.aspx/.ascx/.cs/)* Project 2: Class Library (has one static class, Repository.cs, which is full of static methods used to put/get data to/from DB) Project 3: Web Service (allows few of the mthods of the Repository to be used via WebService)
Conditions:
There will be about 10 copies of Project 1 (WebAppliation) runngin on IIS each for a seperate client.I want each copy of Project 1, and the Web Service to read/write data from/to DB via Repository only. So all 11 Projects (10 Project 1, and 1 Wb Service, will be using repository as DAL)Questions1) Where shall i put the connection strings??? because each web application will have its own connection string, i cant save it in repository. And if i keep it at the web.config of each project, then what is the best way to pass it to repository?
2) Repository.cs is a static class with all static methods, is this a good approach? Should it be static? or should i not make it static in order to allow creationof objects of Repository.cs. (this way may be i can also send connection strings to the objects of repository, in whatever project required...???)
I have an ASP project that works fine locally. It makes use of a dll that gets information from a database. I set this up using the datasource wizard, which is not how I like to do things. I find it to be a bit opaque, and this problem is a fine example. When I publish the website, I get an error that ultimately shows this:
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.]
That suggests that it is not using the username and password, so I went to the App.Config file in the dll, which is the one place that has the connection string that I know of (normally, I'd do it in code and it wouldn't be there, but I'm doing something new). If I change the DB name to a DB that is very similar to the correct one, then run one of the queries, it correctly complains about a few missing columns. As long as I use the correct DB name, then it works (there's a production DB and a dev DB. The two are identical except that I haven't added a few columns to the tables in the production DB). This shows that the connection string is being at least partially used.
However, if I alter the password, such that it is invalid, I have no problem running the query, which suggests that the username and password are being ignored, and my own local credentials are being used instead (or at least that's the going theory as to why I can connect just fine when the password is wrong). The credentials are set up correctly as far as I can determine. That portion of the connection string are copied directly from a different project that works fine.
So, despite having credentials that should be valid, the dll appears to be steadfastly using my local credentials and ignoring the ones in the connection string in App.config. I would assume that this has something to do with the datasource wizard, which I don't use.
