Re: [Ccnet-user] Source control operation timed out

[Mark W. <cc...@wa...>]

Guessing wildly, could it be a permissions problem? Does the CCnetservice
run as a different user? Try stopping the service and running CCNet.exe
(which will run as your logged in user - i.e. the same as the one that you
are using VSS with). Does it work?

________________________________________
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Jay Williams
Sent: Tuesday, 17 October 2006 9:52 a.m.
To: ccn...@li...
Subject: [Ccnet-user] Source control operation timed out

All our builds are failing with the following message:
ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control
operation has timed out. at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(P
rocessInfo processInfo) at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetModifi
cations(ProcessInfo info, DateTime from, DateTime to) at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.GetModifications(IIntegrat
ionResult from, IIntegrationResult to) at
ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(I
SourceControl sourceControl, IIntegrationResult lastBuild,
IIntegrationResult thisBuild) at
ThoughtWorks.CruiseControl.Core.IntegrationRunner.RunIntegration(BuildCondit
ion buildCondition)


However, when I remote into our build box, fire up Visual Source Safe and do
a get, it will get source code, albeit a bit slowly. In the ccnet.config
file, buildTimeoutSeconds is set to 1600 for all our projects. It has NEVER
taken this long to get source and the builds fail in less time than
this.only 5 or 10 minutes.

This all started happening when we rebooted the serer that has all our
source on it. We're banging our heads against the wall trying to figure out
why it's failing. Any ideas would be greatly appreciated!!!

Jay