Server Application Unavailable

What is happening? Out of a sudden, when accessing asp.net website, this error message is showing up instead of a normal webpage.

Oh my god... Checked on the IIS, every setting is correct, verify file is there, permission is correct as well.

I even tried setting Everyone's permission to Full control but this is not solving the problem.

So my next step?
Re-registering aspnet_regiis.exe -i
(c:\windows\microsoft.net\framework\v2.0.50727\aspnet_regiis -i )

And Voila, everything works back to normal. YAY!!!

If the above still couldn't fix your problem, you can try the solution in this link, http://blog.crowe.co.nz/archive/2005/08/30/242.aspx

Cheers, :)

HTTP Error 404 - File or Directory not found

What happen?
Encountered this problem on my VPC (Virtual PC), Windows 2003, IIS 6.0.
When I try to view default.asp or default.aspx file, nothing seems to work.
The error returned in the browser was:

HTTP Error 404 - File or Directory not found.

Search the web and found this useful site from microsoft which explains why it happen and the solution: http://support.microsoft.com/kb/315122

What's the problem?

When you request dynamic content such as an Active Server Pages (ASP) page, an ASP.NET page, an Internet Services API (ISAPI) application, or a Common Gateway Interface (CGI) application on a Microsoft Windows Server 2003 server that is running Internet Information Services (IIS) 6.0, you may receive one of the following error messages:

• Error message 1
  HTTP Error 404 - File Not Found
  
• Error message 2
  HTTP Error 404- File or Directory not found

Cause?
By default, when IIS is installed on any version of the Windows Server 2003 family, IIS only serves static content (HTML).

The Solution?
Enable a Pre-existing Web Service Extension in IIS 6.0

To permit IIS to serve content that requires a specific ISAPI or CGI extension that is already listed in the Web service extensions list, follow these steps:

• Open IIS Manager, expand the master server node (that is, the Servername node), and then select the Web service extensions node.
• In the right pane of IIS Manager, right-click the extension that you want to enable. In this example, this is Active Server Pages.
• Click to select the Allow check box.

For more information on this, refer to http://support.microsoft.com/kb/315122

Error '80040211' When Sending Email in ASP

All this while, the web server used to host a web application that sends out email when a request is submitted suddenly couldn't send email anymore.
Error returned was this weird figure: Error '80040211'.

Seek my best buddy help: Google and found this link:
http://forums.aspfree.com/asp-development-5/error-80040211t-96396.html

Based on the forum, what that guy did is basically change the 'sendusing' fields from 2 to 1.
I tried and the trick works. ^_^

And from the explanation from MSDN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/bb2a4e60-080f-49bf-be71-e2a7e52ce5ad.asp

cdoSendUsingPickup (value 1)
Send message using the local SMTP service pickup directory.

cdoSendUsingPort (value 2)
Send the message using the network (SMTP over the network).

Couldn't convince myself why this happens since my web server is over the network, but it works. Let's put this on for now, while I'm busying with another project at the moment.

ERROR: Object reference not set to an instance of an object

Problem occurs after the reinstallation of IIS in the web server (since out of a sudden --> might be due to a patch, the IIS is corrupted).

Accessing ASP page works fine in the localhost, but gives this error when accessing .Net page
"Object reference not set to an instance of an object".

Googled the web and found few links that teach on how to solve:

1. Support from Microsoft: http://support.microsoft.com/kb/810098

2. Common causes in VB.net: "http://codebetter.com/blogs/raymond.lewallen/archive/2005/06/23/65033.aspx"

3. Re-registering aspnet_regiis.exe -i: http://dev.communityserver.com/forums/p/474748/531732.aspx

Item #1 and #2 didn't fix my problem, but the #3 did.

Basically, to prevent this error, you need to install IIS before install .Net Framework. If you did the reverse way, the .Net framework somehow are not registered in IIS. Therefore, you need to run the command again "aspnet_regiis.exe -i" to install it.

Screenshot of running the command in cmd prompt: