FIX: Windows Edge Browser error “Hmm, we can’t reach this page.” for web pages

Scenario: All of sudden, Windows Edge browser starts resulting in error “Hmm, we can’t reach this page.” whenever you browse any web pages.  However, you will be able to access the internet through other browsers on the same system. Cause: The Windows Edge browser depends on DNS resolution which is provided by “DNS Client” service.  Edge browser fails to load page when “DNS Client” service is disabled on the system. Solution: Enable and start the “DNS Client” service on the system.

Read more

Automating IIS Web tasks using AppCmd command

Requirement: You need to automate the management like create, start, stop, etc., of IIS Resources including Web Site, App, AppPool, etc. Solution: Microsoft provides a command line tool named Appcmd.exe which ships/installs along with IIS.  It’s usually located at C:\WINDOWS\system32\inetsrv\appcmd.exe path. Automation Examples: Create an APPPOOL, with specified name, .Net Framework version, Managed pipeline mode, etc., C:\>C:\WINDOWS\system32\inetsrv\appcmd.exe ADD APPPOOL /name:TestAppPool /managedRuntimeVersion:v4.0 /managedPipelineMode:”Integrated” APPPOOL object “TestAppPool” added C:\> Stop an APPPOOL PS C:\> C:\WINDOWS\system32\inetsrv\appcmd.exe STOP APPPOOL TestAppPool “TestAppPool” successfully stopped PS C:\> Start an APPPOOL PS C:\> C:\WINDOWS\system32\inetsrv\appcmd.exe START APPPOOL TestAppPool “TestAppPool” successfully started. PS C:\> Create a web Application under […]

Read more