Deploy And Configure Aspnetdb On A Production Server?
Mar 7, 2011
I am developing a MVC 2 application that uses aspnetdb on my SQL Server 2008 detabase for forms authentication. On my development machine I can configure the users, roles and permissions using my Website Administration Tool (WAT). My question is how do I deploy this database to a production server and how do I configure it with users, roles and permissions?
I have created my site using ASP.NET Personal Starter Kits 3.5. I use Visual Studio 2008 only . .with its built-in SQL Server (2005 Express) ... my database in App_Data is ASPNETDB.MDF ...
I have created some of my tables also ....in ASPNETDB ..
In my local PC the site was running fine ...
But when I publish my site on production server it doesn't work and shows the following error
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.
My hosting provider gave me the connection string to connect to the SQL Server 2005 but it doesn't work...
I don't understand why my site was running fine using the production SQL Server 2005 in my local PC when I include ASPNETDB.MDF file in App_Data in my local pc only ..if I remove file ASPNETDB.MDF from App_Data of my local pc ... the site stops working ...
Can anybody tell em how to fix this ... !! I am very tensed since last 3-4 days
I have create a report in sql server 2005 & want to deploy on production server, in local system it deployed & works well. also if that report deploy at local system successfuly than how i see report in intranet.
I developed application with using of SqlMembershipProvider.
I want to deploy on server with SqlExpress. And I don't understand how to deploy aspnetdb database. I want to deploy aspnetdb with preliminarily defined groups. How to do it?
My technique for deploying an ASP.NET webapp into production is as follows: Client: Select 'Release' mode and then right-click to publish. Go manually to the publish folder and zip contents. Now transfer to server by FTP.
Server:
Unzip folder contents. Stop IIS. Deploy new folder contents for web app. Start IIS. I don't stop the database or run any additional tools to promote to production. It's a small company, and this seems fine. What's wrong with this technique in your opinion?
I have an asp.net web application that I am deploying using ms web deploy to an iis 7 web server. I recently moved the project to source control with tortoise svn. Now web deploy isn't working since it is trying to copy the hidden read-only files (in a .svn subdirectory) that svn is using onto the iis server. How do I configure web deploy to leave these files alone?
I hate to sound stupid, but ASP.NET is not my forte. I have build an ASP.NET application which I now which to deploy to a production server. Searching on the web I found that it's recommended to just use the Setup tool within VS2010 to compile and install the files on the production servers. However, I find it a bit weird:
The files on the server are exactly those that I had on my system. I would've imagined that moving to a production server would involve some compiling and compression of file content so as to improve execution. But in practice all files on the server are exactly as they are on my local system -- I can even modify my .cs file on the servers and that works!! (Surprised ;-)). Following from the above, all my code is readily available on the server for anyone to see. I am not sure if this is a problem... For example, could it end up a security risk (due to passwords within the files)?
I'm trying to find the best server architecture solution to deploy monthly updates to an Asp.net external public facing website. What I'm looking for are ways to release a new version of a website with minimal impact to users. Besides deploying the standard way (ie. stop IIS, copy new website over existing website, start IIS), what are some "better" solutions for deployment out there? It would be nice if they kept their session and didn't have to see a "Website under maintenance" message during the update. My server configuration
We have 2 IIS web servers (2003) and are trying to figure out the best way to utilize them for deployments. My first thought was to update the non-active web server with the latest release. Then to gracefully point the web traffic to that server with minimal impact to users (best case, the user doesn't lose his session). How would you go about "repointing" the web traffic from server 1 to server 2? Changing firewall NAT? Changing DNS records? Some other way?? We need to be able to test the live site immediately after we release the new changes (duh). BTW, we are using nant and cruise control to automate the builds, and a custom web service to deploy the build to production. So it's all automated with the click of a button. Could a better solution be achieved using a 3rd server? If so how?
I am developing 2 Applications. One WebForms and the other is MVC. How can i secure the code such that when i deploy them to the clients production environment, they cannot be simply picked up, copied and repackaged by someone else?. I simply need a way to protect my intellectual property. Can this be done in Visual Studio 2010?
I have around 100 rdl report files...what i have found in google is -> open RS Admin site upload each report...doing this manually takes a lot of time... We don't want to use Target report server url method and clicking deploy option to deploy the reports or report project onto the report server...because we are not provided with such production server url information...!! In client perspective...We just give the reports as a rar file...now client will have to extract the report files...and what should be the next step...!! Is there anyway to deploy or upload all the reports at a time...!!
i have a problem, i want to decrypt password in aspnetdb, the password created by web administration tool in vs, i want to decrypt it without using MemberShipProvider, i there any way.
I was wondering how I would go about changing a users password in ASPNETDB? There are some stored procedure I've been playing around with such as dbo.aspnet_Membership_setpassword and resetpassword but I've managed to corrupt the login password for my user as now I cannot login anymore (gives wrong username or password message in my webform login screen).Any ideas how I can successfully change my password from the ASPNETDB / stored procedure ?
I'm working on a new asp.net 4.0 resume web site. I'm starting off with SQL Server Express 2005 and using the standard security and login features given with ASPNETDB.mdf. My site will be hosted on GoDaddy.com.
Quesiton. Should the tables that will contain the information that users will be putting in like resumes, contact information and such go into ASPNETDB.mdf or should it go into a separate database.
I have deployed an MVC application that uses ASPNetDB for Membership and Role Provider.
now when i browse to the site on the actual server where it was deployed to i can use the login page to login on to the site and gain access to views that are restricted to users like myself by role.
However when i try and access the web application from any client computer who has access to sites on the server since the server is on the same domain - i experience the following strange behaviour:
when i navigate to my login page and enter my username and password (as stored in the aspnetdb database)
and click login
the page refreshes (looses my userid and name) and it does not go to the view i requested.
it also does not show in the top right links that i am logged on.
it is as though it spits out my username and password and refresh the page and that is that!
Why does it work on the server where the site is hosted - but not from external clients?
i can access all pages that do not require users to be logged on or haev a specific role - but cannot log on and view them since login is broken?
not sure if this is the right place for this and I AM sure that you'll have seen posts like this before...In short, how do I go about replicating the aspnetdb on my hosted server? I would like to avoid manually copying all the tables and relationships.
I create a dynamic dropdownlist to select several values, in developer server it's everything ok but in production server, when the postback happens lost the selected value.
how to transfer my data from devlopment server to production server ,i have already records exist in my database if i go for script then how can i transfor record in script i can transfor only table ,procedure and views.I am using SqlServer 2005.
We have a cient we are stting up that has 2 separate physical servers, one that is the web server the other the database server. Using impersonation we have been able to get the website to connect and retrieve data from the sql server so that part is not an issue. The problem is I have a windows service application that must be installed on the web server (as it process files downloaded to an ftp site) and it must be able to connect and write to the sql server as well.We tried adding a system.web block with the impersonation stuff to the app.config file which of course did not work. Can anyone tell me what/how we need to configure this properly?
I am working on the migration of the server. Our new server is Windows server 2008 with IIS7.0 I have a great difficulty in browsing the pages hosted in virtual directories. I have followed the proper steps of creating a virtual directories and converting them into applications. But when i try to browsing the pages of the virtual directory, i get the 404 error. Note: The .Net Framework 4.0 is installed on the server and the web applications which i am trying to configure in the virtual directories are developed in Visual Studio 3.0. Even the http://localhost also don't work.
I have a named instance of sql 2008 developer edition installed. I have changed the Server name but the query string will still not work. I want to be able to use the default db "aspnetdb.mdf". I use Windows authentication to connect. How can i change the connection string to get this to work?
I've never had this problem before, I'm at a total loss.
I have a SQL Server 2008 database with ASP.NET Forms Authentication, profiles and roles created and is functional on the development workstation. I can login using the created users without problem.
I back up the database on the development computer and restore it on the production server. I xcopy the DLLs and ASP.NET files to the server. I make the necessary changes in the web.config, changing the SQL connection strings to point to the production server database and upload it.
I've made sure to generate a machine key and it is the same on both the development web.config and the production web.config.
And yet, when I try to login on the production server, the same user that I'm able to login successfully with on the development computer, fails on the production server.
There is other content in the database, the schema generated by FluentNHibernate. This content is able to be queried successfully on both development and production servers.
I am wondering the best way to change my connection string based upon which server I am accessing.
Essentially, all of the development is done on our local machines - once we think it is working, we upload it to our development server. In these 2 instances, I want my application to go off of our "dev" connection string for the SQL database in the web.config.
However, once it is published to our production server (for an internal application), I would like the connection string to point to our live db.
I am using the N-Tier model by Imar Spaanjaars - and have it setup like he suggests - In my DAL I have a class called AppConfiguration -
In this class I have a public readonly property ConnectionString() which returns the connection string in the web.config.
This is in an individual class library. What I would like to do is something similar to:
If server is localhost OR devstring return devString else return productionstring
I m getting the following error when i upload my site to Production Server using Database in App_Data ASPNETDB.MDF
Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current ustom error settings for this application prevent the details of the application error from being viewed [code]...
I built an ASP.NET 4.0 Web Site. It works perfectly on my development computer. However, when I deploy the web site to theProduction Server, which is a Win2003 Small Business with Sql Server 2000, the site can't connect to the database.
These are the different tests I've made:
I tried using Integrated Windows authentication and this connection string: Data Source=myServerAddress;Initial Catalog=myDataBase;Integratedsecurity=true; and the error I got was that NT Authority/Network Service couldn't open the database. So I added that account to my database users list and gave it the appropiate permissions. Nothing.I tried using Sql Server authentication, so I created a new database user with a password and changed my connection string toData Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;. Nothing. I still got the same NT Authority user message.I deleted the used I created in step 2 and used the same connection string, to see if this time I got an error saying something about my user, and indeed it happened. I got an exception saying that user myUsername couldn't log on. I then created the user again, ang got the NT Authority user message one more time.I created a console application that used the same connection string from steps 2 and 3, and it connected to the database witouth any problem, which made me think that my problem's got something to do with my Web.config.I tried enabling impersonation on my Web.config, and thos time I got the same error message, only referring to the user I logged in to Windows, instead of NT Authority/Network service. What else could I check? My Web.config is this in case it helps (I havn't really put anything into it other than what VS puts):
I have visual studio 2005 and sql server standard edition installed on my desktop. Im trying to get my head around the authentication and role administration part of visual studio controls.
At the moment Im using the browser version to configure the settings.
While im attempting to access the security tab to develope, users and roles i keep getting a message saying im unable to connect to the database. However, when i use my collogues PC with SQL server express installed it connects with no problems.
Does anyone have an idea how i configure this tool to use SQL server standard edition so i dont have to go back to express?