As defined in Internet Information Services (IIS) an application Pool is a collection of one or more URLs that are serviced by one or a set of worker processes. After installation of SharePoint, open IIS Manager. You will notice application pools in iis.
You must select an existing Application Pool or create a new pool whenever you create a service or web application in SharePoint Server.
application pools in iis allow multiple SharePoint websites to run on a single server without the processes or code in one site interacting with any other sites. This is primarily a security benefit, since any outside intrusion on one site is isolated. Also, problematic or poor code running on one site is isolated so that other sites on the server are unaffected. For these reasons, you should plan to use dedicated application pools to isolate authenticated content and separate applications that contain password information.
we can run powershell command to get all application pools.
Advertisements
Advertisements
Get-IISAppPool
we can search one or more application pool directly by running the below command.
403 forbidden error fix done. Received below error while browsing SharePoint web app.
The website declined to show this webpage
HTTP 403
Most likely causes:
This website requires you to log in
if we create a copy of the web.config file, rename the web.config file, refresh the home page, we receive an “HTTP 404 – Page Not Found” error.
Rename the web.config file back and refresh the page. The site is browse able for a while before failing after some time, We see the following error in Failed Request Tracing.
A procmon trace captured while accessing the web app from the server showed the following:
This issue usually occurs when a request from an authenticated user without local admin rights results in a failed read of the /BIN directory by the impersonating w3wp.exe (IIS worker process for ASP.NET) process.This behavior is typically associated with lack of permissions to the temporary folder /BIN where ASP.Net assemblies are Just In Time (JIT) compiled.
Resolution
The solution is to ensure that the Authenticated Users or \Users group (which usually contains DOMAIN\Users group) has Read & Execute, List Folder Contents and Read permissions on the /BIN folder below
Follow the steps below to grant the required permissions:
Open Windows Explorer and navigate to the /bin directory of your web application
Right-click on the folder and click on Properties
Go to Security tab and click on Edit
Click on Add and add the local server group Authenticated Users or \Users (this usually contains DOMAIN\Users group).
Select the Read & Execute, List Folder Contents and Read permissions (if you are planning to add Everyone to the /bin folder, grant Read permissions only)
Click OK to apply the new settings
Refresh the page and we should be able to browse to the site.
More Information
If an administrator accesses the site/feature that caused the error, the subsequent requests from non-administrators would succeed. This behavior is typically associated with lack of permissions to the temporary folder where ASP.Net assemblies are Just In Time compiled.
The freb trace shows a 403.0 for ManagedPipelineHandler
It seems to go through quite a few ASPNet events – but happens during the ASPNetPageRender – it goes to the ASPNetPageRender Enter, then ASPNetHTTPHandler Leave.Only then does it get a 403.0 which is not an official RFC error. The first sub-status for 403 is 403.0.
Application pool in Classic or Integrated mode
Application Pool in Classic Mode – In this case, we can configure a Wildcard mapping for ASPNET_ISAPI.dll at the website level. That would propagate to child virtual directories. That should not need any further modifications at the virtual directory level.
Application Pool in Integrated Mode – In this case, all relevant virtual directories would need individual modifications. They need to be set for specific handler.
Name: SharePoint Administration Service Name: SPAdminV4 Description: Performs administrative tasks for SharePoint Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BINWSSADMIN.EXE
Name: SharePoint Insights Service Name: SPInsights Description: Microsoft SharePoint Insights is a hybrid solution that helps SharePoint administrators manage their infrastructure more efficiently. After it is configured properly, it will upload data to Microsoft and give administrators access to different reports in Office 365. Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BINOfficeDataLoaderMicrosoft.Office.BigData.DataLoader.exe  Name: SharePoint Search Host Controller Service Name: SPSearchHostController Description: Performs host deployment and management for SharePoint search components. Path to Executable: C:Program FilesMicrosoft Office Servers16.0SearchHostControllerhostcontrollerservice.exe
Name: SharePoint Server Search 16 Service Name: OSearch16 Description: Administers and crawls content from repositories. Path to Executable: C:Program FilesMicrosoft Office Servers16.0Binmssearch.exe
Name: SharePoint Timer Service Service Name: SPTimerV4 Description: Sends notifications and performs scheduled tasks for SharePoint Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BINOWSTIMER.EXE
Name: SharePoint Tracing Service Service Name: SPTraceV4 Description: Manages trace output Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BINwsstracing.exe
Name: SharePoint User Code Host Service Name: SPUserCodeV4 Description: Executes user code in a sandbox Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16UserCodeSPUCHostService.exe  Name: SharePoint VSS Writer Service Name: SPWriterV4 Description: SharePoint VSS Writer Path to Executable: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions16BINSPWRITER.EXE
 Name: Microsoft Project Server Calculation Service 2016 Service Name: ProjectCalcService16 Description: Microsoft Project Server Calculation Service manages the lifecycle and the communication of the processes that handle modifications to projects. Path to Executable: C:Program FilesMicrosoft Office Servers16.0BinMicrosoft.Office.Project.Server.Calculation.exe  Name: Microsoft Project Server Events Service 2016 Service Name: ProjectEventService16 Description: Microsoft Project Server Events Service executes events triggered by changes to entities on the ProjectServer. Path to Executable: C:Program FilesMicrosoft Office Servers16.0BinMicrosoft.Office.Project.Server.Eventing.exe  Name: Microsoft Project Server Queue Service 2016 Service Name: ProjectQueueService16 Description: Microsoft Project Server Queue Service executes project related jobs asynchronously. Example queue jobs: Save project, publish project, submit timesheet. Path to Executable: C:Program FilesMicrosoft Office Servers16.0BinMicrosoft.Office.Project.Server.Queuing.exe
Site not appear in IIS Manager error opening in SharePoint Designer
I have created a site collection and then create two team sites on SharePoint server. Sites are working fine from central Admin but Site not appear in IIS Manager. Also when I try to edit a SharePoint site on SharePoint designer 2010 following error comes.
Unable to open website following causes:
The web server may not have SharePoint installed.
The web server may be temporarily out of service.
If you are connecting through a proxy server the proxy settings may be incorrect.
An error may be occurred in the web server
The IIS manager only showing the following sites SharePoint 80 and SharePoint central admin
When I try to create a site on SharePoint designer following error comes:
The web site must be created on a server that is running Microsoft SharePoint foundation server please choose another location.
I have installed SharePoint server 2010, SharePoint foundation server 2010 and SharePoint designer on my pc.
Solution :
* In IIS Manager, you're only going to see the Web apps, the site collections and sites are wont show up(if you have another web app that isn't showing up, that's a bigger issue. I'd delete it and try to recreate it.
* The SharePoint Designer issue, I've had before. For me, the issue was a firewall setting. But basically if you can get to the pages with the browser, make sure you have correct permissions set for your login, etc.
