Could you send us the details of the crash events? Or even better a crash dump if possible.
Did you enable ModSecurity in your web.config file? If not, then there should be no crash for sure. We had an issue with a crash when the ModSecurity configuration file with rules was missing (in most cases you would put it in the same folder where web.config is), but it was fixed.
> Date: Thu, 25 Oct 2012 15:57:09 +0200 > From: Jan van Valen firstname.lastname@example.org > Subject: [Mod-security-developers] WS2008 R2 SP1 (64bit) IIS 7.5 > ModSecurityiis.dll crash (2.7.0) > To: "email@example.com" > <firstname.lastname@example.org> > Message-ID: > <F0F767A6EAC7B241BB427843808610AD63A9E76995@tilsrv04.corp.medicinfo.nl> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > > Trying to get ModSecurity 2.7.0 to work on a windows server 2008 R2 SP1 with IIS7.5 to no avail. > This is what I tried so far: > > - Installer 2.7.0.msi > > - Downloaded the debug version followed the reference manual: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#wiki-Installation_for_Microsoft_IIS > > - Copied and registered everything in either System32 (32bit) and SysWOW64 (64bit) > > - Did a DepencyWalker which only mentioned IEFRAME.DLL for which I read online that's almost always the case. > > - Reinstalled vcredist_x64 > > - Set the application pool to 'Enable 32-Bit Applications' > > All result in 'HTTP Error 503. The service is unavailable' and crash events for modsecurityiis.dll in the Application Event log. > > On http://blog.spiderlabs.com/2012/07/announcing-the-availability-of-modsecurity-extension-for-iis.html in the comments it states that 'you can add the modsecurity.conf file into the wwwroot'. > I'm a little confused about what that location should be. > > In my situation I have the default website removed. Created a website in d:\websites\website. > Where should I put the conf and the rules? )If that should solve my problem. > > What else can I do to make it work? > Thnx, > JamBo