cancel
Showing results for 
Search instead for 
Did you mean: 

Error: "The type or namespace name 'Nintex' could not be found"

Not applicable
2 0 4,515

Products: Nintex Workflow 2007, Nintex Workflow 2010, Nintex Workflow 2013

Summary

The following error appears during workflow design and appears in the ULS logs:

"The type or namespace name 'Nintex' could not be found"

Symptom

The following errors appear in the logs:

Microsoft.SharePoint.SPException: <Error><CompilerError Line="0" Column="10" Text="The type or namespace name 'Nintex' could not be found (are you missing a using directive or an assembly reference?)" /><CompilerError Line="19" Column="16" Text="The type or namespace name 'Nintex' could not be found (are you missing a using directive or an assembly reference?)" /><CompilerError Line="18" Column="16" Text="The type or namespace name 'Nintex' could not be found (are you missing a using directive or an assembly reference?)" /><CompilerError Line="17" Column="16" Text="The type or namespace name 'Nintex' could not be found (are you missing a using directive or an assembly reference?)" /></Error> at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(SPWorkflowAssociation as... e776999c-5af4-d067-632b-9fb92fe5da90

...sociation, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association, Boolean fallback) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflow, Collection`1 events, SPWorkflowRunOptionsInternal runOptions) e776999c-5af4-d067-632b-9fb92fe5da90

Cause

This issue can occur when servers have only the Microsoft SharePoint Workflow Timer Service running.

Resolution

Use the following procedure to resolve this issue.

  1. Confirm that every server running the Microsoft SharePoint Workflow Timer Service is also running the Microsoft SharePoint Foundation Web Application service. For more information, seeWorkflows and the SharePoint services required to run them.
  2. To fix any possible configuration issues resulting from this issue, run the following commands from a SharePoint 2010 Management Shell:

    $webapp = Get-SPWebApplication -identity http://WebApplication[:port]

    $webapp.UpdateWorkflowConfigurationSettings()

  3. Activate your web application at Central Admin > Nintex Workflow > Web Application Activation.
Tags (1)