Error 2262 Sharepoint
Contents |
360 games PC games "note: 1: 2262 2: error 3: -2147287038" Windows games Windows phone games Entertainment All Entertainment event id 2262 iis-w3svc-wp deadlock detected Movies & TV Music Business & Education Business Students & educators event id 2262 isapi deadlock detected Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Aspnet_isapi.dll Deadlock Detected
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All asp unhealthy because 100 of executing requests Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
N/AComputer: XXXXXXXXXXXXXXXXXDescription:ISAPI 'C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.Checking the SQL server revealed over 30 deadlocks on one content database. Every site in the affected content a process serving application pool exceeded time limits during shut down database was inaccessable. The rest of the sites on other content databases were fine.While many different reasons could cause the Deadlock, such as third party applications running SQL queries on the content databases with the "No Lock", our problem seemed to be something else.Further investigation showed that the SQL Server was not configured optimally. The server is 64bit https://support.microsoft.com/en-us/kb/974165 SQL Server 2005 Enterprise. Things we checked and changed:Make sure that AutoGrow on the Content Databases are set to more than 500MB. As well as the Log files AutoGrow is set to 500MB. IF the log file size increases over 10GB in one day then set the initial size to 10GB.Max degree of Parallelism, check this blog: http://blogs.msdn.com/grahamk/archive/2009/06/15/troubleshooting-sql-server-deadlocks-and-performance-when-running-sharepoint.aspxWe set http://wssmossstuff.blogspot.com/2009/09/deadlock-detected-event-2262.html our servers Max Degree of Parallelism to 1.Our server has 16GB Ram. SQL Max memory was set to 14GB, which left 2 GB for the OS and other applications. The number of worker threads in a 64bit environment is 576. Each worker thread requires 2MB of RAM. That equals 1GB of RAM just for the worker threads. AS I understand, if there is not enough memory available for the worker threads, then memory contention occurs.This could create deadlocks, as some of the worker threads are waiting for the other worker threads to complete.So, leave 2GB for the OS, 2GB for the worker threads, and at 2 GB for other Applications. So means you set the maximum memory for SQL to 10GB on a 16GB box in a 64bit environment.All these changes definately increased our server performance. Posted by Daniel van der Gryp at 9:42 AM No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search Custom Search Visitor Locations About Me Daniel van der Gryp View my co
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/2390934/asp-net-web-app-deadlocking-think-its-caused-by-sql-server-locking of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: deadlock detected Sign up ASP.NET web app deadlocking - think it's caused by SQL Server locking up vote 6 down vote favorite 1 Our client's web app restarts suddenly at random intervals. For each restart, we've found an entry like this in the Windows Event Log: Event Type: Warning Event Source: W3SVC-WP Event Category: None Event ID: 2262 Date: 2/21/2010 Time: 1:33:52 PM User: event id 2262 N/A Computer: LIQUID-NXCFZ9DJ Description: ISAPI 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'. This has happened 10 times in 3 weeks, several of those being 2 or 3 times in several hours, and also going over a week without it happening. In the crash dump that we have maybe 70-80 client connections, like so: GET request for