I've just uploaded an asp.net web project to a Fasthosts shared server (yes, I know!). The site works fine on a different server, and builds successfully. However, when I upload it (or even just the files in the App_Code folder) to the fasthosts server, I just get a flat error 500 message.
I've ensured that the web.config file includes: <customErrors mode="Off"/> but still nothing - just Error 500.
The Fasthosts server is running asp.net 3.5, which is what the web project is built to.
I 'm using visual studio 2007 and I have come up with an error in my web config that I have never come up with before. I have set customError mode "off" in my web config and I'm getting an error code of The 'mode' attribute is invalid ' The value 'off' is invalid according to it's data type 'NM Token' - the enumeration constraint failed what an 'NM token' is and what I can do to fix this problem? My page works perfectly when I'm working on it locally, but when I move it to the web server I get an error and it tells me to set the custom mode errors in the web config to 'off' This is the error I'm getting:
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".
When an error occurs (I type in a non-existing page in address), I get the default IE "page not found" page.This happens both on localhost in development, and of course in live environment.I think this started happening since a recent Microsoft Update, which included most recent updates to .net.
We developed an application in ASP.NET 3.5 on Windows Server 2003. (IIS 6.0)They are trying to deploy it on Windows Server 2008 IIS 7.5.But we are getting the old yellow screen message: Runtime ErrorDescription:
[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]....
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.Details: To enable the details of this specific error message to be viewable on the local server machine, 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 "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".We have turned off custom errors everywhere we can find in ASP.Net Error Pages and set it to Detailed Errors at all folder levels for IIS Error Pages.Still the yellow screen with custom errors and no detailed errors.If we switch the application pool to run in 32 bit = true, we get a detailed error. But we don't get very far with that because of Oracle issues and wouldn't really want to force it to run in 32 bit when it should really run in 64 bit anyway.So how do we get detailed messages from IIS while running in 64 bit?
I successfully implemented role based authorization in ASP.NET. When a person does not have the needed role he gets to see an error page for 401.2 not authorized.
What I would like to accomplish now is to have a custom 401 page in my application and have it redirected there via settings in the web.config. I tried this:
If I have a customErrors section in my Web.config that says to redirect to Error.html, then putting code in the Application_Error method in the Global.asax to redirect to Error.html is redundant is it not? Technically, I could bypass the Web.config by redirecting to a different page in the Application_Error method if I wanted to, but since I don't want to go to a separate page I don't think I need the code.
We usually catch unhandled exceptions in Global.asax, and then we redirect to a nice friendly error page. This is fine for the Live environment, but in our development environment we would like to check if CustomErrors are Off, and if so, just throw the ugly error.
Is there an easy way to check if CustomErrors are Off through code?
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".i got this error during login time on the server how it can be solved
The basic idea is we have a test enviroment which mimics Production so customErrors="RemoteOnly". We just built a test harness that runs against the Test enviroment and detects breaks. We would like it to be able to pull back the detailed error. But we don't want to turn customErrors="On" because then it doesn't mimic Production.
I've looked around and thought a lot, and everything I've come up with isn't possible. Am I wrong about any of these points?
We can't turn customErrors on at runtime because when you call configuration.Save() - it writes the web.config to disk and now it's Off for every request.We can't symlink the files into a new top level directory with it's own web.config because we're on windows and subversion on windows doesn't do symlinks. We can't use URL-Mapping to make an empty folder dir2 with its own web.config and make the files in dir1 appear to be in dir2 - the web.config doesn't apply. We can't copy all the aspx files into dir2 with it's own web.config because none of the links would be consistent and it's a horrible hacky solution. We can't change customErrors in web.config based on hostname (e.g. add another dns entry to the test server) because it's not possible/supported. We can't do any virtual directory shenanigans to make it work.
If I'm not, is there a way to accomplish what I'm trying to do? Turn on customErrors site-wide under certain circumstances (dns name or even a querystring value)?
By defauly in my web.config I have set the , in runtime I just want to change the Mode = "Off" in memory. I do not want to save the changes to web.config.
Basically we need to see the description of the runtime error, when required.
This is a yellow page which is not user friendly and we didn't expect . I'm wondering setting customeError in webconfig doesn't support this type of address or not ? How can i prevent users seeing this yellow page . Edit : solution you mentioned are about configuring IIS ,But as i mentioned earlier , my site has been published on shared hosting provider . I don't have those access at IIS , What should i do at this situation ?
I am having an issue where if I change my url to .asp from .aspx i get a 404 error but it is not handled by my custom errors. If I change the url to def23947823h.aspx it is caught and redirects to correct page.
Error: Executed as user: MACSTEELUSA.COMsa. ...9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:00:17 PM Error: 2010-06-02 20:00:18.56 Code: 0xC0202009 Source: CRM_ORACLE_ARSUMMARY Connection manager "SourceConnectionOLEDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for Oracle" Hresult: 0x80004005 Description: "Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed.". End Error Error: 2010-06-02 20:00:18.58 Code: 0xC020801C Source: Data Flow Task Source - Query [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireCon... The package execution fa... The step failed.
Tasks Taken:Went to this folder checked for tnsnames.ora file but it is in good shape.
I have a serious problem with "Error on Page". The error message points to line number 939, char 13. In my code behind (C#) in line number 939 is only an obsolete method found which is no longer called. The aspx file has only 339 lines. What the heck is line number 939?The Webapplication allows a special user group to change some group memberships for members of another user group in Active Directory. The App handles 3internal DataViews derived from corresponding DataTables as DataSource for 3 GridViews and some other internal lists with objects (List<obj>).
It uses windows authentication to get current users credentials and his membership in the "Operators" group. This credentials will be passed-through to allow the process managing group memberships in active directory.After starting the App in browser it seems to work fine. But after an indeterminated time it doesn't longer respond. After each click on buttons (or link buttons) you only can see the message "Error on Page" in the browsers status bar below.I played with session timeout, storing the DataTables in session variables, without success.
Last week I found this article here: [URL]" and I addedEnableEventValidation="false" ViewStateEncryptionMode="Never" to Page declaration. However, at some point the the server does not respond. Each time the worker process on webserver recycles it seems the application turn to wrong state. Might be important: All controls including GridViews are embedded in an AJAX UpdatePanel. How to get a better error message? Debugging is enabled and Custom Error handling On, Off or Remote Only brings the same result as described.
When a server error occurs for whatever reasons (YSOD), the server will send a message via SMTP class. In my case, my company employs microsoft exchange and uses NTLM authentication for all domain users. I am authenticating users via NTLA windows integrated authentication. My question is, is it possible to utilize this authentication data, and pass it to the system.web SMTP username/password authentication scheme to send an email to me (the web developer) when the error occurs? I am pretty sure my company requires a username/pwd to send emails via SMPT on the ms exchange server.
I'm receiving the following error occasionally when calling web service using a .NET 4.0 web application."The underlying connection was closed: An unexpected error occurred on a send."All of the articles I've read regarding this issue are for the Framework 1.1.Is there any solution to this issue for using .NET framework 4.0?
I am consuming a third party web service wsdl using my .net aps.net page. And I am getting following error message. Cannt get to resolve it. Its working on my machine but not in my development machine. I have installed the certificate also in certificates on that machine.
Error --> The underlying connection was closed: An unexpected error occurred on a send.
i write a site and get this error, i using VS2010.
An error occurred during local report processing.
The definition of the report 'ModulesReport1.rdlc' is invalid.
An unexpected error occurred in Report Processing.
Could not load file or assembly 'Microsoft.ReportViewer.ProcessingObjectModel, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
i try run on my machine its all work fine, but when i complier and run it on Window server 2008 get this error.
I read [URL] I install the ReportViewer.exe but still cannot find the Microsoft.ReportViewer.ProcessingObjectModel.dll, however I got find it Microsoft.ReportViewer.ProcessingObjectModel in C:Windowsassembly and is not a dll file.
I am REALLY stuck with this and need a solution in the next 24 hours .i I have uploaded my asp.net web application to the web and have the database and connection strings functioning and reading the data from the database. But when I try to write to the DB
I get the following error :
Server Error in '/' Application.
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.
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: 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: 26 - Error Locating Server/Instance Specified)
The wierd thing about this is the connection strings work from the local machine when I run from Visual Studio and I can write to the DB there, I just cannot write to the DB from the URL.
I am pretty new to asp.net but I am sure it has to be something to do with the web.config.
