[cvsnt] CVSNT Lock Service Not Working

[Bo Berglund]

If you previously have installed CVSNT on that same machine using the
InnoSetup installer that was distributed with WinCvs or Tortoise or in
fact CVSNT 2.0.58 and earlier, then you will have all kinds of trouble
when you use the latest MSI installer from Mach Hare.

You actually have to UNINSTALL CVSNT first completely and restart your
PC.
Check that there are no cvs services running.
Also check that noone is listening on ports 2401 and 2402.
(use "netstat -a -p tcp" in a command window to list all TCP ports and
look for these ports among the LISTENING group.
If you find any of these then you have to fix that first.

Then install again using the CVSNT MSI installer and I bet that all will
work fine.


Best regards,

Bo Berglund


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of David Somers
Sent: den 30 augusti 2006 12:17
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] CVSNT Lock Service Not Working

Bhushan Kalse wrote:

> Hi All,
> 
> I am trying to setup CVSNT (2.5.03) on Windows 2000 Machine and seems
> like Win 2K does not like CVSNT Lock Service.

There shouldn't be a problem with cvslock and Win2K

> I am not able to start Lock Service on the same machine, where as it
> (CVSNT Lock service) was working fine on the other machine with Win XP
> that I have tried before.

What error message do you get? What is in the Event Log?

[snip] 
> Installed Winsock protocols:
> 1035: CA ISafe LSP over [MSAFD Tcpip [TCP/IP]]
> 1036: CA ISafe LSP over [MSAFD Tcpip [UDP/IP]]

You have some anti-virus/firewall software running... so make sure you
allow
cvslock and cvs to connect to their ports... disable virus scanning in
your
repository directories (or the performance will be awful).

> c:\> cvslock -test
> 
> CVSLock 2.5.03 (Scorpio) Build 2260 (Mar  3 2006) starting in test
> mode.
> Initialising socket...
> Starting lock server on port 2402/tcp...
> Couldn't bind listening socket... Only one usage of each socket
address
> (protocol/network address/port) is normally permitted.

It can't bind to the port, which means something else (probably cvslock)
is
already using that port. Are you sure the cvslock service hasn't already
started?

David
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt