[cvsnt] Re: Crash updating to 2.0.12

Tony Hoyle tmh at nodomain.org
Thu Nov 27 18:33:00 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

On Thu, 27 Nov 2003 18:16:39 +0000 (UTC), gagenellina at softlab.com.ar
(Gabriel Genellina) wrote:

>I tried to update from CVSNT 2.0.11 to 2.0.12. Server is Windows NT.
>Using the Windows installer it crashed while "Generating default
>certificates" at address 0x77f7ce4c trying to write memory at 0x00000010
>The installer continued anyway and said it was OK. But I could not connect
>from the client:
>CVS95 update: SSL conneciton failed: error:140770FC:SSL
>routines:SSL23_GET_SERVER_HELLO:unknown protocol

You probably have an old openssl library hanging around somewhere.
Delete any copies of ssleay32.dll and libeay32.dll that aren't shipped
with cvsnt 2.0.12 (best to uninstall cvsnt, delete any instances of
those DLLs, then reinstall cvsnt).

Unfortunateley openssl isn't portable across versions, so you have to
be careful not to put it in system32 or anywhere like that.

>But it still crashes when a client issues a command including -z option.
>And I'm still unable to generate a crash dump (fails with error 50).

That still sounds like AV has mucked the system up somehow.  At this
point I'd be tempted to wipe the OS and reinstall.  If that isn't
possible, maybe install on a different server.

Don't use cvs95 if possible as it's not really possible to test
reports involving it.


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook