Error publishing Nintex Workflow on Workspaces list

Error publishing Nintex Workflow on Workspaces list


Problem:

You get the following error when publishing a Nintex workflow:


'soap:Server Server was unable to process request. ---> System accounts can't create a Workspaces.'  


​

Solution: 

1. Go to the settings of the Collaboration Manager and set the Workspace Creation to 'Workspace created by custom Workflow or web service'.


 

2. Publish your workflow.

3. Set the settings in the Collaboration Manager to automatically create Workspaces.




    • Related Articles

    • Error occured in Workspace generation with Nintex Workflow

      Problem: When you create a workspace with Nintex Workflow status runs on "error occured". Reason: The error in the list can be caused by the "Workflow Tasks". The Collaboration Manager detects "two" lists because of the space character. Solution: ...

    • Nintex Workflow 401 Unauthorized

      Symptom You're accessing Collaboration Manager Web Service through Nintex workflow engine. Action fails with error "Request failed with status: Unauthorized" when creating a Site Collection using CreateWorkspaceFromTemplate.  Cause This could be ...

    • Nintex Workflow 500 Internal Server Error

      Symptom You're accessing Collaboration Manager Web Service through Nintex workflow engine. Action fails with error "The remote server returned an error: (500) Internal Server Error." when creating a Site Collection using CreateWorkspaceFromTemplate.  ...

    • Nintex Workflow runs into Timeout

      Symptom You're accessing Collaboration Manager Web Service through Nintex workflow engine. Action fails with error "Timeout" when creating a Site Collection using CreateWorkspaceFromTemplate.  Cause - The Site Collection doesn't get created within ...

    • Create a workspace through workflow results in Internal Server error 500

      Symptoms You receive "The remote server returned an error: (500) Internal Server Error." in the workflow enginge like Nintex or in ULS. Furthermore you're receiving errors in ULS log at the time you get the Internal Server Error: 03.03.2016 ...