Intermittent error collecting changes for StarTeam vcs root

Hello

We are using TeamCity Enterprise 4.5.4 accessing StarTeam vcs (2008). We are experiencing a rather odd issue with a VCS root, it seems to work fine for a day or two and then this exception is thrown. If we delete and recreate the VCS root it works for about a day and then starts complaining again. We do have other VCS roots configured for different projects and none of them seem to have the same issue. Are we missing any permission settings in StarTeam for this project? Thanks


jetbrains.buildServer.vcs.VcsException: Error collecting changes for VCS root 'starteam://starteam:49201/proj/trunk' #280
You do not have access rights to perform this operation. If you need access, contact your administrator.
    at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$1.collectChanges(StarteamSupport.java:165)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader$1.collectBuildChanges(VcsChangesLoader.java:1)
    at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:37)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesByIncludeRules(VcsChangesLoader.java:126)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges(VcsChangesLoader.java:160)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:115)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChangesForRule(VcsChangesLoader.java:179)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectChanges4CommonCheckoutRule(VcsChangesLoader.java:139)
    at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChangesForRoot(VcsChangesLoader.java:69)
    at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:252)
    at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:29)
    at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:11)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
    at java.util.concurrent.FutureTask.run(FutureTask.java:123)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)
Caused by: You do not have access rights to perform this operation. If you need access, contact your administrator.
    at com.starbase.starteam.ServerException.wrap(Unknown Source)
    at com.starbase.starteam.Server.wrap(Unknown Source)
    at com.starbase.starteam.Folder.getHistory(Unknown Source)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamItemImpl.getNativeHistory(StarteamItemImpl.java:108)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamFolderImpl.getHistory(StarteamFolderImpl.java:91)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.ChangesCollector.processHistory(ChangesCollector.java:234)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.ChangesCollector.processEdits(ChangesCollector.java:205)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.ChangesCollector.collectChanges(ChangesCollector.java:69)
    at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport$1.collectChanges(StarteamSupport.java:157)
    ... 17 more

14 comments
Comment actions Permalink

SDK version - StarTeam SDK 10.4

0
Comment actions Permalink

Hello,

This is really odd. Please, when it happens again, try to read the history of any project item using the native StarTeam client under the same user. I wonder if it results in some error message or something unusual.

0
Comment actions Permalink

Thanks, I will try that. One more detail - We recently (about two months ago) upgraded StarTeam 5.2 to 2008. The sources of the VCS roots that are working fine were migrated from 5.2 to 2008. This project(proj) was created after we moved to StarTeam 2008, so I am not sure if we would have this problem with all the new projects (may be we are missing an access right somewhere in StarTeam 2008)

0
Comment actions Permalink

Well, it would be interesting to check this too on some other new project. Then it potentially could be a case for Borland support.

0
Comment actions Permalink

The baffling thing is that it works fine for a couple of days and then stops working, despite the fact that nothing was changed or interfered with.

0
Comment actions Permalink

TeamCity itself doesn't accumulate or cache any StarTeam specific information that can potentially become inconsistent in some time. When you recreated the root, did you specify absolutely the same settings and credentials?


0
Comment actions Permalink

Yes, deleted the vcs root and re-created it with exactly the same settings

0
Comment actions Permalink

Very strange...
How many times did it happen?
Did you manage to repeat the problem on a new project?

0
Comment actions Permalink

I can imagine one case, when such a problem may potentially occur.

Someone's made a change within that project (say added a folder), and this folder is visible for the user, under which TeamCity accesses the repository. But this user has no permission to see the history of this folder.
TeamCity analyses items' history in order to detect changes.

This explains the fact that recreating the VCS root helps -- the newly created root isn't checked for older changes.

Please ensure that in all problematic projects the user under which TeamCity accesses them has the permission "see history" for all the folders.

0
Comment actions Permalink

Yes, that might be it. We have added this access right in StarTeam, will keep you posted. Thank you for your help.

0
Comment actions Permalink

Thank you. Please let me know if you get success. I should probably add better diagnostics for such a case.

0
Comment actions Permalink

Sure thing, will keep you informed. Thanks again.

0
Comment actions Permalink

We haven't had any issues as yet, marking issue as resolved. Thanks again for your help Sergey

0
Comment actions Permalink

Thank you! I've added an issue regarding this problem http://youtrack.jetbrains.net/issue/TW-9889.

0

Please sign in to leave a comment.