Solved

unsuccessful with no exception returned from the compiler

  • 3 December 2019
  • 5 replies
  • 11 views

When i deploy a worklow i get this error and i have no information about the same.

Can anyone help?

unsuccessful with no exception returned from the compiler

icon

Best answer by Sabina 4 December 2019, 07:32

View original

5 replies

Good day Sabina, 


Please apply the latest fix-pack on your environment it should help to resolve the issue especially if you are on K2 5.1 fix-pack 21 should help:https://help.k2.com/kb002374


If it's in another K2 version and for best practices please apply the latest or most recent fix-pack.


 


Best regards,


Dumisani


 


 

Badge +9

Hi Sabina


 


See the link below:


https://help.k2.com/support-services/kbt139981


 


https://help.k2.com/support-services/kbt142181


 


Regards


Elvis

Badge +7

Hello  @Sabina 

 

Please review the content below to help solve your error you are having:-

 

Hotfix: An error occurs when deploying a workflow after upgrading to K2 Five (5.2):

https://help.k2.com/kb003201

 

Workflow deployment error in K2 Studio:

https://help.k2.com/support-services/kbs100046

 

Hotfix: An error occurs when deploying a workflow containing a File property:

https://help.k2.com/kb003173

 

Code Fix: An error occurs when editing a workflow deployed from a K2 Package when the workflow has a field referencing a SmartObject:

https://help.k2.com/kb002229

 

Unable to deploy newly created workflows - Login failed for user:

https://help.k2.com/support-services/kbt163166

 

Hotfix: Unable to deploy a solution due to view errors:

https://help.k2.com/kb002424

 

All the best

The issue was resolved when i restarted the K2 Server Service on PROD.

But the solution is uncleared and we did not get into the root cause.

more investigation has to be done for the same.

Hi Sabina,


 


I assume there were changed made to the workflow before it was deployed?  This error can sometimes occur when the logic behind a split event is changed.  Without knowing more information on what was changed or lead to the error occurring, root cause will be difficult to determine.


 


If you are looking for complete root cause analysis on the issue, I'd recommend working with K2's Remote Services team, as they are experts with that sort of thing.  


 


Thanks!


 

Reply