Skip to main content
Search Again

We think these articles could help you:

    See More
    Nintex Knowledge Base

    Error "Nintex soap:ServerServer was unable to process request ... Nintex Workflow 2013 is not activated for this Web Application"

    Status: Validated

    ISSUE
    When publishing a workflow, the following error occurs, even though Nintex Workflow has already been activated on this web application:

    Nintex soap:ServerServer was unable to process request Failed to publish workflow: It appears that Nintex Workflow 2013 is not activated for this Web Application.
    ERROR CODE
    01/01/2016 08:54:25.27 w3wp.exe (Service1:0x39A8) 0x6D98 Nintex Workflow 2013 Web Service 00000 Unexpected Error saving from workflow export file.: Nintex.Workflow.NWSavingWorkflowException: Failed to publish workflow: It appears that Nintex Workflow 2013 is not activated for this Web Application. Check your settings in Central Administration. at Nintex.Workflow.Publishing.Publish.TiE=(String TyE=, String UCE=) at Nintex.Workflow.Publishing.Publish....
    RESOLUTION
    1. Identify the server or servers where this error occurs, by extracting the merged Sharepoint ULS logs:
      1. On a web front-end or application server, run the following Sharepoint Powershell command, replacing the <String> with the file path and filename of the log file to be created, and the <DateTime> of 5mins before and after the workflow failing to publish:
        Merge-SPLogFile -Path <String> [-StartTime <DateTime>][-EndTime <DateTime>]
      2. Examine the ULS log files and look for an error similar to the following:
        01/01/2016
        08:54:25.27
        w3wp.exe (Service1:0x39A8)
        0x6D98
        Nintex Workflow 2013 Web Service 00000
        Unexpected Error saving from workflow export file.: Nintex.Workflow.NWSavingWorkflowException: Failed to publish workflow: It appears that Nintex Workflow 2013 is not activated for this Web Application....
      3. On the 3rd line, next to the w3wp.exe process is the server name,
    2. On the server identified above, navigate to the following location, where <web app> is the web application where this issue is occurring, and open the web.config file: C:\inetpub\wwwroot\wss\VirtualDirectories\<web app>
    3. Open the web.config file and confirm if the following declaration is present:
      <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" />
    4. If these are missing from the web.config file:
      1. Create a backup of the web.config file.
      2. Within the original web.config file, add the above two missing declarations within the following tags:
        <authorizedTypes>
              <targetFx version="v4.0">
        
        ................
        
              </targetFx>
            </authorizedTypes>
    5. Perform an IISreset.

    If the issue isn't resolved or if the changes to the web.config file have caused unexpected issues, restore the web.config from backup and perform an IISreset to load the original web.config.
    ADDITIONAL INFORMATION
    RELATED LINKS
    • Was this article helpful?