InfoPath Forms Services solution cache churning - Event 5759 (SharePoint Server 2010)

  • Article

 

Applies to: SharePoint Server 2010 Enterprise

Alert Name:   InfoPath Forms Services solution cache churning

Event ID:   5759

Summary:   InfoPath Forms Services uses the ASP.NET cache to cache form templates when the form templates are first loaded on a front-end Web server. When the in-memory cache is full, the ASP page releases system memory and form templates are reloaded. This churning could indicate high memory pressure and performance that is less than optimal.

Symptoms:   One or more of the following symptoms might appear:

  • InfoPath forms take longer than usual to open in the Web browser.

  • This event appears in the event log: Event ID: 5759 Description: Form templates in the InfoPath Forms Services in-memory cache are being reloaded frequently. This could indicate high memory pressure and suboptimal performance.

Cause:   One or more of the following might be the cause:

  • Low-memory conditions exist or a form is consuming a large amount of memory.

  • Microsoft SQL Server is running on a front-end Web server.

Resolution:   Restart Internet Information Services

  • In a Command Prompt window, type iisreset /noforce <computername>.

Resolution:   Install product updates

  • Check Windows Update for updates and install the available product updates.

Resolution:   Check SQL Server installation

  • If you run SQL Server on a SharePoint Server front-end Web server — for example, in a single-server evaluation deployment — the ASP.NET cache releases system memory at a lower threshold than SQL Server, which could result in InfoPath Forms Services memory starvation.

  • To mitigate this issue, configure SQL Server memory limits manually when SQL Server is installed on the same computer as SharePoint Server 2010. For more information, see Server memory options(https://go.microsoft.com/fwlink/p/?LinkId=160542).

Resolution:   Upgrade hardware

  • If all previous resolutions do not result in improved form performance, the problem might be hardware-related. Verify that the current server has adequate memory. Upgrade the memory if necessary.