Unable to check out files from StarTeam after StarTeam upgrade

Hello,

Background info:
TeamCity Version 4.0 (Build 8080)
StarTeam SDK Build 10.4.8.36 dated 09/12/2008

The StarTeam server was upgraded from (sorry, don't know) to 10.4.8.54 recently.
Prior to that, TeamCity was working fine.
Neither TeamCity nor the StarTeam SDK were changed.
(There is no newer StarTeam SDK available from Borland that we can see.)

Currently, TeamCity is unable to get source code from StarTeam.
When I do Test Connection on the VCS root, it succeeds.
When a build gets triggered, it fails with:
com.starbase.starteam.NoSuchPropertyException: The type "Project" has no property with ID=0x20016.
at com.starbase.starteam.NoSuchPropertyException.wrap(Unknown Source)
at com.starbase.starteam.Server.wrap(Unknown Source)
at com.starbase.starteam.File.checkoutToStream(Unknown Source)
at jetbrains.buildServer.buildTriggers.vcs.starteam.adapt.StarteamFileImpl.checkout(StarteamFileImpl.java:60)
at jetbrains.buildServer.buildTriggers.vcs.starteam.PatchUtil.patchFile(PatchUtil.java:100)
at jetbrains.buildServer.buildTriggers.vcs.starteam.PatcherImpl.patchFile(PatcherImpl.java:25)
at jetbrains.buildServer.buildTriggers.vcs.starteam.DeferredPatcher$1.run(DeferredPatcher.java:26)
at jetbrains.buildServer.buildTriggers.vcs.starteam.DeferredPatcher.apply(DeferredPatcher.java:57)
at jetbrains.buildServer.buildTriggers.vcs.starteam.StarteamSupport.buildPatch(StarteamSupport.java:430)
... 22 more


StarTeam support is suggesting that TeamCity is attempting to get a property that doesn't exist.
I asked if any properties had been removed per the StarTeam server update- the answer was no.

Someone else who is using the StarTeam SDK in a different manner had no issue.
Not knowing how their use of it compare's to TeamCity's use of the StarTeam SDK, it's hard to conclude anything.

We could use some help in coming up with ideas on how we can troubleshoot the root cause.
As much as it may seem to be an issue with the StarTeam server upgrade, approaching it from that angle has not been productive.

Thank you very much.
Brian

3 comments
Comment actions Permalink

StarTeam integration developer is on vacation now, he will be available on the next week only. Could you please try to upgrade to TeamCity 4.5.1 or install the latest release of TeamCity somewhere with the same configuration and try to reproduce this issue? Anyway it is worth to upgrade because we may not be able to provide a patch for TeamCity 4.0.

0
Comment actions Permalink

Good news.

Rebooting the TeamCity server machine resolved this issue.
Ideally, a reboot would not be required so as to avoid the need to coordinate them, etc.

Bonus Question:
Is TeamCity holding onto any information that might explain why the reboot resolved this?

We are posing a similar question to Borland regarding the StarTeam SDK and will share the response.

Enjoy the weekend!
Brian

0
Comment actions Permalink

Hello Brian,

I'm glad the issue has gone.

Since I'm not aware of SDK implementation I can only suppose that the client
library being run holds some cache of binary representations of StarTeam
properties. The new server version may have different binary values behind
the same property names so it simply may not understand requests containing
values taken from the older server.

After you restarted the client the cache was renewed.

Well, this is my version :)

Good news.

Rebooting the TeamCity server machine resolved this issue. Ideally, a
reboot would not be required so as to avoid the need to coordinate
them, etc.

Bonus Question:
Is TeamCity holding onto any information that might explain why the
reboot resolved this?
We are posing a similar question to Borland regarding the StarTeam SDK
and will share the response.

Enjoy the weekend!
Brian
---
Original message URL:
http://www.jetbrains.net/devnet/message/5237749#5237749

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.