Error creating new RQM lifecycle project - RQM 3.0.1.3 - Windows 7
![]()
yolanda moya (11●1●2)
| asked Jul 10 '12, 5:15 a.m.
edited Jul 10 '12, 5:13 p.m. by Robert Rassmann (992●3)
Hi,
Did anybody have this specific problem with RQM 3.0.1..3? What could I do? Here is the stacktrace when trying to create a new lifecycle project, in the second step (Initializing cross application communication): hide details Error Stacktrace: com.ibm.team.lpa.automation.TaskException: java.io.IOException: Unexpected character "60": line 1, column 1at com.ibm.team.lpa.common.tasks.AbstractGETTask.runTask(AbstractGETTask.java:83) at com.ibm.team.lpa.common.tasks.AbstractTask.run(AbstractTask.java:56) at com.ibm.team.lpa.automation.CompositeTask.run(CompositeTask.java:158) at com.ibm.team.lpa.automation.CompositeTask$MonitoredSubTask.run(CompositeTask.java:71) at com.ibm.team.lpa.automation.CompositeTask.run(CompositeTask.java:158) at com.ibm.team.lpa.common.tasks.LoggingCompositeTask.run(LoggingCompositeTask.java:37) at com.ibm.team.lpa.automation.AsyncTask$TaskRunner.run(AsyncTask.java:40) at java.lang.Thread.run(Thread.java:811) Caused by: java.io.IOException: Unexpected character "60": line 1, column 1 at com.ibm.team.json.internal.Tokenizer.next(Tokenizer.java:112) at com.ibm.team.json.internal.Parser.parse(Parser.java:31) at com.ibm.team.json.JSONObject.parse(JSONObject.java:81) at com.ibm.team.lpa.common.tasks.AbstractGETTask.runTask(AbstractGETTask.java:81) ... 7 more If I go to the tab "Projects", I see an error message: Error retrieving artifact containers. |
2 answers
![]()
The stack says that you are getting a parse error due to an invalid character but I don't see any indication on what might be the cause. I did see a similar error message in https://jazz.net/forum/questions/59618/crjca0069e but it looks like the cause there is different. You may need to open a support ticket on this one.
|
![]()
I did reinstall everything and now is working...
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.