Hi Bill,

Our configuration also uses port 21234 and I don't need to add this to
the url so i don't think that's your problem.

It's starting to smell like an IIS problem to me - if you have access
to IIS then check that the web dashboard is wired up correctly and
that it can see the \webdashboard folder.

Hope this helps
Dave

On Apr 21, 12:32 pm, Bill Campbell <[email protected]> wrote:
> Hi Dave,
>
> Thanks for getting back to me so quickly. The Web URL for the dashboard was
> an excellent thing to try. I am getting this error:
>
> Server Name Url Message
> 55d3s81 tcp://55d3s81/CruiseManager.rem Tcp channel url must have a port
> number: tcp://55d3s81/CruiseManager.rem
>
> So I looked in ccnet.config and found the port number that tcp is using
> which is 21234. So I changed my url to use that port
>
> http://localhost:21234/ccnet- and now I get this error.
>
> .NET          System.Runtime.Remoting.RemotingException: Tcp channel
> protocol violation: expecting preamble. at
> System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamb
> le() at
> System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOper
> ation(UInt16& operation) at
> System.Runtime.Remoting.Channels.Tcp.TcpServerSocketHandler.ReadHeaders(
> ) at
> System.Runtime.Remoting.Channels.Tcp.TcpServerTransportSink.ServiceReque
> st(Object state) at
> System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow()
>
> Here is my ccservice.exe.config section for the tcp port:
>
>        <!-- Defines the port and protocol that the ccnet server will
> use to service remote requests -->
>        <system.runtime.remoting>
>                <application>
>                        <channels>
>                                <channel ref="tcp" port="21234">
>                                        <serverProviders>
>                                                <formatter ref="binary"
> typeFilterLevel="Full"/>
>                                        </serverProviders>
>                                </channel>
>                        </channels>
>                </application>
>        </system.runtime.remoting>
>
> Since this just stopped working yesterday morning, I'm wondering if perhaps
> IT rolled out some MS patches that tightens security or something? I never
> had to use a port number on the URL connection before. Have you ever seen
> this error? Without CCTray running it's rather like going to work without
> your cell phone :)
>
> thanks in advance!
> Bill Campbell
>
> On Tue, Apr 21, 2009 at 3:41 AM, Dave Carson <[email protected]> wrote:
>
> > I've never had a problem with CCTray either - so I'm shooting in the
> > dark here.
>
> > The first thing i would chceck would be that I could access the Web
> > Dashboard URL. If not then I'd probably restart the CCservice and try
> > again. If you can access the Web Dashboard then are you sure that you
> > have the correct URL in the settings for CCTray (daft question I
> > know).
>
> > Have you looked in the log file to see if anything I being thrown up
> > in there?
>
> > Dave
>
> > On Apr 20, 8:13 pm, Bill <[email protected]> wrote:
> > > Hi,
>
> > > Sorry if this is a repeat message - I didn't see it get posted to the
> > > group.
>
> > > We have been using CCNet for about a year and today our CCTray turned
> > > Gray with the message "Error: Project 'MyProjectName' was not found on
> > > server. This is the case for the entire team. I tried restarting ccnet
> > > service and then restarting IIS with no luck. When I try to map the
> > > CCTray to the project again, it doesn't give me any choices for
> > > projects under my url. Weird. I can do a CheckOut on the project from
> > > SVN just fine.It was working fine as early as this morning. It looks
> > > like the last build check was made on the build machine just a couple
> > > of minutes ago. It's just like no one can connect through CCTray.
>
> > > Any thoughts of what else I might check would be greatly appreciated.
> > > I've been using ccnet for a couple years and never have seen this one.
>
> > > thanks in advance!

Reply via email to