Forms Authentication Works On Dev Server But Not Production Server (same SQL Db)?
Feb 7, 2010
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 have used a dll named MARCEngine, which is used to read Marc data. I use a method named MARC2MARC21XML which converts a normal marc file to an XML file.
The problem is it works great on my local IIS, but when I upload it to the production server, it only generates the root node and not the child nodes.
Here is a snippet of my sample page :
[Code]....
Asp.net has the permissions to access the files geneated.
This is a real quick question, is it possible to allow Windows Authentication for an ASP.Net intranet site (on a test server) to authenticate against the production server user accounts? If so, how would I go about doing so.
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.
Does anyone knows why HttpContext.Current.Server.MapPath within a server control works when I run the server control but gives and error whilst in Design mode?
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
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.
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 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 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 some code that allows users to upload file attachments into a varbinary(max) column in SQL Server from their web browser. It has been working perfectly fine for almost two years, but all of a sudden it stopped working. And it stopped working on only the production database server -- it still works fine on the development server.
I can only conclude that the code is fine and there is something up with the instance of SQL Server itself. But I have no idea how to isolate the problem.
I insert a record into the ATTACHMENT table, only inserting non-binary data like the title and the content type, and then chunk-upload the uploaded file using the following code:
I've been implementing the Forms Authentication in ASP.NET with C# (v3.5).I created a simple login form, when the users' email & passwords are stored in my SQL db.When I login in my localhost, everything works just fine, but when I published the project and uploaded it on to my production web server, things got a little bit wierd for me.The ttpContentxt.Current.User.Identity.IsAuthenticated variable return false, even if the login was successfull (and again, in localhost everything works fine).
In my Visual Studio 2008 web site, I created a new folder named Reporting. Then one of my web pages creates an xml file in this new folder when the user clicks a button. The user then clicks another button and the xml file displays in the browser. This all works fine on my development PC. But if I publish this web site to my production server, it does not work. I get an error when I click the first button to create my xml file. The error reads: Could not find part of the path 'c:windowssystem32inetsrvReportingabc.xml' What must I do so that this works on my development PC and also my production server?
I have a vertical menu placed on top of (z-Index) a background image. The background appears nicely on my development server but does not appear on the production server. I have deleted all folders and file from the appropriate directory on the production server and copied all files and folders from the dev server to the production server to no avail. I figure that there must be a setting blocking this functionality on the production server or perhaps that older version (Server 2003) does not support this function.Oh, I have been attempting to add 2 PNG images to this post but cannot succeed.
recently converted a project written with VS 2008 + asp.net 3.5.The problem is that on line on the production server (that's running asp.net 3.5) it can't render correctly on safari.The project has a BrowserFile.browser that with past visual studio worked:
I have this website with english and portuguese support. In localhost everything works fine and the content is translated based on the querystring parameter named "lang". This chunk of code makes the trick in every page:
Thanks to the logger I can say for sure that this method is called in both cases (production and localhost). I have two resources files in App_GlobalResources folder: -WebSitemapGlobal.en-us.resx; -WebSitemapGlobal.resx;
We deployed our legacy ASP.NET application to production after successful test deployments to our staging environment. The application makes use of RequiredFieldValidators on one particular registration page. On our development and stage environments, the validators successfully detect empty fields when "Submit" is clicked, error messages are displayed, and form submission is prevented. But on production, the validators do not display error messages. Clicking submit will cause a postback, the code-behind checks for Page.IsValid and correctly detects the form has missing fields, but the registration form is redisplayed with no error messages (ie "Please enter an email") to the user.Sample: (note I dont explicitly declare EnableClientScript or SetFocusOnError)
<asp:requiredfieldvalidator id=Requiredfieldvalidator1 runat="server" CssClass="NormalRed" Display="Dynamic" ErrorMessage="Please enter an email." ControlToValidate="txtEmail"></asp:requiredfieldvalidator>
Both environments (stage and production) are identical: Win2K3 Server and IIS 7, SQL Server 2008, and ASP.NET 1.1 runtime (embarrassingly).
Here is my problem: I have created a login form on my local machine. I have tested it on the local machine and it works fine. But when I push it to production it doesn't work.
I set-up the web config file so that the system uses the production database even from my local machine. I used the Web > AspNet Configuration tool in Visual Web developer to add a user to the production database. I used Sql studio management studio to confirm that the user was in the production database and not just on a local database. I have removed all references to the local database. I even deleted the entire app_data folder on my machine so that there was no chance that I am using a local database.
To create the login, I dragged a login component onto my Login.aspx page from the toolbar in visual web developer.
Why can I log in just fine on my local machine, but when push everything to production and I try to log in as that user I get the error message "Your login attempt was not successful"
