Invalid UUID
6 answers
This only happens when using the web client. The work item can be accessed via the Eclipse client.
Any ideas? (and telling everyone to use the Eclipse client is NOT the idea I am looking for - even on April 1st ;-)
Try the URL created from the work item in the Eclipse client. If you right-button on the work item tab, copy the URL for the work item and try and paste it in your browser. If that works, I guess something in the web client is pointing it to the wrong place.
regards
anthony
Try the URL created from the work item in the Eclipse client. If you right-button on the work item tab, copy the URL for the work item and try and paste it in your browser. If that works, I guess something in the web client is pointing it to the wrong place.
regards
anthony
Thanks. All seems well now - must have been some kind of transient problem.
I have this exact same issue with the same symptoms.
I tried to copy the URL from the Eclipse client into the Web client. When I do this, it redirects to the following URL:
https://<my>:9443/jazz/web/projects/BPM#action=com.ibm.team.workitem.viewWelcome&error=%20%3A%20invalid%20UUID%20
Any suggestions on how to debug this further?
I tried to copy the URL from the Eclipse client into the Web client. When I do this, it redirects to the following URL:
https://<my>:9443/jazz/web/projects/BPM#action=com.ibm.team.workitem.viewWelcome&error=%20%3A%20invalid%20UUID%20
Any suggestions on how to debug this further?
I have this exact same issue with the same symptoms.
I tried to copy the URL from the Eclipse client into the Web client. When I do this, it redirects to the following URL:
https://<my>:9443/jazz/web/projects/BPM#action=com.ibm.team.workitem.viewWelcome&error=%20%3A%20invalid%20UUID%20
Any suggestions on how to debug this further?
I resolved this. In the work item there was a URL that RTC didn't like. So while I could save the work item with the problematic URL, when I then tried to view the URL in the web client I got the UUID error (interesting that RTC would parse the content such that it put up this message). After bouncing back and forth between the web and Eclipse clients to debug and correct this all is well. My suggestion to debug your issue is use the Eclipse client to look at any URLs contained in the problematic work item and remove them one-at-a-time until you can successfully view the work item in the web client.