IIS stuck with old SSL Certificate despite of deleting it from Server

Follow me Recently one of out client requested to configure remote app publishing through windows 2012 server. After configuring all remote app setting it failed because of certificate error as Remote app requires a valid trusted certificate to be installed so that the clients can open the applications from their desktop icon.  We went ahead and generated a self signed certificate on the remote app server and assigned it correctly on the required sites in IIS by editing the binding settings. Refer the screen shot below However despite of these changes the server kept presenting the old server certificate and hence the remote app wasn’t able to connect. I even deleted the old server certificate from the server and rebooted the server but still it kept presenting the old certificate. I researched further and found the following commands to check the installed certificates on the server and delete them as needed. Following command (ran from command prompt) display the certificates installed on a server. Netsh Http Show Sslcert   As we can see in the screenshot above, this command did reveal that the old certificate (which I had already deleted from the server) was still present on the server. The old and new certificates can be identified from the certificate hash value.   I used the following command to delete the non required stale certificate from the server Following command (ran from command prompt) deleted the required certificate from the server. Netsh delete Sslcert Ipport=[::]:443 (please replace IP Port value with your required value After this SSL certificate was deleted we ran the following command again and validated that its showing only...

IIS Application Pool Keeps crashing:A listener channel for protocol ‘http’ in worker process reported a listener channel failure

Follow me A issue was reports on a Windows 2008R2 IIS server where the hosted site was going down repeatedly, Investigation revealed  IIS Application pool keeps crashing with the following event logged in event viewer. Log Name:      System
Source:        Microsoft-Windows-WAS Event ID:      5139
                           Task Category: None Level:         Warning
Keywords:      Classic
User:          N/A Description:
A listener channel for protocol ‘http’ in worker process ‘XXXX’ serving application pool ‘Name of AppPool’ reported a listener channel failure.  The data field contains the error number.   Upon further troubleshooting we found some corruption in IIS binaries, To validate that we executed SFC /ScanNow and checked the Cbs.log (%windir%\logs\cbs\cbs.log). The Log revealed the files which sfc /scannow wasn’t able to repair, we un-installed the updates relevant to those files and installed the latest hotfixes of those files. Rebooted the Server and found IIS working fine. Feel free to report new issue on our forum Follow...

Understanding 500 internal server error

Recently we migrated a clients website from an windows 2003 IIS6 with SQL 2005 backend server to a fresh new Windows 2008 R2 Server with IIS 7.5 with SQL 2008R2. The whole migration was a piece of cake, we handed over the migrated website and all was working well. One fine day we got a call back that a specific section of website where they create users gives them “500 Internal Server Error”.     Whats interesting about this error is that its just a fake message or rather in programming language terms its a Error handler.  Basically when there is error on your website, One would not like to show it to the world, Its one thing that it looks ugly however, the bigger reason is that a detailed error can expose alot about what you got running in background and may become a security threat for the website as well. However to fix the 500 Internal Server Error it is very important that we find the underlying cause of the error and to find that underlying cause, we need to go around this 500 Internal Server error and Expose the actual reason behind the Failure. Steps to Reveal the behind the curtain error of 500 Internal Server Error So when I faced this error my website was hosted on Windows Server 2008 R2 with IIS 7.5, so the steps and screen shots here are from the same versions. However, I am sure the same logic should remain applicable for a couple of versions before and after this. So lets get started. Step1 : Open IIS 7.5, expand...