Hi Thanks yes, I did this and eventually tracked it down to " chars in some paths. It's weird that it's OK to use " in some places and I have to use " in others.
v 1.5 does not give me any clues to where the error is in the error output. v 1.6 did at least tell me the node it was trying to process so that made it a lot easier. The ideal would be to have it output the element that was the issue and/or the line number of the config file. Cheers On Sat, Jun 11, 2011 at 10:06 AM, Adam Bruss <[email protected]> wrote: > Comment out all but one project in your config to reduce the amount of > possibilities. > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Jonesie > Sent: Thursday, June 09, 2011 6:10 PM > To: ccnet-user > Subject: [ccnet-user] Illegal characters in path after upgrade > > > > Hi > > > > Im trying to upgrade from 1.4 to 1.5 and when I start the server I get this > error: > > > > 2011-06-10 11:04:06,739 [CCNet Server:ERROR] INTERNAL ERROR: Illegal > characters in path. > > ---------- > > System.ArgumentException: Illegal characters in path. > > at System.IO.Path.CheckInvalidPathChars(String path) > > at System.IO.Path.IsPathRooted(String path) > > at > > > ThoughtWorks.CruiseControl.Core.Tasks.BaseExecutableTask.Validate(IConfiguration > > configuration, ConfigurationTrace parent, IConfigurationErrorProcesser > > errorProcesser) > > at ThoughtWorks.CruiseControl.Core.Project.ValidateItem(Object > > item, IConfiguration configuration, ConfigurationTrace parent, > IConfigurationErrorProcesser errorProcesser) > > at > > ThoughtWorks.CruiseControl.Core.Project.ValidateItems(IEnumerable > > items, IConfiguration configuration, ConfigurationTrace parent, > IConfigurationErrorProcesser errorProcesser) > > at ThoughtWorks.CruiseControl.Core.Project.Validate(IConfiguration > > configuration, ConfigurationTrace parent, IConfigurationErrorProcesser > > errorProcesser) > > at > > > ThoughtWorks.CruiseControl.Core.Config.NetReflectorConfigurationReader.ValidateConfiguration(Configuration > > value, IConfigurationErrorProcesser errorProcesser) > > at > > > ThoughtWorks.CruiseControl.Core.Config.NetReflectorConfigurationReader.Read(XmlDocument > > document, IConfigurationErrorProcesser errorProcesser) > > at > > > ThoughtWorks.CruiseControl.Core.Config.DefaultConfigurationFileLoader.Load(FileInfo > > configFile) > > at > > ThoughtWorks.CruiseControl.Core.Config.FileConfigurationService.Load() > > at > > > ThoughtWorks.CruiseControl.Core.Config.FileWatcherConfigurationService.Load() > > at > > ThoughtWorks.CruiseControl.Core.Config.CachingConfigurationService.Load() > > at > > ThoughtWorks.CruiseControl.Core.CruiseServer..ctor(IConfigurationService > > configurationService, IProjectIntegratorListFactory > projectIntegratorListFactory, IProjectSerializer projectSerializer, > IProjectStateManager stateManager, IFileSystem fileSystem, > IExecutionEnvironment executionEnvironment, List`1 extensionList) > > at > > ThoughtWorks.CruiseControl.Core.CruiseServerFactory.CreateLocal(String > > configFile) > > at > > ThoughtWorks.CruiseControl.Core.CruiseServerFactory.Create(Boolean > > remote, String configFile) > > at ThoughtWorks.CruiseControl.Core.ConsoleRunner.Run() > > at ThoughtWorks.CruiseControl.Console.AppRunner.Run(String[] args, > Boolean usesShadowCopying) > > ---------- > > > > > > This is not particularly helpful! There are lots of paths in the file and > it used to work fine with 1.4 so I know the paths are correct. A line > number in the message would be really helpful! > > > > Is there a way I can track this down ? > > > > Thanks >
