I have encountered an issue with LAPI/IIS while building an ActiveX DLL that calls the Search API.EnvironmentIIS 5.0 (Personal Web Server)VB 6 ActiveX Dll (invoked via an ASP)LAPI 9.1BackgroundCustomer launches searches using ASPs. I have created an ActiveX DLL that is invoked within an ASP that makes calls on LAPI functions to take advantage of Livelink Search/Index for the retrieval of results.SymptomsWhen a search is invoked the first time, results are returned as expected. Thereafter, all searches result in thedisplay of an IIS error message. Stopping and restarting the WWW service clears the problem - but only for the next single access.The ErrorHTTP 500.100 - Internal Server Error - ASP errorError Type:Microsoft VBScript runtime (0x800A01FB)An exception occurred: 'MyObjectName'About Error 0x800A01FBMS says: "This problem occurs because the session variables in Internet Information Server (IIS) 5.0 are stored in the Global Interface Table (GIT), and this causes an access violation with an open recordset when it is stored in a session variable." Microsoft has confirmed this tobe a problem most commonly found in IIS 5.0 with ActiveX Data Objects (ADO), versions 2.1 , 2.5. For more info refer to..
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262681 http://support.microsoft.com/default.aspx?scid=kb;en-us;Q249175 Findings1. When the search is issued via the same code invoked from an Windows EXE file, search consistently returns without any error indicating that the LAPI search functions works.2. The error only occurs when the search is issued via the Web interface using (ActiveX) DLL code. On the second and subsequent search attempts the failure occurs when 'LL_ValueSetLength' function is called. This function sets the length of an array that is used to format one of the arguments passed into the main search function (LL_ApplyQuery). When invoked, the LL_ValueSetLength function does not return at all and IIS immediately returns the error.3. LAPI provides no alternative ways of calling the required functionalityHas anyone seen this before? Any ideas how to get round it?
