Skip to main content
Answer

Error upgrade Upcycler 2023.3 to 2024.1

  • May 14, 2024
  • 4 replies
  • 70 views

Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil

I tried to upgrade the upcycler from 2023.3 to 2024.1 from the deployment package.. It gave the following error:

2024-05-14 14:24:03.302 -03:00 [Error] Graph does not contain the provided target vertex. (Parameter 'target')
System.ArgumentException: Graph does not contain the provided target vertex. (Parameter 'target')

 

Best answer by Erwin Ekkel

Seems to be something wrong with the upcycler, i can reproduce this error myself as well. A ticket is reported for this problem and is forwarded to our development team to investigate. 

This topic has been closed for replies.

4 replies

Forum|alt.badge.img+17
  • Moderator
  • May 15, 2024

Can you try downloading the package once more from TCP? It seems to be a malfunction in the download task from TCP. Let me know if it works on a 2nd download. Otherwise I could try sending you the package. 


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • May 21, 2024

Can you try downloading the package once more from TCP? It seems to be a malfunction in the download task from TCP. Let me know if it works on a 2nd download. Otherwise I could try sending you the package. 

same issue

2024-05-21 07:29:34.594 -03:00 [Error] Graph does not contain the provided target vertex. (Parameter 'target')
System.ArgumentException: Graph does not contain the provided target vertex. (Parameter 'target')
   at QuikGraph.Algorithms.RankedShortestPath.HoffmanPavleyRankedShortestPathAlgorithm`2.Compute(TVertex root, TVertex target)


Forum|alt.badge.img+3
  • May 22, 2024

I have the same error (2023.2 to 2024.2, but also with the package 2024.1 to 2024.2).

In the Main menu the new version is missing in the text:

“Upgrade an existing Thinkwise Upcycler to .”

Normally you'll see ‘2024.2’.


Forum|alt.badge.img+17
  • Moderator
  • Answer
  • May 24, 2024

Seems to be something wrong with the upcycler, i can reproduce this error myself as well. A ticket is reported for this problem and is forwarded to our development team to investigate.