Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

An internal error occurred while starting RTC client

I'm using RHEL 6.6 with
RTC Version: 4.0.6
Build id: RTC-I20140205-1437

I don't know what happened but now I can't build projects because I get an error similar to below (I also get this when I start RTC)


An internal error occurred during: "Updating local SCM data".
Invalid segment "C:\nppdf32Log\debuglog.txt" in [C:\nppdf32Log\debuglog.txt]

the full stack trace is:
java.lang.IllegalArgumentException: Invalid segment "C:\nppdf32Log\debuglog.txt" in [C:\nppdf32Log\debuglog.txt]
at com.ibm.team.filesystem.client.internal.RelativeLocation.validateNameParts(RelativeLocation.java:80)
at com.ibm.team.filesystem.client.internal.RelativeLocation.append(RelativeLocation.java:90)
at com.ibm.team.filesystem.client.internal.ManagedFileStore.getChild(ManagedFileStore.java:1351)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:269)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populateChildren(ManagedFileTree.java:276)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:236)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:224)
at com.ibm.team.filesystem.client.internal.ManagedFileTree.populate(ManagedFileTree.java:194)
at com.ibm.team.filesystem.client.internal.ManagedFileSystem.fetchFileTree(ManagedFileSystem.java:226)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:822)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:808)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:855)
at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:801)
at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1669)
at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:166)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

0 votes

Comments

Czesc Andrzej,


Open terminal and try to run "eclipse -clean" from the Eclipse install directory. Try a new workspace if that doesn't help. Do you still see the same problem?

Marek

Czesc Marek,
I tried with clean option but that didn't work. Still same error. I have other workspaces (different version of the stream) and they are fine.
I also tried to fix my meta data but that fails at the end.

I don't want to create workspace from scratch unless it's only way to fix it.
Thanks



3 answers

Permanent link
Have you tried to repair the metadata:



Otherwise unload the repository workspace and reload it.

I have (rarely) seen Eclipse workspaces getting damaged and the only way out has been creating a new Eclipse workspace in some of the cases.



1 vote

Comments

Yes, I tried that multiple times but I was getting same error.
I think it was related to adobe plugin. RTC is using some embedded web browser and that's why it was probably failing.
I have deleted workspace and recreated and so far it looks much better.
Thanks for your answers.


Permanent link
Rational Team Concert 4.0.6 is getting quite old and there have been improvements in 5.x and now 6.x. Perhaps upgrading the client (and server) will improve stability?

0 votes


Permanent link

Repair the metadata worked for me - thanks!

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 28 '15, 12:53 p.m.

Question was seen: 5,292 times

Last updated: May 30 '18, 2:17 p.m.

Confirmation Cancel Confirm