Is there a solution to fix the HTTP500 error message without changing browsers?

HTTP status 500 (Internal Server Error) indicates that an internal error occurred while the server was executing the request. This could be due to a problem with the server's application, or a problem with the server's internal settings.

Common causes of HTTP status 500 are:

An exception occurred while the program was running.

Program bugs

The server is running out of memory.

Server hardware failure.

There is a problem with the server operating system.

If you are running a network terminal and you are experiencing an HTTP status** 500 error, we recommend that you check the server logs for the specific cause. Depending on the information in the logs, you may need to fix bugs, increase the memory usage of your server, or replace your server's hardware, etc.

Repair your network with 360 network repair.

Method 1: You must be able to get the error message correctly in the HTTP method:

Please open the browser, select Tools, Internet Options, Advanced, there is a checkbox in the browsing item in Advanced "Show HTTP friendly error prompt", please uncheck the checkbox, and close the window and reopen the Internet Explorer browser, you can get the correct error prompt, after that, you can check your specific error cause according to the error prompt.

Method 2: After deleting the system SAM file, IIS reports a 500 error. Method 3: This method requires multiple attempts to find a solution.

Change the password of iWAM MyServer [MyServer is local computer name] in the Management Tools.

Then, in CMD, change the internal account of IIS to the new password that has just been changed.

Then in the admin tool, confirm that it is in the guest group in the IWAM My Server user's properties in the user group, then right-click on the users group property in the local users and groups group, and add the members authenticated users and interactive, and then OK.

After the above work is done, it is necessary to synchronize the com+ component account and enter the command in cmd.

Contact the administrator of the **, the 500 error means that the IIS server cannot parse the web page**, and the problem is not caused by the client, nor can the client solve it.

The path of the iis bind ** is wrong, we should bind 12345, but we bind the 123456, which will also cause the **500 error.

The 500 InternalServer Error is mainly caused by the wrong password for IWAM. This error indicates that the IIS server is unable to resolve ASP**, and if you visit a static page to see if this problem also occurs.

If there is no problem with accessing static pages, then it is necessary to analyze the following situations:

Have you ever changed the name of your computer?

Whether the file directory where the site is located has custom security attributes.

Whether the domain policy has been adjusted after the domain controller has been installed. If this is one of the cases, please check back the changed parameter settings one by one to see if the problem is solved. If the static space cannot be accessed, the parsing has not yet taken effect.

First you need to determine the cause of the error:

Let IE display detailed error information: Menu - Tools - Internet Options - Advanced - Show friendly HTTP error messages, remove this selection of Yu Bury Li Choose, and then refresh the error page, you can see the detailed error information, which is very helpful to help you determine where the error is!

Common causes of Liquid 500 errors are: ASP syntax error, access database connection statement error, file reference and inclusion path delay error (for example, the parent path is not enabled), and the use of components that are not supported by the server, such as FSO.

Another explanation: Unable to execute asp file under xp, error! 500 Internal Connection Error|Resolution.