NINTEX Workflow doesn't work after moving

  • 23 April 2015
  • 5 replies
  • 0 views

Badge +3

Hi all,

We did an SharePoint upgrade from 2010 to 2013. Additionally we moved our SP webapplication which includes a recruitng workflow and of course we use NINTEX WF 2013.

Now all the moves are made successfully.

Everything seams to be there which we had before,

No Errors when we moved BUT...

Now I get always emails that workflow errored (not all wf's but some):

The WF has ended unexpectedly.....

. . .

When I start a new WF, there is no error message (first). But the following tasks obviously don't go out....

Something I forgot here I guess, but I don't know where to search.

What could I try?


5 replies

Badge +3

I try now to Change the "Database Mappings" (in the Central Administration).

Actually it set on...   Any Available Workflow Database Content

to explicitely the one Content DB.

CentralAdmin: Monitoring - Review Job Definitions:

1. Stopped NINTEX Scheduler Job

2. Stopped Workflow Job

Then Central Administration - NINTEX - Workflow Database Setup --> Manage Database Mappings:

Change from... Any Available Workflow Database Content

to (new)....        NAME (of the Content database)....

Reset the IIS

The activate the two Job Definitions again.

Will test and post the result here....

Badge +3

No effect yet.

Further Information will follow a.s.a.p.

I found a message that the first wf in this process was chancelled by the "systemaccount".

??

Userlevel 5
Badge +12

A lot of times this error pops up when an action has timed out.   Have you opened the workflow in the designer to check and see if any configuration errors exist?  Sometimes they aren't noticeable until viewed inside the designer.   When moving from environments, references to "resources" such as lists can easily become broken.   There can also be issue with URLs no longer accessible from the new env.


Thanks

Badge +16

‌ did you resolve this in the end?  

Badge +3

Hi Cassy

It's been a Long time ago since this Problem occured. I think it's solved....almost now it works.

Reply