cancel
Showing results for 
Search instead for 
Did you mean: 
Workflow Hero

Web.config not updating correctly on upgrade or install, Web.config not updating correctly on upgrade or install

We've had issues on past upgrades and recent installations from scratch where items are missing from web.config - are there any known issues on this or pre-reqs for ensuring that the web.config files are properly updated?

Aaron has posted fixes for this (unfortunately this isn't fixing the issue I've currently got on missing safecontrol entries), but I've not seen anything about root causes.

0 Kudos
Reply
4 Replies
Not applicable

Re: Web.config not updating correctly on upgrade or install, Web.config not updating correctly on upgrade or install

Hi Stuart,  Normally the Web.config file could be locked for some reason by the Web App during installation. Have you tried Web App activation under the Nintex workflow management in Central Admin? that should also update the Web.config with the safe control. check if there are no other process is locking the Web.config file. Thanks

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Web.config not updating correctly on upgrade or install, Web.config not updating correctly on upgrade or install

Yep, that was one of the first things we did, the standard route of web app activate, then disable and enable through the various levels of site/site collection features.

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Web.config not updating correctly on upgrade or install, Web.config not updating correctly on upgrade or install

Forgot to mention that it would be nice if this locking were flagged, or flagged more obviously if it's already in the copious messages shown during the installer's progress. I'm worried now that various things will be missed as we update

0 Kudos
Accept as Solution Reply
Not applicable

Re: Web.config not updating correctly on upgrade or install, Web.config not updating correctly on upgrade or install

Stuart,

Thanks for your question.

Our product updates the web.config files on servers using the SPWebConfigModification class of the Microsoft.SharePoint.Administration namespace, which allows you to dynamically register entities. These modifications are persisted in the configuration database where they function as a kind of virtual web.config that effectively serves as the final layer of the .config file stack for the SharePoint Foundation web application. The changes become effective when the SPWebService.ApplyWebConfigModifications method is called.

The web application activation piece for Nintex Workflow and Nintex Forms adds the following entries to the web.config using this method:

<SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebControls" TypeName="*" Safe="True" SafeAgainstScript="False" />

      <SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebParts.InitiateWorkflow" TypeName="*" Safe="True" SafeAgainstScript="False" />

      <SafeControl Assembly="Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" Namespace="Nintex.Forms.SharePoint.WebParts.NFListFormWebpart" TypeName="*" Safe="True" SafeAgainstScript="False" />

     

<add expressionPrefix="NFResources" type="Nintex.Forms.SharePoint.NFResourceExpressionBuilder, Nintex.Forms.SharePoint, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c52d764dcf7ec883" />

      

    <authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WorkflowActions" TypeName="HTLookupActivity" Authorized="True" />

        <authorizedType Assembly="mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.Generic" TypeName="List`1" Authorized="True" />

        <authorizedType Assembly="mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.Collections.Generic" TypeName="List`1" Authorized="True" />

        <authorizedType Assembly="Nintex.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.*" TypeName="*" Authorized="True" />

        <authorizedType Assembly="Nintex.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow" TypeName="RunNowParameterOptions" Authorized="True" />

In addition, following web.config safe control entries are added during solution deployment of Nintex Workflow:

  <SafeControl Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TypeName="*" Safe="True" />

      <SafeControl Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls.WebParts" TypeName="*" Safe="True" />

In conclusion, the updating on the web.config is actually controlled by the SharePoint farm and Nintex simply uses in place methods to ensure this process works without causing any unsupported updates to the web.config file.

If you are seeing web.config entries not being added to a single server then I would recommend reviewing any issues with that web.config file or the server in question.

Cheers,

Andrew Beals

0 Kudos
Accept as Solution Reply