BPM Errors after update to 2.36.3

[Ralf Peters]

just updated to 2.36.3  , select our normal   BPM   and getting this error now !

ticket number is SR00019713  if you want to check on our system

Thanks

Ralf 

 

[Martyn Houghton]

@Ralf Peters

This might be related to a similar issue we are having another Team based BPM node, see post below.

Cheers

Martyn

 

 

[Ralf Peters]

@Martyn Houghton 

Thanks , yes looks the same to me !

 

Ralf

[ArmandoDM]

Hi @Ralf Peters,

can you please provide a screenshot on the node in your BPM where you have selected this operation "Assign to Owner" ? 

I run a few tests and it works for me, so we're trying to reproduce the issue.

 

Regards,

 

Armando

[Ralf Peters]

@ArmandoDM

screenshot attached  :

if  the task is picked up  manually :

if asigned round robin :

[Ralf Peters]

@ArmandoDM

some of the error messages :

 

SQL error 1052 !

[Paul Morrow]

I'm having exact same issue too.

[ArmandoDM]

Hi @Ralf Peters,   @Paul Morrow

we are investigating about this issue. We will get back to you .

 

Regards,

 

Armando

[nasimg]

We are seeing similar errors following the 2.36.3 patch

[Steve G]

Hi @Ralf Peters, @Martyn Houghton, @Paul Morrow, @nasimg,

The distinct errors that have been raised in this post, and those in the below post, are fixed, and the fixes will be included in the 2.36.4 patch. This patch is on course for release this afternoon.

Kind regards,

Steve

 

[Steve G]

Good morning @Ralf Peters, @Martyn Houghton, @Paul Morrow & @nasimg,

Service Manager 2.36.4 is now live, so please feel free to apply this to your Hornbill instances to take advantage of the fixes contained within this patch.

Kind regards,

Steve

[Paul Morrow]

Looks back to normal in my case anyway.

[Hornbill Staff DR]

Hi All,

 I can confirm that the root causes to the recent spate of BPM errors seen earlier this week have been addressed in the 2.36.4 and 2.36.5 patches. We of course advise that those of you still on Service Manager version 2.36.3 update to the latest available build in order to avoid encountering these known issues.

It is possible to rectify any failed BPM processes effected by these particular issues by using the "Process Restart" capability which retries the last failed operation in a Requests' Workflow. If after updating to the latest build pressing the process restart does not allow the workflow to continue, it is likely a new, unrelated issue and should be reported as such.

Dan