function refreshTime(options) { $.ajaxService({ url: 'http://localhost:1549/Store/Pages/services.aspx?ServiceName=hello-world', data:{ oldpassword: $('#oldpassword').val(), newpassword: $('#newpassword').val() }, onStartService: function () { $(options.target).addClass('loading'); }, onEndService: function () { $(options.target).removeClass('loading'); }, onResponse: function (response) { if (response.result == '1') { $.pushMessage({ message: 'success changed', messageClass: 'success-message', delay: 3000 }); } else { $.pushMessage({ message: 'error in change password', messageClass: 'success-message', delay: 3000 }); } } }); }
NameValueCollection ResponseResultCollection = new NameValueCollection(); protected void Page_Load(object sender, EventArgs e) { System.Threading.Thread.Sleep(2200); string serviceName = this.Request.QueryString["ServiceName"]; if (!string.IsNullOrEmpty(serviceName)) { switch (serviceName.ToLower().Trim()) { case ("hello-world"): string oldpassword = Request["oldpassword"].ToString();//i get null this string newpassword = Request["newpassword"].ToString();//and get null this try { System.Web.Security.MembershipUser usr = System.Web.Security.Membership.GetUser(); if (usr.ChangePassword(oldpassword, newpassword)) ResponseResultCollection["result"] = "1"; else ResponseResultCollection["result"] = "0"; } catch (Exception ex) { Response.Write("An exception occurred: " + Server.HtmlEncode(ex.Message) + ". Please re-enter your values and try again."); } break; } } Response.Write(this.GenerateResponseResult()); Response.End(); } private string GenerateResponseResult() { string result = ""; foreach (string key in this.ResponseResultCollection.AllKeys) { result += string.Format(",\"{0}\":\"{1}\"", key, this.ResponseResultCollection[key]); } if (!string.IsNullOrEmpty(result)) { result = result.Substring(1); result = "{" + result + "}"; } return result.ToString(); }
Quote:The 500 Internal Server Error is a very general HTTP status code. It means something has gone wrong on the website and webserver is unable to specify what exactly, thus failing in fulfilling the request made by the client. This is not related to client and the fault is in the webpage/website requested that resides on server. This status code can be considered as a ‘catch-all’ server error of Web server.
Quote:Make sure that internally web server maintains some kind of internal error logs that gives more detail of what went wrong and thus help in diagnosing the issue. Generally, it is logged into Windows Event Logs on the server. Thus, first thing while troubleshooting the error is to see Windows Event Logs on the server to find what went wrong. Other useful thing to troubleshoot it would be to disable friendly HTTP error messages to see if the raw content can provide a direction to look more. Steps: Go to menu Tools/Internet Options in your IE. Click on the Advanced tab & then uncheck “Show friendly HTTP error messages” option and then click OK. Now, when on accessing the same web page, much more developer meaningful error message will be shown. Moving on, following are most common: Option #1: HRESULT: 0×80070035 – The page cannot be displayed because an internal server error has occurred. This occurs because the server that is running IIS cannot access the configured root directory of the requested location. Resolution would be to make sure that the server that is running IIS can access the configured root directory of the requested location. Option #2: HRESULT: 0x800700c1 – The page cannot be displayed because an internal server error has occurred. This occurs because a script mapping is not valid. Resolution would be to make sure that the script mapping points to the ISAPI.dll file that can process the request. To do this, follow these steps: Click Start, click Run, type inetmgr.exe, and then click OK. In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify. In Features view, double-click Handler Mappings. Make sure that the script mapping points to the correct ISAPI.dll file. (e.g.: .asp files should map to the %windir%\system32\inetsrv\asp.dll file) Option #3: HRESULT: 0x8007007f – There is a problem with the resource you are looking for, so it cannot be displayed. This occurs because the handler mapping for the requested resource points to a .dll file that cannot process the request. Resolution would be to edit the handler mapping for the requested resource to point to the .dll file that can process the request. To do this, follow these steps: Click Start, click Run, type inetmgr.exe, and then click OK. In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify. In Features view, double-click Handler Mappings. Right-click the script mapping that you want to edit, and then click Edit. In the Edit Script Map dialog box, type the appropriate executable file in the Executable box, and then click OK. Option #4: One of the other possibilities could be an issue in the way web application is hosted. Some security configuration issue or conflict due to multiple config files. Resolution would be to make sure application is hosted correctly by published the application as website and setting up the virtual directory as needed.
var
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)