It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×5,997

question asked: Oct 28 '15, 12:53 p.m.
question was seen: 4,445 times
last updated: May 30 '18, 2:17 p.m.

Related questions

FAQ - How this Forum works

An internal error occurred while starting RTC client

0
Andrzej Wrobel (11●1●1) | asked Oct 28 '15, 12:53 p.m.
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)

Comments
Marek Siekierski commented Oct 28 '15, 1:38 p.m.

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

Andrzej Wrobel commented Oct 28 '15, 4:41 p.m.

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

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.1k●3●36●46) | answered Oct 30 '15, 4:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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.



Comments
Andrzej Wrobel commented Nov 02 '15, 5:29 a.m.

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.

0
permanent link
Chris McGee (505●1●11●17) | answered Nov 03 '15, 2:51 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
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
permanent link
Eric Peters (1●1) | answered May 30 '18, 2:17 p.m.

Repair the metadata worked for me - thanks!

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.