I am getting this error on the .NET version of Zoom V6 running on a Win 2003 server:
I am using the .NET version in XML mode.Code:Server Error in '/NET_ROOT' Application. Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.] malloc(UInt32 ) +0 zoomSearch.setup1(zoomSearch* , zoomSearchSetup* zsSetup) +96 ZoomASPX.ASPXSearch.Render(HtmlTextWriter output) +886 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +25 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +121 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22 System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +199 System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +20 System.Web.UI.Page.Render(HtmlTextWriter writer) +26 System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +25 System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +121 System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2558 Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
The search engine works for some time after I reindex & reupload the search files, but eventually the error occurs. Resetting IIS temporarily fixes it.
First thing to do is make sure you are using the latest build of the .NET Server Control and the latest build of the Indexer.
You can get the latest .NET Server Control here:
Note that you need to uninstall the previous server control for it to install.
The latest Indexer can be downloaded from here:
Let us know if you still have this problem with the latest builds.
Wrensoft Web Software
Zoom Search Engine
I currently have the .NET control installed on the web server, and the Indexer installed on a remote machine. Does the Indexer need to be installed on the web server as well?
No. The indexer can be either on the server or another machine. Having it on the server does avoid the need to transfer the set of index files to the server however, and it will also make indexing faster.
I installed the latest .NET control (build 1013) and it doesn't work at all on my server! Gives the following error:
Code:Unable to load DLL 'msvcm90.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.DllNotFoundException: Unable to load DLL 'msvcm90.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %> or: 2) Add the following section to the configuration file of your application: <configuration> <system.web> <compilation debug="true"/> </system.web> </configuration> Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [DllNotFoundException: Unable to load DLL 'msvcm90.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)] <CrtImplementationDetails>.ThrowModuleLoadException(String , Exception ) +0 <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* ) +112 .cctor() +46 [TypeInitializationException: The type initializer for '<Module>' threw an exception.] ASP.search_search_aspx.__BuildControlTree(search_search_aspx __ctrl) +0 ASP.search_search_aspx.FrameworkInitialize() +21 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +38 System.Web.UI.Page.ProcessRequest() +86 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18 System.Web.UI.Page.ProcessRequest(HttpContext context) +49 ASP.search_search_aspx.ProcessRequest(HttpContext context) +4 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Is there a place I can download the previous build of the .NET control, as it worked despite an occasional crash? I can't get the latest build to work at all, on any machine.
This was an unexpected bug caused by an issue in the Visual Studio 2008 SP1 update. We updated our development environment just recently, thinking it was fairly safe to do so but were hit with a surprise from Microsoft (merge module .msm policy files appear to have incorrect dependencies, resulting in the required policy files being excluded from the installation package).
We have now updated the ASP.NET Server Control and it should be fixed. You can download it here:
If you still have trouble with the new build, please let us know.
Wrensoft Web Software
Zoom Search Engine
Thanks - the new build works.
However over the weekend I switched the site to use the CGI engine instead of the broken .NET control. Are there any performance or other benefits for using the .NET version over the CGI version? Would you reccomend one over another for a .NET site running on Win2003/IIS?
The CGI is actually slightly faster than the .NET control.
The .NET control is better for servers that can't run a CGI due to lack of permissions or the like. Some .NET developers also like to keep everything in .NET.
But if the CGI is installed and working. I wouldn't suggest changing to .NET.
Thanks, I will stick with CGI then. One minor issue I noticed with CGI is there are several identical application errors in the event log every time the site is reindexed and files are uploaded:
Is this anything to be concerned about?Code:Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 4/20/2009 Time: 1:59:25 PM User: N/A Computer: WTRSCP19874 Description: Faulting application search.cgi, version 0.0.0.0, faulting module search.cgi, version 0.0.0.0, fault address 0x00005376. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 73 65 61 ure sea 0018: 72 63 68 2e 63 67 69 20 rch.cgi 0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0 0028: 69 6e 20 73 65 61 72 63 in searc 0030: 68 2e 63 67 69 20 30 2e h.cgi 0. 0038: 30 2e 30 2e 30 20 61 74 0.0.0 at 0040: 20 6f 66 66 73 65 74 20 offset 0048: 30 30 30 30 35 33 37 36 00005376