Problem cases caused by HTTP500 errors and http500 Problems

Problem cases caused by HTTP500 errors and http500 Problems

**************************************** ******************************** **************** 

Original Works are from the "Deep Blue blog" blog. You are welcome to reprint them. Please note the following source during reprinting. Otherwise, the author reserves the legal liability for copyright.

Link: http://blog.csdn.net/huangyanlong/article/details/39161255

Blog: http://blog.csdn.net/huangyanlong

Please leave a message or email (hyldba@163.com) indicating that there is an error. Thank you very much.

**************************************** **************************************** ********************

**************************************** *********************

Case 1: problems caused by resources (experimental virtual machines)

**************************************** *********************

Small Problems Encountered in WAS cluster exercises:

For WAS cluster exercises, the HTTP500 error is displayed, as shown in:

Resources are located at http500, with fewer resources allocated to virtual machines in the experiment environment. As a result, the memory of the was Cluster Server is increased from 1 GB to 2 GB, the server is restarted, and the application is successfully logged on. The problem is solved.

**************************************** ******************************** **************** 

Original Works are from the "Deep Blue blog" blog. You are welcome to reprint them. Please note the source when you reprint them. Otherwise, the author will hold the copyright legal liability accountable.

Link: http://blog.csdn.net/huangyanlong/article/details/39161255

Blog: http://blog.csdn.net/huangyanlong

Please leave a message or email (hyldba@163.com) indicating that there is an error. Thank you very much.

**************************************** **************************************** ********************

**************************************** *********************

Case 2: problems caused by network connection (experimental virtual machine)

**************************************** *********************

The following error is reported when a web client logs on to an application deployed on a single WAS node:

Check the WAS service, which is normal, such:

Check the java process. The process is normal, for example:

View Application Status: started, normal, as shown below:

Database connection test: failed!

On the application server, the database server cannot be pinged, as shown below:

Modify the VM connection mode:

After modification, as shown in:

Ping the database server from the application server again, as shown in figure:

Test the database connection again in WAS. The connection is successful, as shown in:

At this time, the client web login is successful.

 

**************************************** *********************

Case 3: monitoring problems (production environment)

**************************************** *********************

Problem Review: "HTTP 500 error" is reported during client login ". It is found that the listener is not started normally, and the client cannot connect to the database.

Solution: reconfigure the listener, start the listener, and use the client to log on again for verification. The connection is normal.

**************************************** ******************************** **************** 

Original Works are from the "Deep Blue blog" blog. You are welcome to reprint them. Please note the source when you reprint them. Otherwise, the author will hold the copyright legal liability accountable.

Link: http://blog.csdn.net/huangyanlong/article/details/39161255

Blog: http://blog.csdn.net/huangyanlong

Please leave a message or email (hyldba@163.com) indicating that there is an error. Thank you very much.

**************************************** **************************************** ********************

Http 500 Error

When a 500 error occurs, many people do not know how to handle it.

Method 1: You can set the properties of the test server on the site in Deamwaver, open the page to debug, and click a lightning icon next to the design view to debug errors. Locate the actual error location.

Method 2: Use Deamwaver to open the page for debugging. Cut all the content of the page and save it, but do not close the file. When you browse this page in a browser, you will see a blank page. Do not close the browser. Then UNDO the content in Deamwaver, restore it, and save it. Then refresh the browser and you will see the real error.

Why is an http500 error?

The internal HTTP 500 error is mainly caused by the wrong password of the IWAM account (my computer is the IWAM_MYSERVER account.

Before analyzing the cause of an internal error in HTTP500 in detail, let's give a brief introduction to the IWAM account: the IWAM account is a built-in account automatically created by the system when IIS5 is installed, it is mainly used to start the I nternet information service for applications outside the process. The name of the IWAM account varies depending on the NETBIOS name of each computer. The common format is IWAM_MACHINE, it is composed of the prefix "IWAM", the connection line "_", and the computer's NETBIOS name. My computer's NETBIOS name is myserver, so the IWAM account name on my computer IS IWAM_MYSERVER, which IS very similar to the way I IS named ISUR_MACHINE, an anonymous account.

After the IWAM account is created, it is used by the Active Directory, IIS metabase database, and COM + applications. The account and password are respectively saved by the three parties, the operating system is responsible for synchronizing the IWAM password stored by the three parties. Generally speaking, we can rest assured that we do not have to worry about errors, but we do not know whether it is B UG or another reason, the system sometimes fails to synchronize the password of the IWAM account, which leads to inconsistent passwords used by the third-party IWAM account. When IIS or COM + Applications use the wrong I WAM password to log on to the system and start IIS Out-Of-Process Pooled Applications, the system will reject this request due to a wrong password, this causes IIS Out-Of-Process Pooled Applications to fail to start, that is, the "cannot run server {3D14228D-FBE1-11D0-995D-00C04FD919C1}" we see in the ID10004 error event (here {timeout} is the KEY Of IIS Out-Of-Process Pooled Applications ), it cannot be transferred to the IIS5 application. An internal HTTP 500 error occurs.

Knowing the cause of an internal error in HTTP 500 makes it easy to solve the problem, that is, manually synchronize the password of the IWAM account in Active Directory, IIS metabase database, and COM + applications.

You must log on to the computer as an administrator in three steps to provide sufficient operation permissions (IWAM uses IWAM_MYSERVER as an example ).

(1) change the password of the IWAM_MYSERVER account in Active Directory

Because the password of the IWAM account is controlled by the system and generated randomly, we don't know what it is. To complete the password synchronization in the following two steps, we must set the password of the IWAM account to a value we know.

1. Choose Start> program> Administrative Tools> Active Directory users and computers to start the Active Directory users and computers Management Unit.

2. Click "user", select "IWAM_MYSERVER" on the right, right-click and select "Reset Password (T )... ", in the Reset Password dialog box that appears, set A new password for IWAM_MYSERVER. Here we set it to" A boutnt2001 "(without quotation marks). OK, wait until the password is successfully modified.

(2) synchronize the password of IWAM_MYSERVER account in IIS metabase

This change may be too sensitive and important. Microsoft did not provide an explicit user interface for us to modify the IWAM_MYSERVER account password in IIS metabase, and only provided a management script adsutil with iis5. vbs, this script is located in C: \ inetpub ...... remaining full text>