"An unexpected error has occurred while trying to force build. The method or operation is not implemented"

[HowitZer]

I get a message box saying "An unexpected error has occurred while
trying to force build. The method or operation is not implemented"
when forcing a build through cctray.

I'm using cctray 1.6 with ccnet 1.6. I downloaded cctray from the
download link on the web dashboard.

The transport method used for the server in question is http. The
server link looks like this "http://servername/ccnet".

Everything else works pretty well with cctray.

What has to be done to get force builds to work in cctray?

[Ruben Willems]

Hi

set the communication to remoting, not via the dashboard.
that does not seem to work :-(

with kind regards
Ruben Willems

[Sandeep Reddy Gurram]

Hi,

Check and see in the dashboard config if backwardscompatibility is set to false, if not set it to false and give it a try.

<server name="linuxBuilder" url="tcp://Metroplex:21234/CruiseManager.rem" allowForceBuild="true" allowStartStopBuild="true" backwardsCompatible="false" />

Regards,
Sandeep

[HowitZer]

I tried the remoting method and supplied the hostname.

CCtray says "validating..." and comes back with

"Failed to connect to server: A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond xxx.xx.xx.xx:21234"

I tried giving it the ip instead of the hostname and received the same
message.

The computer I'm trying to connect to is on the local network. I can
remote desktop into it and view it on the network.The dashboard there
works fine.

Any ideas?

On Sep 23, 1:02 am, Ruben Willems <ruben.will...@gmail.com> wrote:
> Hi
>
> set the communication to remoting, not via the dashboard.
> that does not seem to work :-(
>
> with kind regards
> Ruben Willems
>

[HowitZer]

It's already set to false.

On Sep 23, 1:24 am, Sandeep Reddy Gurram <sandeep15...@gmail.com>
wrote:

> Hi,
>
> Check and see in the dashboard config if backwardscompatibility is set to
> false, if not set it to false and give it a try.
>
> <server name="linuxBuilder"
> url="tcp://Metroplex:21234/CruiseManager.rem" allowForceBuild="true"
> allowStartStopBuild="true" backwardsCompatible="false" />
>
> Regards,
> Sandeep

> On Sep 23, 2011 12:02 AM, "Ruben Willems" <ruben.will...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi
>
> > set the communication to remoting, not via the dashboard.
> > that does not seem to work :-(
>
> > with kind regards
> > Ruben Willems
>

[Ruben Willems]

Hi

things to check :
° double check that CCNet is running on that server
    stop and start the service to see that there is not coming an error message
° try to telnet to that pc with port 21234
     ping and rdp use different ports, and a firewall can block the port of ccnet

with kind regards
Ruben Willems

[HowitZer]

It was the firewall on the server. I enabled port 21234 and now I can
force builds from my dev machine.

I have a bunch of Java cc projects that I'm connected to via cctray
using the http method. For example

http://server:8080/dashboard/cctray.xml

I get the not implemented error message when forcing one of these from
cctray. Any thoughts on how to make those work too?

On Sep 25, 12:25 am, Ruben Willems <ruben.will...@gmail.com> wrote:
> Hi
>

> things to check :
> ° double check that CCNet is running on that server
>     stop and start the service to see that there is not coming an error
> message
> ° try to telnet to that pc with port 21234
>      ping and rdp use different ports, and a firewall can block the port of
> ccnet
>
> with kind regards
> Ruben Willems
>

[Ruben Willems]

Hi

for CCNet it's best that you use .Net remoting.
as the error says, the HTTP communication is not implemented.

you can set the communication when you add the build server

with kind regards
Ruben Willems

[Katherine Moss]

Isn’t .net remoting deprecated in favor of WCF though in .net framework 4.0 and above?

[Ruben Willems]

Hi

true, maybe we can foresee wcf-communication or so in the next version(s).
you may open a ticket for it at :  http://www.cruisecontrolnet.org/projects/ccnet/issues

Only question remains : do we still need to support remoting ?
I'm not in favor of supporting all kinds of communication methods

if you can configure wcf to use remoting, fine by me,
the communication is WCF, only the configuration of WCF is altered, this does not change the code.

but supporting code wise X communication protocols is asking for trouble.

just my opinion, other users / devs may have other thoughts.
I'm open to suggestions :-D

with kind regards
Ruben Willems

[Katherine Moss]

I don’t think that’s possible.  WCF and remoting are two different technologies that do the same.  So to speak, .net remoting has morphed into the richer feature set of WCF.  I’m here for when I begin to use Cruise Control.net.  I am hear to learn for when the time comes.  And by the way, have you ever recommended the CCNet configuration tool (or maybe it’s configurator or something like that), on CodePlex?  I ask because that is a Graphical user interface that allows for most of the configurations to be done through rather than having everybody type all of the XMl configurations by hand.  I do not use it as of yet, but when my coding skills get better (I’m getting there), I am going to turn my server at home into a build server among other functions.  (web, email, database, and possible chat if I can swing it).  But yes, I think you should start supporting WCF and drop support for .net remoting.  That way if you quit supporting it, folks will make the leap to WCF and start using what is recommended by microsoft.