Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm assuming you're using PHP 5.2.6 (latest version). I'm also assuming your using ISAPI from the directions in your link.</p> <p>There seem to be a lot of bug reports for PHP on IIS with access violations.</p> <p><a href="http://bugs.php.net/bug.php?id=43303" rel="nofollow noreferrer">Here</a> and <a href="http://bugs.php.net/bug.php?id=44869" rel="nofollow noreferrer">here</a> or a <a href="http://bugs.php.net/search.php?cmd=display&amp;status=&amp;search_for=IIS+access+violation&amp;php_os=&amp;boolean=1&amp;author_email=&amp;bug_age=0&amp;by=&amp;order_by=&amp;direction=&amp;phpver=&amp;limit=30&amp;assign=&amp;reorder_by=id" rel="nofollow noreferrer">list</a></p> <p>So far the only suggestion I've found is to try FastCGI instead of ISAPI.</p> <p>I've never had to mess with debugging PHP itself, my own scripts of cource, but not PHP. There are instructions for <a href="http://bugs.php.net/bugs-generating-backtrace-win32.php" rel="nofollow noreferrer">generating a backtrace</a> and some <a href="http://us3.php.net/manual/en/debugger.php" rel="nofollow noreferrer">general debugging info</a>.</p> <p>Edit -- After reading viceBerg's answer I remembered another possible cause was non-thread safe PHP extensions and IIS not liking each other. It might be worth it to disable them all and enable them one at a time but it's only really useful if you can get a script to cause that error consistently.</p> <p>Without a consistent, reproducible error this will be very hard to debug.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload