Skip to main content
SharePoint

Return to Answer

added 4 characters in body
Source Link
SPDoctor
SPDoctor
  • 9.6k
  • 2
  • 35
  • 60

I think there is a misconception here that there is something called SharePoint "running" and responding to requests. What you have running is IIS which is handling incoming requests. SharePoint handlers are installed in the ASP.NET pipeline to process the requests but it is the w3wp IIS worker process that is receivinglistening for them.

While that is the answer to your question, I am afraid I don't think it helps you solve the problem you described.

I think there is a misconception here that there is something called SharePoint "running" and responding to requests. What you have running is IIS which is handling incoming requests. SharePoint handlers are installed in the ASP.NET pipeline to process the requests but it is the w3wp IIS worker process that is receiving them.

While that is the answer to your question, I am afraid I don't think it helps you solve the problem you described.

I think there is a misconception here that there is something called SharePoint "running" and responding to requests. What you have running is IIS which is handling incoming requests. SharePoint handlers are installed in the ASP.NET pipeline to process the requests but it is the w3wp IIS worker process that is listening for them.

While that is the answer to your question, I am afraid I don't think it helps you solve the problem you described.

Source Link
SPDoctor
SPDoctor
  • 9.6k
  • 2
  • 35
  • 60

I think there is a misconception here that there is something called SharePoint "running" and responding to requests. What you have running is IIS which is handling incoming requests. SharePoint handlers are installed in the ASP.NET pipeline to process the requests but it is the w3wp IIS worker process that is receiving them.

While that is the answer to your question, I am afraid I don't think it helps you solve the problem you described.