Error: Unhandled exception: 'Object reference not set to an instance of an object.'

Permanently deleted user

May 24, 2019 22:49

How would one go about troubleshooting this error.

 

Thank you.

0

• 

  Permanently deleted user

  May 24, 2019 22:54

  Hi Ryan,

   

  It really depends on where you are seeing the error.  The error is stating that there is a variable that is being accessed and the variable is not set to anything.  In reality, this should never happen.  If it's a workflow error, a workflow variable is being accessed before the variable is set to anything.  If you are seeing this in the viewer or Essentials somewhere, the error should have been trapped and a more friendly error displayed.

   

  Feel free to provide more details if possible.

   

  Regards,

   

  Wayne

  0
• 

  Permanently deleted user

  May 27, 2019 18:37

  Hi Wayne,

   

  Thanks for the response.

   

  This error is being seen in the viewer:

   

  I have found the activity in Workflow Designer, and can reproduce the error with the workflow simulator.

   

  Can you point me to any resources on how to debug a workflow?

   

  I'm parsing the W3SVC1 log files and having a hard time correlating what's in the log to the error. 

   

  Thanks.

   

   

   

   

   

   

  0
• 

  Permanently deleted user

  May 27, 2019 18:51

  Hi Ryan,

   

  If you find the 'Assign' activity (done by searching for 1.2909 in the search bar) and look at the right side of the Assign, see what is trying to be assigned, it doesn't like the value of it.  You can try adding an Alert to see what the value of the item on the right side is currently equal to, but it sounds like it's not set to anything so you would most likely need to look higher up in the workflow, to see where it is being set.  An 'Alert' may also throw an error, the same error, indicating the item is set to nothing.

   

  Feel free to open a support ticket if you want help troubleshooting this.

   

  Regards,

  Wayne

  0

Please sign in to leave a comment.