[Date Prev][Date Next] [Chronological] [Thread] [Top]

# RE: win 2000 service problem

Code 21 means it was unable to startup the backends. Sounds like your
back-sql configuration is broken. Remember that when slapd runs as an NT
service, it changes its working directory to the directory where the slapd
executable resides. If you're using relative paths for certain things, or if
you rely on certain DLLs to be in your path, this needs to be taken into
account.

-- Howard Chu
Chief Architect, Symas Corp.       Director, Highland Sun
http://www.symas.com               http://highlandsun.com/hyc
Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of Rob Tice
> Sent: Sunday, March 02, 2003 1:11 AM
> To: 'openldap--bugs@openldap.org'
> Subject: win 2000 service problem
>
>
>
> This is a repost as I didn't get any feedback on the last
> submission :)
>
> I am running 2.1.13 with back-sql on windows 2000 (or trying to run
> depending upon how you look at it!).
>
> After building to include back-sql, slapd runs from the command line
> fine but not as a service. This would seem to be a bug as it
> worked as a
> service before the back-sql was included. The windows
> diagnostic for the
> service failure says it terminated with error code 21 when the service
> start fails.
>
> It also doesn't log to openldap.log when the debug define is set in
> portable.nt and the debug directive loglevel -1 is included in the
> slapd.conf. It does however log as expected when run with option -d -1
> from the command line.
>
> Any ideas
>
> Regards
>
> Rob Tice
> rob.tice@k-int.com
>
>
> ----------------------------------------------------------
>
>
>
>
> When I tried to build
>
> -----Original Message-----
> From: Pierangelo Masarati [mailto:ando@sys-net.it]
> Sent: 27 February 2003 10:40
> To: rob.tice@k-int.com
> Cc: openldap-software@openldap.org
> Subject: RE: Build problem (maybe)
>
>
> > Hi there and thanks for the response to my original message.
>
> I'm replying to the list because it may be of interest.
>
> suggested which has
> > the suggested fix to the structure initialisation which was causing
> > visual studio to complain. The build now fails on a standard build
> even
> > before I try and incorporate back-sql.
> >
> > The message is
> >
> > cache.c
> > fatal error C1083: Cannot open source file:
> > 'C:\development\openldap-2.1.13\libraries\libldap\cache.c': No such
> file
> > or directory
> >
> > and is thrown during the build of libldap.
> >
> > There is indeed no file cache.c and it is indeed referenced in the
> > libldap.dsp file configuration
> >
> > I have browsed CVS and there is no file cache.c in there
> either so it
> > doesn't appear to be just missing from my distribution.
> >
> > Is a new windows project file required for libldap?
> >
> > Any help would be appreciated.
>
> The problem has already been discussed (there is also an ITS,
> I think).  It has to do with the fact that cache code was
> trimmed from libldap.  Apparently it is still in your build
> stuff.  I assume you are building under windows, so I don't
> exactly know where you need to look; you need to eliminate
> all the dependencies on libraries/libldap/cache.c in your
> makefiles / MSVC projects.
>
> p.
>
> --
> Pierangelo Masarati
> mailto:pierangelo.masarati@sys-net.it
>
>
>
>
>
>