AnsweredAssumed Answered

Unable to create workflow start form with Nintex Forms after update

Question asked by tobale on Mar 15, 2016
Latest reply on Jun 17, 2016 by nguyenhuynhan

Hi,

 

we updated Nintex Workflow (3.1.6.0 to 3.1.7.10) and Nintex Forms (2.6.0.0 to 2.9.0.0) some days ago in our dev environment. During testing, we found that we're unable to create workflow start forms or open/edit previously created start forms with Nintex Forms.

 

Scenario:

  1. Create new or edit existing Nintex Workflow
  2. Go to Workflow Settings
  3. Choose Edit Start Form > Edit with Nintex Forms

 

The Nintex Forms Designer does not open. The "Please wait..." dialog is shown < 1 sec. and disappears without further information or error message.

 

It seems to have something to do with authentication. Within Verbose ULS, we can see the following entries after hitting "Edit with Nintex Forms":

  • SPApplicationAuthenticationModule: There is no Authorization header, can't try to perform application authentication.
  • Claims Windows Sign-In: Sending 401 for request [SPSiteURL]/_layouts/15/NintexWorkflow/_vti_bin/NintexWorkflow/Workflow.asmx' because the user is not authenticated and resource requires authentication.
  • SPFederationAuthenticationModule.IsRedirectToLogOnPage: This is a 302 redirect to /_login/default.aspx?ReturnUrl=%[URL]%2f_layouts%2f15%2fNintexWorkflow%2f_vti_bin%2fNintexWorkflow%2fWorkflow.asmx
  • SPFederationAuthenticationModule.IsRedirectToLogOnPage: Redirect to known signin page: /_login/default.aspx?ReturnUrl=%[URL]%2f_layouts%2f15%2fNintexWorkflow%2f_vti_bin%2fNintexWorkflow%2fWorkflow.asmx
  • SPFederationAuthenticationModule.OnEndRequest: User was being redirected to authenticate.
  • Claims Windows Sign-In: Sending 401 for request [SPSiteURL]/_layouts/15/NintexWorkflow/_vti_bin/NintexWorkflow/Workflow.asmx' because the user is not authenticated and resource requires authentication.
  • Server challenged request: 'The remote server returned an error: (401) Unauthorized.'

 

Workaround by hand:

  1. Deactivate "Nintex Forms for Nintex Workflow" feature on the problematic site collection
  2. Activate "Nintex Forms for Nintex Workflow" feature on the problematic site collection
  3. The editor comes up again

However, this does not work if we do this using PowerShell like:

  1. $Feature = "ac8addc7-7252-4136-8dcb-9887a277ae2c"
  2. Disable-SPFeature -Identity $Feature -Url $Site.Url
  3. Enable-SPFeature -Identity $Feature -Url $Site.Url

 

Can you help us with this?

 

Regards,

Tobi

Outcomes