Problem checking out files with ss.exe in release 3.1.2

I was having problems earlier with vss and 3.1.1. Issue was that Teamcity was not checking out files correctly after they've been moved inside vss. I did the research and found out that 3.1.2 suppose to have fixed the problem. I upgraded my build server to the newest version, and now I'm running into this problem. I am building on windows 2003 64bit server. I noticed that the installation directory for vss is under "Program Files (x86)". Can someone shed some light on this issue?

: Could not get project sources: for build #36[11:10:02]: jetbrains.buildServer.vcs.VcsException: Getting sources for checkout rule '.=>.' failed with erorr: ss.exe has failed to start:


jetbrains.buildServer.vcs.VcsException: Getting sources for checkout rule '.=>.' failed with erorr: ss.exe has failed to start:


at jetbrains.buildServer.vcs.VcsSupportUtil.buildPatch(VcsSupportUtil.java:25)
at jetbrains.buildServer.buildTriggers.vcs.vss.VssSupport.buildPatch(VssSupport.java:68)
at jetbrains.buildServer.serverSide.impl.projectSources.SmallPatchCache.getCachedCleanPatch(SmallPatchCache.java:25)
at jetbrains.buildServer.serverSide.impl.projectSources.PatchCacheImpl.buildCleanPatch(PatchCacheImpl.java:44)
at jetbrains.buildServer.serverSide.impl.projectSources.PatchComposer.buildPatch(PatchComposer.java:58)
at jetbrains.buildServer.serverSide.impl.projectSources.PatchComposer.buildPatch(PatchComposer.java:127)
at jetbrains.buildServer.serverSide.impl.projectSources.PatchComposer.buildPatch(PatchComposer.java:75)
at jetbrains.buildServer.serverSide.impl.BuildTypeImpl.buildPatch(BuildTypeImpl.java:185)
at jetbrains.buildServer.serverSide.impl.BuildTypeImpl$$FastClassByCGLIB$$a84db719.invoke() at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:696) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at jetbrains.buildServer.serverSide.impl.auth.TeamCityMethodSecurityInterceptor.invoke(TeamCityMethodSecurityInterceptor.java:5) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$FixedChainStaticTargetInterceptor.intercept(Cglib2AopProxy.java:578) at jetbrains.buildServer.serverSide.impl.BuildTypeImpl$$EnhancerByCGLIB$$cd071f9d.buildPatch(]]>)
at jetbrains.buildServer.serverSide.impl.BuildStarter$3.run(BuildStarter.java:27)
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: jetbrains.buildServer.vcs.VcsException: ss.exe has failed to start:


at jetbrains.buildServer.buildTriggers.vcs.vss.SSPatchBuilder.checkoutSSLatest(SSPatchBuilder.java:6)
at jetbrains.buildServer.buildTriggers.vcs.vss.SSPatchBuilder.start(SSPatchBuilder.java:58)
at jetbrains.buildServer.buildTriggers.vcs.vss.VssSupport.buildPatch(VssSupport.java:106)
at jetbrains.buildServer.vcs.VcsSupportUtil.buildPatch(VcsSupportUtil.java:33)
... 22 more
: Could not get project sources[11:10:02]: Error while applying patch: Getting sources for checkout rule '.=>.' failed with erorr: ss.exe has failed to start:

12 comments
Comment actions Permalink

Could you please try moving vss to folder without spaces.
Do you have spaces in vss path, like $/PROJECT?

Please attach debug logs from server. To enable debug, please have a look to
http://www.jetbrains.net/confluence/display/TCD4/Reporting+Issues

Thanks!

0
Comment actions Permalink

The path I gave was for the actual vss installation. My repository is in a directory without any spaces, and the project path within vss doesn't have any spaces either. I'm attaching the buildserver logs.



Attachment(s):
teamcity-agent.log
wrapper.log
launcher.log
0
Comment actions Permalink

Please attach logs from server side. All you have attached was from build agent. VSS checkout is done only on the server.

0
Comment actions Permalink

Here's the server log. Not seeing much more than the exception itself. Thanks for looking into it.



Attachment(s):
teamcity-vcs.log
0
Comment actions Permalink

Does that command line works if start from cmd.exe:
"C:\Program Files (x86)\Microsoft Visual SourceSafe\ss.exe" Get $/trunk -R -Vd9/23/2008;8:10:58a -Yteamcity,build -I-Y -W -GF- -GTM -GWR

Thanks!

0
Comment actions Permalink

Yes, after I set the ssdir, that line works in any directory I tried.

0
Comment actions Permalink

Could you please try running it from 64bit cmd.exe and 32bit cmd.exe process. Are there any differences?

0
Comment actions Permalink

I ran again the same command using both the cmd.exe under system32 folder, then the one under syswow64 folder. Both times the command ran flawlessly. Doesn't appear to be any difference.

0
Comment actions Permalink

What is the user that is used to run TeamCity server service? Does that used have enough rights to access VSS?
Thanks!

0
Comment actions Permalink

It runs under Local System account. And the thing is it's detecting all the changes I checked into VSS, and attempting to do the build. So the problem seems to lie with trying to execute ss.exe. You think it's security preventing it to start ss.exe?

0
Comment actions Permalink

That could be so. Could you please try changing from local system account to some real account.
BTW. Do you use mapped network drive for VSS database? If so, please try using network path instead, because under service there could be no network drive mappings.
Thanks!

0
Comment actions Permalink

It's indeed the security. Looks like cmd.exe was being locked down in my environment. Thanks for the help.

0

Please sign in to leave a comment.