Hi now I'm a bit lost :(
° you have your old buildserver, running ok ° old build server has a dashboard, visualizing old buildserver, all ok ° you set up a new buildserver, running ok ° you can connect to the new build server via cctray --> only problem : visualizing the 2 buildservers via the dashboard on the old buildserver correct? I do not see anything wrong with your dashboard config, you did iis reset, did you also do a force refresh with your browser (CTRL+F5) just a long shot, but want to be sure. with kind regards Ruben Willems On Mon, Aug 3, 2009 at 10:47 PM, Saran <[email protected]> wrote: > > Hi Ruben, > > Yes, I'm able to see the new build server on the CCTray running on my > older server. > > Thanks > Saran > > On Aug 3, 3:33 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > if you copy cctray to the same machine where the dashboard is running, > > do you see the new buildserver ? > > > > with kind regards > > Ruben Willems > > > > On Fri, Jul 31, 2009 at 5:03 PM, Saran <[email protected]> wrote: > > > > > Hi Ruben, > > > > > Update: > > > > > I'm able to add the new machine to my CCTray without any problem. > > > > > Thanks > > > Saran > > > > > On Jul 31, 10:59 am, Saran <[email protected]> wrote: > > > > Hi Ruben, > > > > > > Thanks for quick reply, I did the above steps but was unable to see > > > > the new server. So I started playing around C:\Program Files > > > > \CruiseControl.NET\webdashboard\dashboard.config but I realized > > > > whatever I did to this file nothing got updated in the web > > > pagehttp://explorer/ccnet/ViewFarmReport.aspx. I even tried restarting > CC > > > > and ISS. Even renaming the file didn't make any difference in the > > > > report, it seems I'm missing something important, can you please help > > > > me? > > > > > > Thanks very much > > > > Saran > > > > > > On Jul 31, 2:13 am, Ruben Willems <[email protected]> wrote: > > > > > > > Hi > > > > > > > 90% chance that this is a network / firewall issue : > > > > > straight from the FAQ : > > > > > > > - First check that the used port is correct, standard it is > 21234. > > > If you > > > > > never changed this, or it's the first time you see this number, > this > > > setting > > > > > will probably be correct. > > > > > You can find the value in the exe.config files > (CCNet.exe.config, > > > > > CCService.exe.config) in the > > > system.runtime.remoting/application/channels > > > > > part. > > > > > - Next, check the firewall on the server. You can do this by > running > > > the > > > > > following command in a prompt : *netsh firewall show > portopening* > > > > > If you get an empty list, no firewall is on, if you see a list, > > > check > > > > > that there is a line containing the correct port : standard it > is > > > 21234 > > > > > To open the port, run the following command : *netsh firewall > add > > > > > portopening TCP 21234 CCNET* > > > > > > > check firewall settings on both servers > > > > > > > with kind regards > > > > > Ruben Willems > > > > > > > On Thu, Jul 30, 2009 at 11:18 PM, Saran <[email protected]> > wrote: > > > > > > > > Hi, > > > > > > > > I recently installed Cruisecontrol.NET on a new machine and > started > > > > > > the same (I haven't setup any projects yet). I added the new > server > > > > > > details in webdashboard/dashboard.config on the machine where > CC.NET > > > > > > and webdashboard are working fine. > > > > > > > > <servers> > > > > > > <server name="oldmachine" url="tcp://localhost:21234/ > > > > > > CruiseManager.rem" /> #old line > > > > > > <server name="newmachine" url="tcp://newmachine:21234/ > > > > > > CruiseManager.rem" /> #new line > > > > > > </servers> > > > > > > > > Even after restarting IIS I'm unable to see the new server. > > > > > > > > I'm not sure what I might be doing wrong. > > > > > > > > Thanks in advance for your help > > > > > > Saran >
