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.

Object not found when running the command “set-spserviceapplicationpool” for web application

Object not found when running the command “set-spserviceapplicationpool” for web application

 

Issue: Object not found error when running the command set-spserviceapplicationpool for web application

Cause: using the Set-SPServiceApplicationPool command we cannot change the application pool identity of a web application. The command only works to change the application pool identity for the service application in SharePoint.

Resolution: Follow the below power shell to change the identity of the Web Application pool

$WebApplicaiton = Get-SPWebApplication https://webapp:port
$ManagedAccount = Get-SPManagedAccount -Identity "domain\username"
$WebApplication.ApplicationPool.ManagedAccount = $ManagedAccount
$WebApplicaiton.ApplicationPool.Update();
$WebApplication.Update() 

  

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.

Server error in ‘/’ Application0x80131904

Server error in ‘/’ Application

<nativehr>0x80131904</nativehr><nativestack></nativestack>

 

Description: an unhandled exception occurred during the execution of the current web request

Exception details: system.runtime.interopservices.comexception: <nativehr>0x80131904</nativehr><nativestack></nativestack>

Details: When I opened the Sharepoint central administration page I welcome with the below error.

Cause: there could be many reasons for the issue. I am providing the solutions specifically related to the error shows above.

Solution: Please check the below to resolve the issue.

1.   Ensure that the password for the Application pool “SharePoint Central Administration v4” in IIS is set correct.

2.   Ensure to have a enough space on the C:\ drive

3.   Ensure that the password updated correctly in the services of SharePoint 2010 Administration and SharePoint 2010 timer in the services.msc.

 

 

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.