Sometimes is a good idea to create an exclusive build user (local or domain), configure the service with this account and login to the build machine with that user to avoid this kind of problems. If everything is configured to run with your personal account, everything will stop working if your account is disabled for some reason.
Rolando El 27 de abril de 2012 12:16, Rolando Valdivia <[email protected]>escribió: > When you have this kind of differences between console and service, > remember that the service runs with certain user credentials and console is > running with your current credentials. > > Environment variables can also be per user or machine. > > Verify that the service credentials can access your environment variables, > certificates and other resources that may be accessoble to your current > user only. > > Rolando > El 27/04/2012 11:53, "Chris" <[email protected]> escribió: > > I don't think this is a Nant issue since the differentiating factor is >> how ccnet is run, console vs. service, so I'm asking here. >> >> I call a nant script from ccnet, and I have the following Nant >> target. >> >> <target name="deleteLockFiles"> >> <exec program="${cmdexe}" commandline="/C dir "$ >> {testFileDirectory}"" /> >> <delete> >> <fileset> >> <include name="${lockFiles}" /> >> </fileset> >> </delete> >> </target >> >> When ccnet is running as a console, I'm able execute the <exec> call >> that lists the directory contents. Of course simply executing the nant >> script from command line works too. >> >> But when I'm running ccnet as as service, I get >> >> <task name="exec"> >> <message level="Warning"><![CDATA[The system cannot find the >> path specified.]]></message> >> <duration>218.7906</duration> >> </task> >> >> Any clues? > >
