It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,876
×343
×50
×7
×6
×2

question asked: Jun 05 '15, 2:13 p.m.
question was seen: 3,139 times
last updated: Jul 06 '16, 2:12 p.m.

Related questions

Error opening up Plan Editor in Client

1
Norma Madrid (25●2●5) | asked Jun 05 '15, 2:13 p.m.
ACTION: Open a plan editor in client
BACKGROUND: Usually this error is seen when a work item with a progress bar has a error (usually caused by an error importing items). Usually, we delete the work item with the progress bar error and create a new work item to resolve this issue. 

QUESTION: This time, there is no work item with a progress bar issue (see Background section). Any suggestions on how to fix this?

ERROR MESSAGE:
An internal error occurred during operation: "Retrieving Data". See the error log for details.
java.lang.NumberFormatException: For input string: " "path":"\/resources\/internal\/progress""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:59)
at java.lang.Integer.parseInt(Integer.java:460)
at java.lang.Integer.valueOf(Integer.java:565)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.extractStackTrace(MarshallerUtil.java:537)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:402)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:374)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:334)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeFault(MarshallerUtil.java:299)
at com.ibm.team.repository.transport.client.RemoteTeamService.constructExceptionFromFault(RemoteTeamService.java:621)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:505)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:194)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
at com.sun.proxy.$Proxy61.fetchResolvedIterationPlan2(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110)
at com.sun.proxy.$Proxy61.fetchResolvedIterationPlan2(Unknown Source)
at com.ibm.team.apt.internal.client.IterationPlanClient$1.run(IterationPlanClient.java:393)
at com.ibm.team.apt.internal.client.IterationPlanClient$1.run(IterationPlanClient.java:1)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1324)
at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1319)
at com.ibm.team.apt.internal.client.IterationPlanClient.fetchIterationPlanData(IterationPlanClient.java:396)
at com.ibm.team.apt.internal.ide.ui.editor.IterationPlanEditorInput$2.resolve(IterationPlanEditorInput.java:143)
at com.ibm.team.apt.internal.ide.ui.editor.IterationPlanEditorInput$2.resolve(IterationPlanEditorInput.java:1)
at com.ibm.team.apt.internal.ide.core.util.TeamFuture$DefaultResolver.resolve(TeamFuture.java:39)
at com.ibm.team.apt.internal.ide.core.util.TeamFuture$LoadJob.execute(TeamFuture.java:112)
at com.ibm.team.apt.internal.ide.core.util.TeamFuture$LoadJob.access$0(TeamFuture.java:110)
at com.ibm.team.apt.internal.ide.core.util.TeamFuture$LoadJob$1.run(TeamFuture.java:95)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at com.ibm.team.apt.internal.ide.core.util.TeamFuture$LoadJob.run(TeamFuture.java:93)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Accepted answer

0
permanent link
Kevin Ramer (4.5k●9●186●201) | answered Jun 05 '15, 3:32 p.m.
I would suggest looking at the project configuration's Planning / Plan Views in the RTC Eclipse client.  Sometimes unusable views get in there.  Even if the section says "unconfigured" it is helpful to view the section for bad views.  They will be marked with red x on the label.

  1. Right click on Project name in Team Artifacts or Team Organization view
  2. Choose Open
  3. Choose Process Configuration tab along the bottom of the frame
  4. Expand Planning and look at all sections.  
  5. If views are marked bad, remove and save the project config.
May or may not yield any good results, but worth a try.
Norma Madrid selected this answer as the correct answer
Comments
Norma Madrid commented Jun 05 '15, 4:37 p.m.

Hi Kevin--

Thank you for your suggestion. Unfortunately, this did not seem to resolve the issue.

If it helps, I'm running RTC Version 5.0.2

1
Kevin Ramer commented Jun 08 '15, 9:18 a.m. | edited Jun 08 '15, 9:21 a.m.

Check all sections under Planning.   As the error leads with:

java.lang.NumberFormatException: For input string: " "path":"\/resources\/internal\/progress""

I would look at what is used to track progress (Planning / General ).  I would also suggest that you create a query with "Planned for" the bad iteration as the sole criteria and look at things like Story Points, and time estimate values.   Assuming that a (few) specific plans only are affected.

Norma Madrid commented Jun 15 '15, 10:54 a.m.

Thank you, Kevin. We have noted that the plans usually have broken "progress bars". Usually fixing these will resolve the issue. Unfortunately, this doesn't seem to resolve it this time.

Norma Madrid commented Jul 06 '16, 2:12 p.m.

UPDATE:

The issue was resolved as Kevin suggested. When we migrated our tickets from a different system into RTC, the story field was set to an actual string value of "Unassigned". Because empty fields also display as "Unassigned", it was initially overlooked. Once the string value of "Unassigned" was cleared out, this resolved the issue.

Thanks, Kevin!!

Your answer

Register or to post 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.