RE: FW: Subversion 1.3.2 Win32 binaries -Apache mod_dav_svn.so module load error message

From: Daniell, Casey B <Casey_Daniell_at_reyrey.com>
Date: 2006-06-27 19:47:58 CEST

You are probably missing the Subversion binaries, they need to be
available to Apache. You may try a few things to accomplish this (going
off the top of my head)

1. Copy all SVN DLLs to the apache/bin directory
2. Copy all SVN DLLs to the apache/modules directory
3. Add SVN/bin to the PATH

If none of those options work, try using the dependency walker too
mentioned in docs. That is ultimately what I had to do to find the
missing, or incorrect version, of a particular DLL (Ignore msjava.dll
missing errors).

Also note, the above is the order to try things in, not necessarily the
steps you should perform to accomplish your task.

Casey

________________________________

From: Bill Bacon [mailto:bill.bacon@dowerinc.com]
Sent: Tuesday, June 27, 2006 9:26 AM
To: users@subversion.tigris.org
Subject: FW: Subversion 1.3.2 Win32 binaries -Apache mod_dav_svn.so
module load error message
Importance: High

I was told to forward this problem to the users list..

Problem:

I am using your June 2, 2006 Subversion 1.3.2 Win32 binaries with an
Apache 2.0.58 server on my Win2K server as a service.

I get the following module load error after configuring Apache:

/***********************************************************************
**********************************

C:\Program Files\Apache Group\Apache2\bin>apache -k start

Syntax error on line 173 of C:/Program Files/Apache
Group/Apache2/conf/httpd.conf:

Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_dav_svn.so
into server:

The specified module could not be found.

/***********************************************************************
*******************************

I copied the mod_dav_svn.so into the Apache modules folder per the
TortoiseSVN_en.pdf instructions provided (section 3.1.3 step 3). The
prior modules in the httpd.conf list apparently loaded and I verified
subject file was in the modules folder. It has a 6/2/2006 date stamp.

Any ideas why this module will not load? Work-arounds? The Apache was
running before I restarted it after configuring.

Regard,

Bill Bacon

678-560-4403