Microsoft SharePoint Foundation Web Application Service - To Run or Not Run

Scenario: Running Deployment Scripts that are publishing WSPs into a multi-server farm (2 front-ends, 1 App Server)

Microsoft SharePoint Foundation Web Application Service running in their environment (where the Foundation Web Application is running) is making the deployment go fine, where as the same in our environment is not running, so the script is failing.

Generally, if you run this service in a server, that makes that server as WFE (Web Front End) so, people prefer to have this stopped in App Servers. But there is a dependency on this with the “Microsoft SharePoint Foundation Workflow Timer Service” and since this is running as well in the App Server, the script is trying to deploy the solution in the App Server as well and since the Web Application Service is not running, the script is unable to deploy and throws errors.

Now you have 2 options:

1.       To stop the “Microsoft SharePoint Foundation Workflow Timer Service” and re-run the script and try how it works
2.       Second, to turn on the Web Application Service  on the App Server as well. Though it is not required or generally people don’t do it as a best practice, by leaving it on, it is not taking up any resources or it is not going to make the environment slow. The reason is – users always are hitting the WFEs only and thus the Foundation Web Application Service in the WFEs only invoke the IIS Web Sites, Load up the App Pools and start consuming memory
3.       Since direct requests are not going to come to the App Server, the Foundation Web Application Service running in the App Server will never have any job to do: so the memory over here will not be used



Comments

  1. jadeDecember 21, 2016 at 3:08 AM

    Interesting topic for a blog. I have been searching the Internet for fun and came upon your website. Fabulous post. Thanks a ton for sharing your knowledge! It is great to see that some people still put in an effort into managing their websites. I'll be sure to check back again real soon. SharePoint Intranet

    ReplyDelete
  2. LianMarch 26, 2021 at 11:43 AM

    Actually I had problems with nintex workflow last 3 weeks and till now not fixed

    Our sharepoint 2016 environment running 2 applications server and 2 WFE servers,
    SharePoint Foundation Web Application are currently running only on applications server also SharePoint Foundation workflow Timer
    Both are running on applications server,


    Scenario is im designed nintex workflow and publish it into WFE, and once I start to tested it goes to ((Failed to run)),

    After reading your article now im pretty sure why this happened, because nintex depend on these two services web application service and workflow timer service.
    And they are running on applications server , and I was created my workflow on WFE

    So pls your help on this....

    ReplyDelete

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp...
Read more

Validate a SharePoint Date Field against Current Date in Javascript

Consider the following scenario: You have a SharePoint Site which has its regional settings set to English (UK) - so that the date format becomes dd/mm/yyyy in all date pickers You would like to validate a particular date field in your List or Document Library against the current date If the validation does not pass, you should not allow the form to save So what the script does is: Uses the sputility (check my previous posts and also look at http://sputility.codeplex.com) to get the particular SharePoint date field It comes out as a date datatype, so I cast it to string Since the format is in dd/mm/yyyy and Javascript compare and date functions work only with mm/dd/yyyy, I am converting them back to that format then using UTC string conversions and comparing... Enjoy! <script type="text/javascript"> function PreSaveAction() {  var createdate = SPUtility.GetSPField('Date of Creation').GetValue();  var createdatestr=createdate.toString();      ...
Read more