Hello, Trevor, There is a 3.1.0 rc2 version of the cosignmodule which addresses potential segfaulting issues with the cosignmodule. You can download it from here: <http://sourceforge.net/projects/cosign/files/cosign-windows-dev/CosignModule3.1.0rc2/>
Jarod On Jun 9, 2011, at 1:05 PM, Flick, Trevor wrote: > Dear Cosign Discussion List Members: > > I am using Cosign module 3.0.3 on a site in IIS 7 on Windows Server 2008 > 64-bit. After installing the module, the application pool for the site on > server has automatically disabled itself three times because the > CosignModule.dll is faulting. > > For all three times this has happened, I see five entries for Application > Errors in the Application log in Event Viewer that say this: > > Faulting application w3wp.exe, version 7.0.6002.18005, time stamp 0x49e03238, > faulting module CosignModule.dll, version 0.0.0.0, time stamp 0x4c62cc43, > exception code 0xc0000417, fault offset 0x000000000001cb54, process id 0xbd4, > application start time 0x01cc24b3d862b78c. > > All of these errors makes the application pool automatically disable itself. > If I restart the application pool or restart the server, then everything > appears to be working normally and there aren’t any errors. > > So far, the next incident doesn’t occur until about a few days after the last > incident. The second time this happened was 6 days after the first, and the > third incident was 4 days after the second incident. > > I noticed something while looking the in the System log. A service called > WinHTTP Web Proxy Auto-Discovery entered a running state at the time that the > errors start appearing and a few seconds before the application pool disables > itself. This has occurred for all 3 of the incidents so far. I did disable it > yesterday, since I don’t use that service on the server. I don’t know if that > service could have been causing problems with the Cosign Module. I haven’t > experienced another incident since Monday, June 6. > > This is the first time that I have installed the Cosign Module, and I am > still learning IIS. If there is any other information that I should provide, > let me know. > > I did try and install the IISCosign 3.0.0 ISAPI filter before installing the > module. I did remove the ISAPI filter from IIS before all of this started > happening. Could that have something to do with what I am experiencing? > > Has anyone experienced this issue? Does anyone know have any ideas for what I > should do? > > Sincerely, > > Trevor Flick > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev_______________________________________________ > Cosign-discuss mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/cosign-discuss ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
