Ok. I cannot do anything about Windows (sorry for that). Then, you suggest that I should try Cyrus SASL 2.1.23 and see if it works fine?
Cheers.
Event Log Extract ---------------------
Description: Faulting application slapd.exe, version 0.0.0.0, time stamp 0x4e21b21f, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x00066796, process id 0x12a0, application start time 0x01cc4ab48e961035. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-07-25T10:29:22.000Z" /> <EventRecordID>47013</EventRecordID> <Channel>Application</Channel> <Security /> </System> <EventData> <Data>slapd.exe</Data> <Data>0.0.0.0</Data> <Data>4e21b21f</Data> <Data>ntdll.dll</Data> <Data>6.0.6002.18005</Data> <Data>49e03821</Data> <Data>c0000005</Data> <Data>00066796</Data> <Data>12a0</Data> <Data>01cc4ab48e961035</Data> </EventData> </Event>
Date: Mon, 1 Aug 2011 10:05:07 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com CC: openldap-technical@openldap.org Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception
On 01/08/11 15:50 +0100, Sergio NNX wrote:
I also did what you suggest: sasldb_path in /etc/slapd.conf and still the same issue. Apparently, i'm not alone with this problem:
http://www.openldap.org/lists/openldap-technical/201008/msg00094.htmlThat problem was resolved, in my test environment, by specifying a sasl-auxprops setting in slapd.conf, which you seem to have already done. In theory it should work. The two wild cards in your scenario (from my perspective) are Windows, and 2.1.24rc1.
However, I'll defer to Howard's opinion on possible thread re-entrancy problems.
-- Dan White