We get a lot of deadlock errors on our SharePoint Web applications (similar to this description). These errors result in timeouts, disappearing when the user refresh the browser.    The happens during the first connection to the environment each day. Afte

Document created by nintexsupport Support on Dec 24, 2015
Version 1Show Document
  • View in full screen mode

 

Summary:

We get a lot of deadlock errors on our SharePoint Web applications (similar to this description). These errors result in timeouts, disappearing when the user refresh the browser.    The happens during the first connection to the environment each day. After clearing the full browser cache, sometimes the error occurs again. This error also happens to our other web applications which NW2007 is not deployed to.     We uninstalled NW2007 from our Test-environment to see if it really is NW2007 which is causing the timeouts. After uninstalling, the errors did not occur anymore.

Product:

All Workflow for SharePoint on-premises

Answer/Solution:

Do the web servers have access to the Internet?    Nintex .dll's are signed with a code signing certificate (similar to SSL) to ensure they are authentic. When .NET first loads these it tries to contact the certificate provider to ensure the Nintex certificate has not been revoked.  Are you able to allow your servers access to: crl.microsoft.com and thawte.com’s crl service?    As an alternative you can stop .NET doing this check by editing the web.config file for the web application and adding:        to the runtime section.    The symptoms are mentioned in the following kb article: http://support.microsoft.com/default.aspx/kb/936707.

Attachments

    Outcomes