Posted by shambler on April 12, 2010 at 7:42am
Hi there
I'm running Drupal 6 on IIS7/php5.3 - I get the 500 error on /admin/build/modules 'save configuration' even though changes I've made are saved - I also get the same error when I select 'flush all caches' from the admin menu module (turns out I get a 403 when I flush the 'theme' cache - so that must be the problem - I am using a custom theme - a subtheme of blueprint which Ive created).
The latter problem suggests a permsissions error (i do not have direct access to the server) but I wondered if the first problem is something IIS7 specific?
Categories: 500 - Internal server error iis7 permissions?
Comments
Is this still happening?
I am experiencing the exact same problem on the exact same platform.
Where are your site's temp
Where are your site's temp files and file system directories pointing? admin/settings/file-system. Do these directories have appropriate permissions for the web server to write to them?
Are you running url_rewrite?
What is in your site's web.config file?
chicagomom on Twitter and d.o.
It would be nice ...
It would be nice ... if there was documentation of EXACTLY which accounts need what permission on what folders under IIS 6 and IIS 7 so that it was crystal clear what one has to do to make this work. It is random at present. You have to search on this site and the main site and the comments to documentation pages. It's incomplete, confusing and at times contradictory.
I would be happy to help write docs, but I don't know what the specs and instructions currently ARE.
File system
sites/default/files
Writeable as far as I know.
2.Temp is at
/sites/default/files\tmp
3.Yep we're running url_rewrite
I also get a 403 on /admin/build/modules/uninstall
thanks for your time!
Well it is something to so
Well it is something to so with clean URLs, on the dev version of the site I turned them off and everything is fine, I can access everything.
Re the web.config file, ours is the same, bar some additions, but those additions don't seem to be the problem when I've been dropping stuff in and out.
Do you need a separate rule for long URLs? I will update if I get a solution.
BTW
Doesn't work, we are using
Not sure if that has any effect.
The soluton. Well, what the
The soluton. Well, what the problem was...
I'm still getting the 500 error on /admin/build/modules but other admin pages that were giving me 403s were down to
<rule name="Protect files and directories from prying eyes" stopProcessing="true"><match url=".(engine|inc|info|install|module|profile|test|po|sh|.sql|postinst.1|theme|tpl(.php)?|xtmpl|svn-base)$|^(code-style.pl|Entries.|Repository|Root|Tag|Template|all-wcprops|entries|format)$" />
<action type="CustomResponse" statusCode="403" subStatusCode="0" statusReason="Forbidden" statusDescription="Access is forbidden." />
</rule>
in the webconfig file.
Please Help!
Hi,
I tried disabling the clearn URLs, but I keep getting the same problem.
I'm new at using drupal and I keep getting the same reoccuring problem with each new site I create.
Whenever I begin to get my site running (adding content with cck and views) and I return to save or enable the modules (essetially update them), I receive a "server error" stating that the website is in maintance or configured incorrectly.
I don't know what the problem is! Please help... :(
-Ally
To fix errors on module/uninstall, admin/by-module and others
Replace the code from the web.config above with:
<rule name="Protect files and directories from prying eyes" stopProcessing="true"><match url=".(engine|inc|info|install|module|profile|test|po|sh|.+sql|postinst.1|theme|tpl(.php)?|xtmpl|svn-base)$|^(code-style.pl|Entries.+|Repository|Root|Tag|Template|all-wcprops|entries|format)$" />
<action type="CustomResponse" statusCode="403" subStatusCode="0" statusReason="Forbidden" statusDescription="Access is forbidden." />
</rule>
Note: Replace "+" with asterisks - I can't figure out how to make asterisks (*) display inside a code block.
To fix 'flush all caches' error
I also get the same error when I select 'flush all caches' from the admin menu module
That's because you have the "
theme|" part in your rule.The same problem occurred on my site when I wanted to flush cache - then I removed the mentioned "
theme|" part from "web.config" file, and flushing theme registry already worked. There's also a Drupal-check for user permissions (if one can reach the given part of the site), so this doesn't cause any serious security risks you have to worry about after doing this.