Skip to main content
Nintex Community Menu Bar

Workflow not moving to next user task with error: "Invalid URI, The hostname could not be parsed"

  • February 16, 2021
  • 2 replies
  • 173 views
  • Translate

MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • Nintex Employee
  • 671 replies
 

Workflow not moving to next user task with error: "Invalid URI, The hostname could not be parsed"

kbt165928

PRODUCT
K2 Five
BASED ON
K2 Five (all)
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

When starting a new instance of a workflow it will go into an error state with the error:

Invalid URI, The hostname could not be parsed.

Image

Symptoms

Users will not receive the task event as expected.

Resolution

First validate if the SmartForms Runtime SSL URL is blank or has as space:

Image

If this is the configuration on the Enviromental Fields, the configuration is incorrect and will raise the error.

To resolve this you will need to update the SmartForms Runtime SSL URL with a valid URL that is configured on your IIS Server.

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

2 replies

  • 14 replies
  • September 16, 2021

Hi,

I have same problem but error shows in only 1 workflow. I cannot find solution to this. Settings smartforms runtime ssl url seems to be valid. Any idea how else could i solve it? Sample error log from server:

""1016234278","2021-09-16 11:45:49","Error","General","28083","ExtenderExecuteError","ProcessInstance.HandleException","28083 ClientEvent: Invalid URI: The hostname could not be parsed.
InnerException: Exception has been thrown by the target of an invocation.
InnerException: Invalid URI: The hostname could not be parsed.","","","[servername]:D:Program Files (x86)K2 blackpearlHost ServerBin","1016234278","fd295fd8d1be4777a11171d09d4cdc61",""

Translate

  • 14 replies
  • September 16, 2021

Update I have redeployed workflow, and started it again and everything seems working (for now)

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