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]...
After reading this post and the mentioned blog, I am having the exact same problem. However, my web config does not have a membershipprovider section. Not sure how I'm going to fix it
http://weblogs.asp.net/scottgu/archive/2006/04/22/Always-set-the-_2200_applicationName_2200_-property-when-configuring-ASP.NET-2.0-Membership-and-other-Providers.aspx
I have made changes to my global.asax file so i want to recycle my web application to make the changes work. How to safely recycle my asp.net web application in production server?
View 3 RepliesI have deployed simple application on production server it just update sql server table via update query.
The problem is That when I run that app on development machine it updates table on remote server but after deploying it on production server and accesing the url on production server/and development machine my code doesn't execute and thus it don't update table.
I have created virtual direcotry and configured app with specific application pool which is custom based Asp.net account.
I have an ASP.NET web application that has the following settings in the web.config file:
[Code]....
(The actual names are different, obviously.) I am not a member of the real "Valid Site Users" group which is why I am given explicit access.I am able to access the site without a problem while developing and debugging locally; however, I get a 401 (Unauthorized Access) error when I deploy the site to a server. The only way to gain access is to remove the <deny> element from the configuration, which is not an acceptable option.I'm certain the solution is something simple and I am just overlooking
I am rather new to asp.net but I have built a couple of apps that do not require users to login. am having some problems moving my secure .net application from my laptop to a production server, however, and I am hoping someone can help me. On my laptop my application's user authentication functions as it should, but when I move my application to a webserver I get an assortment of errors. Forgive me if these questions are a little basic. My first question is this. In a production environment do I move the ASPNETDB.MDF file in the App_Data folder to my SQL server? Is it OK to rename it to something more descriptive?
View 4 RepliesSometimes I would like to be able to update during day time my ASP .Net application. I noticed that quite often updating DAL's (.xsd files) that are in used will block my application (and users). The only way, I found to recover, is to restart IIS but my users do not like it.
Is there some more clean way to update an online server without disrupting the users ?
Could I identified the DAL which are in used and the users using them, so that I could somehow disconnect only these users (My application uses Windows authentication).
I run a asp.net 4.0 website. (I did the porting from version 3.5 to 4.0)I receive the following error :ASP.NET AJAX client-side framework failed to loadn a page where I set scriptmanager EnableCdn="true" and there is a microsoft ajax extension Timer on the page.
[Code]....
I receive the error only on the production server.
We have had some problems with using a unmanaged DLL file written in Delphi. (Unable to load dll - not found...)The following code solved the problem on my local machine:
[Code]....
1) The elusive DLL is copied to the ASP.NET temporary files folder2) To check this we get a list of files from that folder.3) The needed function is called with DLL-import.1 & 2 works perfectly - both run directly from Visual Studio 2010 and when uploaded to a webhotel3 works perfectly local, but causes the remote host to think a little and then return a HTTP 503 Service Unaviable error for the next few minutes...
I am working on the MVC storefront Rob Conery project and I lost my ASPNET.mdf database !I would like to have the ASPNET.mdf database in my App_Data folder. I tried to include the db right clicking on it and including it in the project. But on the Server Exporer when I am tring to look at tables there are none.
<connectionStrings>
<add name="ApplicationServices" connectionString="data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true"
providerName="System.Data.SqlClient" />
<add name="CoderForTradersConnectionString"
[code]...
I encrypted my web.config file and I copied this file to the production server. But I get an error. But without encrypting - it's ok. I used:
C:WindowsMicrosoft.NETFramework64v4.0.30319aspnet_regiis -pef "appSettings" "C:inetpubwwwrootSite1" -prov RsaProtectedConfigurationProvider
I don't have access to IIS. Is it possible to encrypt config file and everything works?
I have an MVC web application, the urls like following in my views folder:
<img src="../../Images/Delete.png"/>
are working on my localhost, but when I deployed the application on production server, they stopped working and when I use single ".." instead of double "../.." , they start working on production server.
I created an ASP.NET Website that requires user authentication. I am using VS 2010 Pro and SQL Server 2008R2 Express. On my local machine I established login capability using ASP.NET Configuration, which works fine. When running the website on my local server instance, I can login just fine. The site now has a folder titled App_Data containing the ASPNETDB.MDF data file. My Hosting site requires me to make a backup of the local database (*.bak), upload the .bak file to their site, then run a database restor
View 16 RepliesI have an application that uploads an Excel .xls file to the file system, opens the file with an oledbconnection object using the .open() method on the object instance. The upload and writing of the file to the file system works fine but I get an error when trying to open the file on our production server only. The application works fine on two other servers (development and testing servers).
string connectionString = ("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + fileName + ";") + "Extended Properties="Excel 8.0""
OleDbConnection connection = null;
connection = new OleDbConnection(connectionString);
connection.Open();
The exception comes on production server at connection.Open() some times, when I reset the asp.net worker process it started to work but after some hours/days It occurs again. how can I fix this issue which comes in production some times but very irritating, or there is some other work around.
Server Error in '/staff' Application. Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'. Source Error:
[Code]....
Stack Trace:
[Code]....
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
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
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
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.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
My hosting provider connection string ..
<add name="ConnectionString" connectionString="Data Source=69.16.253.19;Initial Catalog=usa_data;Persist Security Info=True;User Id=user;Password=pass" providerName="System.Data.SqlClient"/>
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 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.
View 4 Replieshow 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.
View 2 RepliesI 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.
View 9 RepliesI'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 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.
View 2 RepliesI 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 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):
[Code]....
On one server I have my ASP.NET 3.5 website running just fine. That server is the one we use for testing (IIS6 with ASP.NET 2.0.50727). I went to the live server where ASP.NET is also installed (IIS6 with ASP.NET 2.0.50727). I right-clicked on the folder I wanted my website to go in, and I set it as an application in IIS. But when I go to the website on the live server, I get the Runtime Error. Like the error told me to do, customErrors mode is "Off" in the web.config file. I even changed authentication mode to "None" (it was set to Windows on the test server). Yet I still get this error. Is there something I should change about the web.config file? Is there something I should check in IIS?
For reference, here is the full error message. Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
[Code]....
I am trying to run an aspx file on my server windows 2003 with IIS 6.0. I get the following error. Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local
server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
[Code]....
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 <customErrors> configuration tag to point to a custom error page URL.
[Code]....