Skip to main content

Posts

Showing posts with the label Error

Make sure "AjaxControlToolkit.Properties.Resources.NET4.resources" was correctly embedded or linked

Error Message Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "AjaxControlToolkit.Properties.Resources.NET4.resources" was correctly embedded or linked into assembly "AjaxControlToolkit" at compile time, or that all the satellite assemblies required are loadable and fully signed. Reason AjaxControlToolkit’s control load reference refers to the base System.Web.UI.Control method which is present as a part of the ASP.NET AJAX Libraries and those libraries are referenced only when the ScriptManager is referenced in the page. Solution Add ScriptManager in the page

ContextSwitchDeadlock was detected

I got following error while trying to retrieve data from a SQL table into a datagridview. Table contains 1000s of data and while retrieving I have to process some data also. ContextSwitchDeadlock was detected Message: The CLR has been unable to transition from COM context 0x159bc0 to COM context 0x1598e0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations. After goggling for about 1 hour I came up with a solution which makes the deadlock detection disable.   Step 1 obtain ...

Timeout Detection and Recovery of GPUs through WDDM

One of the most common stability problems in graphics is when the system appears completely "frozen" or "hung" while processing an end-user command or operation. We generally wait a few seconds and then reboot the system by pressing the Power button. Usually the graphics processing unit (GPU) is "busy" processing intensive graphical operations, typically during gameplay. This results in nothing being updated on the screen, thus appearing to the user that the system is frozen.