When you try to change the application pool identity to another domain account or reset the password for that account. You type in the username and password and hit OK and you will get the following error message
There was an error while performing this operation.
Details: Bad Data. (Exception from HRESULT: 0x80090005)
Usually this is caused by Xcopy the applicationHost.config from one server to another. And on original server you changed the application pool identity to a custom identity. (Advanced Settings > Application Pool Identity > Custom Account).
Users might get “This page can’t be displayed” error in IE7 or IE8 when a website requires too many redirections to go to the destination page. The question is how much redirection will be considered as “too many”.
IE7 and IE8 sets the default value of redirection limit as 10, so if a webpage causes more than 10 continuous redirection, “Page can’t be displayed” error will be displayed.
This limit can be changed by adding the following registry key,
However, from IE9 IE has increase this value by multiplying a coefficient (11). Since the default value of MaxHttpRedirects is kept as 10, the redirection limit will be 10*11 = 110 since IE9.
If you chance the registry to 20, then the redirection limit will be 20 * 11 = 220.
OS: Windows 8.1
IDE: Visual Studio 2013
Uncovering and correcting memory issues in managed applications can be difficult. Memory issues manifest themselves in different ways. For example, you may observe your application's memory usage growing unboundedly, eventually resulting in an Out Of Memory (OOM) exception. (Your application may even throw out-of-memory exceptions when there is plenty of physical memory available.) But any one of the following may indicate a possible memory issue:<!--more-->
This topic contains the following sections:
[00:00] - What is a Garbage Collector (GC)?
[02:40] - How has the GC changed?
[06:02] - Memory issues
[08:57] - Stress Log (!sos.dumplog)
[10:08] - Troubleshooting and Performance
[12:20] - Demo App
[14:20] - !sos.eeheap -gc
[18:08] - !sos.dumpheap -stat
[20:38] - !sos.dumpheap -mt
[21:58] - !sos.dumpobj / !sos.do (Dump Object)
[24:15] - Performance Monitoring (SOS, PerfView, Performance Monitor)
[28:06] - Measure immediately after an action, not at a cadence
[29:45] - x clr!WKS::GCHeap::GcCondemnedGeneration (Current GC being collected)
[31:15] - bp clr!WKS::GCHeap::RestartEE (Break after a GC)
[35:30] - More next week...
[03:30] - How to approach Performance Analysis
[09:00] - Cadence of Gen 0, 1 and 2 garbage collection
[12:20] - !sos.FindRoots
[14:00] - Stop at Gen 1 GC - !sos.FindRoots -gen 1
[16:09] - End of GC: clr!WKS::GCHeap::RestartEE
[17:10] - Stacks of allocations [CLRProfiler] [PerfView]
[18:39] - Object's Generation - !sos.gcwhere
[19:28] - Generation Segments - !sos.eeheap -gc
[24:52] - VM Hoarding
[28:24] - Heap Summary - !sos.heapstat
[00:45] - Internal and Externals Roots
[05:55] - Start of GC: clr!WKS::GCHeap::GarbageCollectGeneration
[07:00] - !sos.dumpheap
[07:30] - !sos.gcroot
[09:45] - New Root Types? Dependent Handles (ConditionalWeakTable)
[12:32] - Handle Types
[13:30] - Pinned Handles - Effect on Fragmentation
[15:40] - Large Object Heap's Fragmentation & Coalescence
[17:55] - Pinned Objects
[19:33] - !sos.gchandles
[20:06] - !sos.gchandles -type Pinned
[20:45] - !sos.gchandles -type AsyncPinned
[00:38] - PerfView overview
[02:52] - (Basic) Collection
[04:39] - GCStats
[10:10] - GC Rollup By Generation
[11:22] - GC Events By Time (>200ms)
[11:31] - LOH Allocation (>200ms)
[12:34] - Gen2
[12:48] - GC Events By Time
[28:40] - Best Approach to Performance Analysis
[31:03] - GC Collect Only
[32:10] - Channel 9 - PerfView Tutorial