Skip to main content

Hi All,

We seem to regularly get issues with various elements of SharePoint after "Patch Tuesday". We aren't involved on the server side of things here, but it seems to be a regular occurence that after a patch is installed on the servers, the app pools need recycling and the Nintex features need to be deactivated and re-activated at web app level.

This month we found that none of our Nintex forms would load in a certain web app and that we received errors in Infopath forms we had. An app pool recycle resolved the Infopath issue but we had to re-enable the features to get Nintex working again.

Does anyone else regularly experience this and if so, how do you go about dealing with this? I'd like our server team to be more proactive about this and could do with as much information on this to push it on them.

Thanks

When changes are made to the Nintex settings in CA, or after Nintex updates are applied, it is required that an IISReset be applied. It is not normal to have to reactivate the features (during a Nintex update or even a SharePoint update).

But after SharePoint or windows patches are applied, the standard running of the SharePoint 2013 Products Configuration Wizard is required which will also do an IISRESET. There should be no further steps to Nintex to get it running again after a windows or SharePoint patch. If you have to reactivate the feature each time, then there may be a step missed during the MS patches.

Even though Microsoft made available to WSUS the SharePoint CU's and security fixes, Microsoft states that IT is obliged to test these CUs before adding them to a production environment. In the SharePoint community, it is widely accepted that CU's only be applied if they resolve an issue you have, or at least wait at least a month and test the CU before installation. It would be a Governance issue to automatically apply SharePoint updates, especially since post deployment there are required steps to run or your farm will have issues.

You can check on your patch status in the farm by going to Central Admin, Manage servers in this farm, and view the Status field on each server. If any say anything buth "No Action Required", it needs to be investigated. It should also list the servers patch level and should match all others.

Some very good information from Stefan Gossner and Todd Klindt Microsoft Now Pushing SharePoint Server Updates via the Windows Update Service -- Redmondmag.com


Reply