There are many causes for HTTP 500, which can be determined based on the HTTP status code. For example
HTTP 500-Internal Server Error
HTTP 500.100-Internal Server Error-ASP Error
HTTP 500.11 Server Disabled
HTTP 500.12 application restarts
HTTP 500.13-the server is too busy
HTTP 500.14-invalid Application
HTTP 500.15-requests to global. asa are not allowed
Based on the above status code, you can determine the possible causes of the problem.
Development Environment: VS2012
Database: SQL Server 2008
Scenario: deployed on an ASP. NET VM
In general, the code is unlikely to have a problem. If the Error 500 still occurs after the tested function can meet the requirements for normal use. Consider the following reasons:
The program runs normally in the local system, but is deployed on the remote server. When you access the aspx page, an HTTP 500 error occurs.
<connectionStrings configProtectionProvider="RsaProtectedConfigurationProvider"> <EncryptedData Type="http://www.w3.org/2001/04/xmlenc#Element" xmlns="http://www.w3.org/2001/04/xmlenc#"> <EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/> <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"> <EncryptedKey xmlns="http://www.w3.org/2001/04/xmlenc#"> <EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/> <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"> <KeyName>Rsa Key</KeyName> </KeyInfo> <CipherData> <CipherValue>data</CipherValue> </CipherData> </EncryptedKey> </KeyInfo> <CipherData> <CipherValue>data</CipherValue> </CipherData> </EncryptedData> </connectionStrings>
After checking, it is found that the preceding connection string encryption configuration section is used in the configuration file. The remote server IIS may not support this configuration section, resulting in a 500 error. After removing this configuration section, the website will work normally.
This article is from the "experience the beauty of technology" blog, please be sure to keep this source http://1606029.blog.51cto.com/1596029/1305097