The reason and solution for the internal server error in HTTP 500

When you try to load the localstart. asp file
When a Web site's default document is iisstart. ASP tries to load localstart. if the user attempts to access this page does not have to run localstart. if the script in the ASP file has the correct permissions, you will receive an HTTP 500 error message. If you clear the show friendly HTTP Error Message check box, you will see information similar to the following HTTP 500 error message:
Error Type:
Microsoft VBScript Runtime (0x800a0046)
Permission denied: 'getobject'
/Localstart. asp, line 19
The cause of this problem is that the localstart. asp file contains the Active Directory Service Interface (ADSI) and Visual Basic Scripting Edition (VBScript) code that uses the IIS Admin object to access the metabase. For security reasons, only members of the Local Administrators Group can access the metabase. This phenomenon is caused by design.
To solve this problem, follow these steps:
Click Start, point to program, point to administrative tools, and then click Internet Information Service.
In the console tree, click the default web site. In the display pane, right-click localstart. asp and click Properties.
On the file Security tab, under anonymous access and authentication control, click Edit.
On the authentication method properties page, click to clear anonymous access.
When browsing ASP pages
When you browse the Active Server Pages (ASP) web page, you will receive the "HTTP 500.100-Internal Server Error-Asp error" error message. If the check box for displaying friendly HTTP Error messages is cleared, the following information is displayed in the "Technical Information (for support staff)" section:
Error Type:
Microsoft VBScript Runtime (0x800a01f4)
Variable is undefined: 'X'
/Optionexpliciterror. asp, line 9
Page:
GET/optionexpliciterror. asp
To solve this problem, delete the option explicit statement or use the dim keyword to declare the variable.
When IIS 5.0 returns the server. getlasterror error message
When a web application or page is unavailable, IIS returns an error message. The result is a custom ASP page that handles responses to server-side script errors. This page returns the status "500 internal server error", which causes the client Remote Script applet to not return any data to the remote script object.
To solve this problem, create a custom error page with the returned status "200 OK" and reference this page on the remote script server page or the application's "custom error" section. To do this, follow these steps:
Note: You can set this custom error page for each page, the entire application, or the entire web site or web server.
Create a copy of % SystemRoot %/winnt/help/IISHelp/common/500-100.asp and store it in the same folder as the original file. Name the new file 500-100-ok.asp.
Click Start, point to program, point to attachment, and then click notepad.
In notepad, click open on the File menu. In the search range drop-down box, browse the 500-100-ok.asp file and click open.
Run the following code response. Status = "500 internal server error"
Replace with: Response. Status = "200 OK"
Note: If you have not modified the error message before, the original code behavior is 12th lines.
In the File menu, click Save.
In the console tree of Internet Service Manager, click your web server. If your remote script ASP page is located in a web application under one of the web sites, expand your web application.
In the details pane, right-click your remote script Server ASP page and click Properties.
Click custom error. In the list, search for items 500; 100. By default, this item is set to a URL and reference help/common/500-100.asp. Click Edit properties.
Modify the path to/IISHelp/common/500-100-ok.asp, click OK, and then click OK again
When assigning classes to files on Alpha or Unix
When assigning a category to files on Alpha or UNIX, an HTTP 500 error message is returned.
To resolve this issue, install Microsoft Office 2000 Service Release 1 (SR-1) or Service Release 1A (SR-1a ). To download the Office 2000 SR-1, see the following Microsoft Web site:
Http://office.microsoft.com/downloads/2000/O2kSR1DDL.aspx
When you use the 500-100.asp file for error handling on non-default web sites
When you use the 500-100.asp file for error handling on non-default web sites, you will receive an HTTP 500 error message. To solve this problem, follow these steps:
In the console tree of the "Internet Information Service" Management Unit, right-click the corresponding web site, click New, and then click virtual directory.
In the create virtual directory wizard, click Next. In the alias text box, type IISHelp and then click Next.
When you are prompted to enter the path of the content folder, Click Browse, select the WINNT/help/IISHelp folder, and then click Next.
On the access permission page, accept all default values, click next, and then click Finish.
Right-click the web site again and click Properties.
On the custom errors tab, select "500; 100" and click Edit properties.
In the URL text box of the information type list box, type/IISHelp/common/500-100.asp.
Click OK, and then click OK again.
When performing a query on the Index Server
When you click go to perform a query on the Index Server, you may receive an HTTP 500 error message.
The cause of this error is that no default application start point is defined for the folder containing the query page.
To solve this problem, follow these steps:
In the console tree of the "Internet Information Service" Management Unit, right-click the root directory of the site that contains the query page, and then click Properties.
On the Home Directory tab, click Create.
Click OK and then retry the query.
When accessing the provider from the ASP page
If the show friendly HTTP Error Message check box is cleared, when you try to access the provider from the ASP page, you may receive the following error message:
ADODB. Connection (0x800a0e7a) provider cannot be found. It may not be properly installed./nwind. asp, line 10
This error occurs because the dynamic link library (DLL) required by the Microsoft Data Access Component (MDAC) is not yet registered.
Click Start, click run, and then type cmd.
At the command prompt, type cd % SystemRoot %:/program files/common files/system/Ole.
At the command prompt, type regsvr32 sqloledb. dll.
After receiving the confirmation of successful DLL registration, click OK. Note: This solution uses Microsoft SQL Server Ole provider DLL (sqloledb. dll) as an example. Because unregistered dll may vary with the ole db provider, you must modify Step 1 as needed.
When setting the COM + Application ID on IIS 5.0
When you try to set the COM + Application ID on IIS 5.0, you will receive an HTTP 500 error message.
This issue occurs when the identification of the COM + application or Microsoft Transaction Server (MTS) package is configured as an interactive user-currently logged on to the user. The application cannot run because no user has logged on to the IIS console.
To solve this problem, set the COM + application or MTS Package identifier to this user, and then specify a user account. To do this, follow these steps:
Click Start, point to program, point to management tools, and then click component service.
In the console tree, expand component services, computers, my computers, and COM + applications. Find the application whose ID you want to change.
Right-click the corresponding COM + application and click Properties.
On the identity tab, click this user, type A valid computer account, and click OK.
When you set the MTS Application ID on IIS 4.0
When you set the MTS program identity on IIS 4.0, you will receive an HTTP 500 error message.
To solve this problem, follow these steps:
In the "Internet Information Service" Management Unit, expand the computer, my computer, and Microsoft Transaction Server. Find the package whose ID you want to change. Applications are listed in the "installed application packages" folder.
Right-click the package and click Properties.
When IIS 4.0 runs in its own memory space
If any of the following conditions is met, an HTTP 500 error message is returned:
The default web site of IIS 4.0 runs in its own memory space as an independent process.
Microsoft Internet Explorer is configured to use the Web Proxy Server on Proxy Server 2.0.
Internet Explorer on BackOffice small business Server 4.5 is configured as a proxy server, and Proxy Server packet filtering is enabled.
To solve this problem, follow these steps:
Click Start, point to program, click Microsoft Proxy Server, and then click Microsoft Management Console.
In the console tree, expand the Internet Information Server folder and then expand the server object.
Right-click the default web site and click Properties.
On the Home Directory tab, locate the application settings area and click to clear the independent processes running in a separate memory space ).
Click application, and then click OK.
Right-click the default web site and click STOP.
Right-click the default web site and click Start.