Nintex Connect

We are facing a very strange issue on our Production Environment. We have a licensed version of Nintex installed on the server. The Nintex version is 11001.

The issue is  - We have a list where we have a workflow attached to each list item. The workflows were triggered from within a batch job using code. The frequency is monthly once. Last time 25% of the workflows got executed and the rest were showing status as -  Failed on start(Retrying).

Following are some of the Application Log and Share point Logs.

Application Log:

Event Type:        Information

Event Source:    McLogEvent

Event Category:                None

Event ID:              257

Date:                     2/3/2010

Time:                     1:32:57 AM

User:                     NT AUTHORITY\SYSTEM

Computer:          XXXXXXXX

Description:

Blocked by access protection rule.  Access to object C:\Documents and Settings\XXXXXXX\Local Settings\Temp\54d346bf-a4eb-4437-ae79-243a732dce8d\Xoml.50b63211_0577_43f4_80b9_d656a14fc3e1.227.17408.229.17408.dll was blocked by rule Common Standard Protection:Prevent common programs from running files from the Temp folder.

SharePoint Log:

Type: BigInt Size: 0 Direction: Input Value: '729'     Parameter: '@CurrentVersion' Type: BigInt Size: 0 Direction: Output Value: ''               

02/03/2010 00:51:30.29 OWSTIMER.EXE (0x146C)                              0x0378  Windows SharePoint Services   Workflow Infrastructure                    72fs        Unexpected       RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="-1" Column="-1" Text="Compilation failed. Could not load file or assembly 'Xoml.50b63211_0577_43f4_80b9_d656a14fc3e1.227.17408.229.17408, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Access is denied." /></Error>     at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(String assmNameIn, SPWeb web)     at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(Guid trackingId, SPWorkflow workflow)     at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalW...         

02/03/2010 00:51:30.29*              

OWSTIMER.EXE (0x146C)                              0x0378  Windows SharePoint Services   Workflow Infrastructure                    72fs        Unexpected       ...orkflow, SPWorkflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)    

02/03/2010 00:51:30.29 OWSTIMER.EXE (0x146C)                              0x0378  Windows SharePoint Services   Workflow Infrastructure                    98d7      Unexpected       Microsoft.SharePoint.SPException: <Error><CompilerError Line="-1" Column="-1" Text="Compilation failed. Could not load file or assembly 'Xoml.50b63211_0577_43f4_80b9_d656a14fc3e1.227.17408.229.17408, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Access is denied." /></Error>     at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(String assmNameIn, SPWeb web)     at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(Guid trackingId, SPWorkflow workflow)     at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)     at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalWorkflow, SPWo...           

02/03/2010 00:51:30.29*               OWSTIMER.EXE (0x146C)                              0x0378  Windows SharePoint Services   Workflow Infrastructure

Hi,

We have seen similar issues in the past. This issue is usally related to uploading multiple (20+ items) to the doc library/list at the same time.

SharePoint will batch the workflows and process ~7 at the same time. The others are queued and processed later.

The queuing process is indicated by a fail to start or starting message in the workflow status column (as you are seeing).  Eventually these workflows should also run and start as normal. This behaviour is controlled by SharePoint.

Hi Peter,

Thanks for your response. But in this case we are starting just 10 at a time. And then we have posted a one minute delay.

Also the workflows didn't start even after long time.

Any ideas what could be the possible cause.

The logs pointed to sharepoint could not to load the assembly XXXXX.

Hi,

We are also facing exactly the same issue, was anyone ever able to resolve this?

Thanks,

 Abhishek