Thanks very much Craig and Ruben. I should have specified what type of drive n: is; as you can probably tell from the nature of my question I am new to CCNET setup. Unfortunately, N: is really just something my work group uses as an alias for a system directory, to make automated version control checkouts simpler, I suppose. In other words, N: is just a drive mapped to a local system directory, not a network drive. It does seem to be related to running as a service, though, because if I am reading ccnet.exe output correctly, I am not encountering the same issue there.
Thanks, Nick On Jan 6, 1:13 am, "Ruben Willems" <[email protected]> wrote: > Hi > > another option is to use UNC paths > so \\servername\\sharename > iso N:\ > > with kind regards > Ruben Willems > > On Mon, Jan 5, 2009 at 11:08 PM, n.b. <[email protected]> wrote: > > > I have run ccnet.exe with my current configuration, and it seems to > > work fine for the most part, but when I use ccservice, I am receiving > > this error for all of my projects: > > > ThoughtWorks.CruiseControl.Core.Tasks.BuilderException: Unable to > > execute: N:\...\NAnt.exe -D:BuildEnvironment=DEV > > System.IO.DirectoryNotFoundException: Directory does not exist: N:\... > > \cruise > > > The directory that is indicated not to exist is identified as the > > baseDirectory in the ccnet.config file. It does indeed exist. > > > I have also tried running the service both with a local account and > > with my own domain account (which, as I understand it, is what I was > > running ccnet.exe with). > > > If anyone has any ideas, or has encountered a similar "directory not > > found issue", please let me know. Thanks, > > > Nick
