Skip to main content
Nintex Community Menu Bar

Error: Value cannot be null. Parameter Name: systemName

  • March 19, 2020
  • 7 replies
  • 355 views
  • Translate

Forum|alt.badge.img+6
  • Rookie
  • 38 replies

K2 Five 5.2 Designer

 

We are currently in the midle of building a very complex workflow with several steps. After many successfull deployments, we are now getting this error which prevents deployment.

 

The error message, as always, is quite opaque. Any ideas on what the issue is?

 

What is systemName and why is it null? How can we correct?

 

12435iFF87D67BFD1AE904.png


14220iC6B0565BCB2D0A4A.png

Did this topic help you find an answer to your question?

7 replies

  • 95 replies
  • March 19, 2020

Hi  @VA1 


 


Can you please try the following:


 



  1. Navigate to management site > Environment Library> Development

  2. Locate the "SmartObject Server," select it and click Edit 

  3. Ensure the "Set as Default" checkbox is checked


Also:



  1. Navigate to management site > Environment Library>Production

  2. Locate the "SmartObject Server," select it and click Edit 

  3. Ensure the "Set as Default" checkbox is checked


Regards


HulisaniN

Translate

Forum|alt.badge.img+6
  • Author
  • Rookie
  • 38 replies
  • March 19, 2020
This is a Development server. Yes, the Development environment library is marked as Default and the SmartobjectServer Key/Value is accurate and set as Default.

Any other ideas?
Translate

  • 137 replies
  • March 20, 2020

HI VA1,


 


You can try the below, but before doing so, ensure that you have created a backup of your K2 DB.


 


1. You can try to Delete designtime version of workflow to revert back to the last major deployed version. This will restore the deleted references and allow the workflow to properly deploy with no error


 


2. Or you can check the mappings on your SMO, ensure that the values are all in sync


 


Should you feel that this post is of use and or an accurate solution to the raised question, I kindly encourage you to mark it as such
using the 'Mark as Solution', 'Kudo' andor ‘Me Too’ options.


 


Cheers,
Kate


 


K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.

Translate

  • 9 replies
  • March 20, 2020

Hello,

It seems your SmartObject is not referenced properly as per the error null value is being passed against the property which is not null.

 

Please try publishing your SMO again and map the properties accordinlgy. 

 

The reason for this could be you might have updated SMO but in the workflow it is still referring to the older one.

 

Hope above help.

 

Thanks

Snehil

Translate

  • 2 replies
  • March 24, 2020

Hi,

I have the exact same error on a brand new workflow ( in k2 5.2 )

I checked the mapping of every called SMO of my workflow and i can't figure out where the problem is.

I even checked each called SMO method in object browser.

Is there a way to have a more precise explanation as which block is concerned?

 

Because as it is right now, it is very frustrating.

 

Regards

 

Eric

Translate

Forum|alt.badge.img+6
  • Author
  • Rookie
  • 38 replies
  • March 25, 2020

FYI I gave up on this, reverted back to the last successful deployment , lost a few days of work.

 

The K2 Five Designer is honestly a disaster, I hate it.

  1. Too much clicking around
  2. error messages are meaningless,
  3. references break all the time,
  4. no capability to do a global search and replace
  5. or even just a search (e.g. show me all steps that use the following SMO/property/method/data field/whatever),
  6. for complex workflows, multiple developers are unable to collaborate
  7. the list goes on.

Yes, I realize I can make suggestions on ideas.k2.com and I will do that.

Translate

Forum|alt.badge.img+1
  • Novice
  • 5 replies
  • November 17, 2022

Hi ,have you solved this problem. Regards

 

 

 

 

 

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings