ASP.NET Denied Access to IIS Directories

ASP.NET V1 RTM now runs using a less privileged windows account – registered as the "ASPNET" account on a local machine. On some locked down systems, this account may not by default have read security access to a website’s content directories, the application root directory, or the web site root directory. In this case you will receive the following error when requesting pages from a given web application:

Write errors to the Event log

Writing to the Windows 2000 Event Log is a powerful feature of the ASP.NET and .NET framework. For those individuals who work in a large company and want to make track application errors, writing to the event log is a must! There wasn't any complete demos actually showing from A - Z how this was setup for the novice/common developer like me. Most novice developers need to be spoon fed how things are done the first time, once they see a simple example, they'll understand how the process works!

Symbols and Crash Dumps

I don't know about you, but in my day job I'm bouncing back and forth so much between .NET and Win32® that my head is spinning. In this month's installment of Bugslayer, I want to discuss some very cool advances that Microsoft® has developed to make debugging your Win32-based applications easier. Anything you can do to stamp out those Win32 bugs faster means you can spend more time playing with your XML Web Services! I'll start out this column by covering the hot new symbol server technology

Introduction to Exception Handling in Visual Basic .NET

Summary: This article provides an overview of structured and unstructured exception handling in Visual Basic .NET. It includes considerations that help you choose the right exception-handling alternative, the approaches involved in each alternative, how to create your own exceptions, and the exception object's properties. A table at the end lists the predefined exception classes and their derived classes. (17 printed pages). Introduction Only perfect programmers create perfect code from th

Exceptions in ASP.NET

ASP.NET uses VB.NET as language of choice and so it inherits all of VB's new features. One of these is exception handling with the System.Exception class. This new feature allows ASP developers to debug at runtime rather than have to build tricky coding to try and catch the different types of errors that they think will happen at runtime. Because ASP.NET uses VB.NET all of these samples can be moved across to a VB.NET application with ease.

Displaying Custom Error Pages

ASP.NET uses the web.config XML file to implement configuration settings for your .NET application and is placed in the root directory of where your application files exists. The web.config can also be placed in sub directories which take precedence over any configuration files above them. The configuration file can implement many types of settings for you application including the version of the common language runtime to use, runtime behavior, configuration properties to use over all applic

Web Application Error Handling in ASP.NET

All applications should have error handling. This we all know. We can't always be notified of an unhandled error (and usually aren't) when one occurs on a client's machine. The advantage we have on the Web is that we can always be notified when an unhandled error occurs. With the advent of ASP.NET, there are some great new ways to handle errors. There are some differences in .NET in not only how to handle the error, but how the information is provided to you. For example, classic ASP uses Server

Displaying Event Log Entries

The Sarbanes-Oxley Act and its related security auditing requirements have had a large impact on the need to monitor and audit IT environments. RippleTech's LogCaster for Sarbanes Oxley Software (http://www.rippletech.com/products/) is one of the products up to the task (more). Under Windows 2000 (or NT) the Event Log is about the most important source of information for the administrator because all events that occurred are logged there - from success to catastrophical failure. And as it is

Logging Unhandled Page Exceptions To The System Event Log

Error handling is a critical part of building enterprise level web applications, for that matter, it is a huge page of any application. In one of last weeks article we discussed using the Try...Catch...Finally statement to catch and respond to exceptions thrown during the page execution process. In this article I will be introducing a new way to catch Page-Level exceptions by introducing the HandleError Method. I will demonstrate what the firing order of the two are (try..catch..finally and Hand

Using the Try...Catch...Finally Statement

Structured error handling will be a completely new concept to Visual Basic and VBScript developers. Since the .NET Framework requires the use of Strong Typed Languages, such as Visual Basic it is time to learn how to use this method of error handling. Background Up until ASP.NET only unstructured error handling has been available within a web page, as with prior versions of Visual Basic. For those of you who are not aware what unstructured error handling is please see Listing 1.1 for a lis

Custom Errors in ASP.NET

Structured exception handling is a fundamental part of the CLR and provides .NET programmers a great way of managing errors. In addition to CLR exception system, ASP.NET also provides ways of handling errors. When a runtime or design-time error occurs in an application, ASP.NET shows a default error page that gives a brief description of the error along with the line number on which the error occurred. A developer would wish to view this default error page, during the testing of the applicati

Handling Timeouts in Web Services

While developing web applications you should also consider factors like network downtime and server crashes. The same applies to developing web services. When you call a method from your client by default it waits infinitely for the response. This means if server hosting the web service is down then you are bound to get error after a long wait. In this article we will how to deal with such timeouts in web services.

An Exception to the Rule

Let's face it, when we write Web applications we occasionally have bugs (or in our more politically correct world, issues) within our code. Unfortunately, it always seems that the more senior the tester, that is CEO, CIO, board members, VC, and so on, the more frequent or serious these issues tend to be. If you did any development what so ever in ASP, you'll recall a wonderfully helpful ASP error messages similar to:

Writing Exceptional Code

I've had some interesting discussions recently about the move from the "error code" style of error handling to the use of exceptions in the .NET world, and that's the main reason I've decided to devote a couple of columns to the subject (the secondary reason being that my column is due tomorrow, and I haven't thought of any other topics). This month, we'll talk about the how's and why's of using exceptions, and next month we'll talk about the ins and outs of writing exception classes.

C# Error Handling

Error handling is an important aspect of software development. The quality of software is often a product of how well the application responds to unexpected events. When an error occurs it is important to determine why that error occurred and take appropriate steps to handle it. C# provides several mechanisms to aid in error handling. Most notable is the concept of exceptions and exception handling. Additionally, the .Net platform also makes it very easy to log messages to the Windows NT Ev

Error handling

Here is my first tutorial; I hope that it will be a good starting point for some of the beginners. Catch errors with coding can make the programmers’ and the users’ life a little easier and a lot less graying hair. If you are from a VB6 background; well throw out the ideas of using On Error Goto or Resume Next—those things DO NOT EXIST in C#-land. So lets get to the areas of catching errors with ASP.net and C#. So what types of errors there are? Syntax –This is a basic typos or

Exception Handling in C#

Summary Exception handling is an in built mechanism in .NET framework to detect and handle run time errors. The .NET framework contains lots of standard exceptions. The exceptions are anomalies that occur during the execution of a program. They can be because of user, logic or system errors. If a user (programmer) do not provide a mechanism to handle these anomalies, the .NET run time environment provide a default mechanism, which terminates the program execution. Introduction C# provides

A custom "404 Page Not Found" in ASP.NET

In this article we will see how to create a custom 404 Response error page in ASP.NET, which will: 1. produce a friendly output to the user 2. send an email to the webmaster letting them know about the broken link so they can fix it.

Custom Errors in ASP.NET

Structured exception handling is a fundamental part of the CLR and provides .NET programmers a great way of managing errors. In addition to CLR exception system, ASP.NET also provides ways of handling errors. When a runtime or design-time error occurs in an application, ASP.NET shows a default error page that gives a brief description of the error along with the line number on which the error occurred. A developer would wish to view this default error page, during the testing of the applicati

The First Step in Debugging ASP.NET

My first experience with programming was with Visual Basic. That said, having and using breakpoints was a tremendous help for developers when it came to debugging and testing code. When I started to dabble with Classic ASP, the only way to debug was to simply insert a RESPONSE.WRITE(“ERROR GOES HERE”) line of code in your application. Well, they don’t call it Classic ASP for nothing. If you are developing with the .NET framework and you still use the good ‘ole RESPONSE.WRITE, I have