Recycling of application pools when memory limits are exceeded.

Recycling of application pools when memory limits are exceeded.

Summary:  Application pools recycle because memory limits have been enabled and exceeded. Recycling based on memory limits is not usually necessary in a 64-bit environment, and therefore recycling should not be enabled. Unnecessary recycling can result in dropped requests from the recycled worker process and slow performance for end users who are making requests to the new worker process.

Cause: Application pools are configured to recycle when memory limits are exceeded. 

Resolution: Change the application pool recycling settings in Internet Information Services (IIS).

1.    Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

2.    Identify the server on which this event occurs. On the Central Administration Web site, in the Monitoring section, click Review problems and solutions, and then find the name of the server in the Failing Servers column. If there are multiple failing servers in a server farm, you must repeat the following steps on each failing server.

3.    Verify that the user account that is performing the following steps is a member of the Administrators group on the local computer that you identified in the previous step.

4.    Log on to the server on which this event occurs.

5.    Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

6.    In the Internet Information Services management console, in the Connections pane, expand the tree view, and then click Application Pools.

7.    In the Application Pools list, right-click the application pool on which you want to disable the memory limits, and then click Recycling.

8.    In the Edit Application Pool Recycling Settings dialog box, in the Memory Based Maximums section, clear the Virtual memory usage (in KB) and Private memory usage (in KB) check boxes, and then click Next.

                         

9.    In the Recycling Events to Log dialog box, click Finish.

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

SPRequest allocation call stack logging in SharePoint

Sp Requestallocation call stack logging in SharePoint

SPRequest call stack logging gives more detailed and useful information to allow to diagnose the problem. It provides information about memory leaks, issues in code part which are not captured in the ULS logs, event viewer. There is no Impact of enabling the cal stack because it’s not going to reset or restart any service. The only thing is, The size of the Log will be more.

Just copy the following code into a file with the extension .ps1 

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") > $null
$contentSvc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$contentSvc.CollectSPRequestAllocationCallStacks = $true
$contentSvc.Update() 

To disable SPRequest allcoation callstack logging after you completed testing just replace $true with $false:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") > $null
$contentSvc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$contentSvc.CollectSPRequestAllocationCallStacks = $false
$contentSvc.Update() 

To start the power shell scripts please open the SharePoint 2010 Management Shell, switch to the directory where you stored the ps1 files and start them using the following syntax:

PS> .\EnableSPRequestCallstacks.ps1

  

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Turn on the verbose log in SharePoint 2013

Turn on the verbose log in SharePoint 2013

To  Turn on the verbose log in SharePoint 2013 run the below command in SharePoint management shell.

Set-SPLogLevel -TraceSeverity verbose

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Configure the maximum number of co-authoring authors in SharePoint 2013

Configure the maximum number of co-authoring authors in SharePoint 2013

Description: The CoauthoringMaxAuthors property lets you specify the maximum number of users who can co-author a Word document or PowerPoint presentation at the same time in SharePoint 2013. This article describes how to configure the CoauthoringMaxAuthors property by using Windows Power Shell.

Check the ink below from MS.

  http://technet.microsoft.com/en-us/library/ff718248%28v=office.15%29.aspx

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.