Hi John, Sorry for the delay in replying - my spam filter got this e-mail :-(
First, from what I can figure out, there is something in your configuration that the pre-processor doesn't like. The really bad news is the exceptions are not defined as serialisable, which is causing problems with the hot-swapping (this uses a separate AppDomain, so it needs to be serialised/deserialised across the AppDomain boundary). Unfortunately, this is as much as I can work out from the error event and log - if you want, I can look into it further, but I will need the config files. If you don't want to send them to the public mailing list, you can send them to my e-mail account - craig.j.sutherland (at) gmail.com. Craig -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of JohnW Sent: Friday, 5 June 2009 2:27 a.m. To: ccnet-user Subject: [ccnet-user] Re: Error starting CCService (CCNet 1.4.4) - Serialization exception Craig, thanks for the quick response. Unfortunately I had to wait until the next day to get to the build server and grab the info... Event Type: Error Event Source: CCService Event Category: None Event ID: 0 Date: 6/4/2009 Time: 10:25:33 AM User: N/A Computer: BUILD01 Description: Service cannot be started. System.Runtime.Serialization.SerializationException: Type 'ThoughtWorks.CruiseControl.Core.Config.Preprocessor.EvaluationException' in Assembly 'ThoughtWorks.CruiseControl.Core, Version=1.4.4.75, Culture=neutral, PublicKeyToken=null' is not marked as serializable. Server stack trace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize (Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize (Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize (Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Ser... For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ccnet.log: 2009-06-04 10:25:29,782 [2172:DEBUG] The trace level is currently set to debug. This will cause CCNet to log at the most verbose level, which is useful for setting up or debugging the server. Once your server is running smoothly, we recommend changing this setting in E: \CC.NET-1.4.4\server\ccservice.exe.Config to a lower level. 2009-06-04 10:25:29,797 [2172:INFO] CruiseControl.NET Server 1.4.4.75 -- .NET Continuous Integration Server 2009-06-04 10:25:29,797 [2172:INFO] Copyright © 2009 ThoughtWorks Inc. All Rights Reserved. 2009-06-04 10:25:29,813 [2172:INFO] .NET Runtime Version: 2.0.50727.1433 Image Runtime Version: v2.0.50727 2009-06-04 10:25:29,813 [2172:INFO] OS Version: Microsoft Windows NT 5.2.3790 Service Pack 2 Server locale: English (United States) 2009-06-04 10:25:31,594 [CCNet Server:INFO] Reading configuration file "E:\CC.NET-1.4.4\server\ccnet.config" 2009-06-04 10:25:33,235 [CCNet Server:DEBUG] Beginning include level 2 for "settings.xml" included by "file:///E:/CC.NET-1.4.4/server/ ccnet.config", resolved to "file:///E:/CC.NET-1.4.4/server/ settings.xml" 2009-06-04 10:25:33,266 [CCNet Server:DEBUG] Ending include level 2 for "file:///E:/CC.NET-1.4.4/server/settings.xml" included by "file:/// E:/CC.NET-1.4.4/server/ccnet.config" 2009-06-04 10:25:33,266 [CCNet Server:DEBUG] Beginning include level 2 for "tds-trunk_builds.xml" included by "file:///E:/CC.NET-1.4.4/server/ ccnet.config", resolved to "file:///E:/CC.NET-1.4.4/server/tds- trunk_builds.xml" On Jun 3, 5:31 pm, Craig Sutherland <[email protected]> wrote: > Hi John, > > Are you using the same config for both the service and the console? > These both use the same pre-processing engine, so if it works with one > it should (in theory) work for the other. > > The other option is to check the log for CC.NET to see if there are > any additional details in there. This is normally in the same folder > as the applications and is called ccnet.log. Hopefully there should be > additional error details (including a stack trace) to help us resolve > the issue. > > Craig > > On Jun 4, 8:30 am, JohnW <[email protected]> wrote: > > > I just installed the 1.4.4 release using setup.exe and cannot start > > the service. I can run successfully using the command line. The error > > is: > > > System.Runtime.Serialization.SerializationException: Type > > 'ThoughtWorks.CruiseControl.Core.Config.Preprocessor.EvaluationException' > > in Assembly 'ThoughtWorks.CruiseControl.Core, Version=1.4.4.75, > > Culture=neutral, PublicKeyToken=null' is not marked as serializable. > > > I was running 1.4.2 but wanted to organize projects and configs better > > so I starting using 1.4.4 with command-line to test the Preprocessor > > stuff. Now that 1.4.4 is released I uninstalled 1.4.4.RC2 and > > installed the released version.
