give authenticated user write/modify/read permission on the wwwroot holder and the same permission to network resource account
samboll:
Thanx for the response.
My WordPress files are located here:
Desktop/websites/wordpress-2.9.1/wordpress
I have given folder “wordpress” READ/WRITE/MODIFY permissions for:
IIS_IUSRS
Users
Authenticated Users
Network Service
I am still having the same problem with the same error.
–w.
hmmm…that error is usually related to permissions
I’m not really a windows guy, though
maybe try permissions one or 2 levels up?
Hope someone can give better help
I would first check and see that php and MySQL are working.
Create a file in the root of the wordpress directory (you said it is : Desktop/websites/wordpress-2.9.1/wordpress) and save it as phpinfo.php
It should have the following in it
<?php phpinfo(); ?>
Now browse to http://localhost:80/phpinfo.php
Look at the results you should see the php version at the top along with all the settings. Look for a section titled: Mysql and/or mysqli
If the phpinfo.php file errors out or displays the text, you have an issue with the php install.
If there is no mysql or mysqli section there is an issue with the mysql extension. Based on your first comment, this is the most likely culprit.
If the phpinfo.php returns good results and has a mysql/mysqli stanza, The issue could be a known bug with IPv6 and php 5.3.1 on IIS7/7.5
Look at your hosts file. It may have the following:
127.0.0.1 localhost
::1 localhost
If it does change it to:
127.0.0.1 localhost
#::1 localhost
This will comment out IP v6 for localhost and allow php 5.3.1 and mysql to work on iis 7/7.5
Give these a try and let us know how it turns out.
kcristiano:
You were right. BOTH the IPv4 and IPv6 lines were commented out in my hosts file. I uncommented the IPv4 line and WP did get installed. I checked the database and the tables were created.
But now when I clicked on Login to go here: http://localhost/wp-login.php
it gives me a similar 500.19 server error.
Please help.
–w.
Ok: Now it gets a bit more complicated. The error you mention is 500.19:
500.19 – Server error: Data for this file is configured improperly.The requested page cannot be accessed because of a configuration error.
How did you set up php? was it by hand or with the automatic installer? This error indicates that the php is not being handled correctly.
This article http://learn.iis.net/page.aspx/246/using-fastcgi-to-host-php-applications-on-iis-70/ walks you through the process. This article was written for IIS 7, but will apply to IIS 7.5 as well.
In addition, if your server is 64 bit, you should set ‘enable 32 bit applications’ to true in your application pools settings.
kcristiano:
Thanx for the suggestions.
I had a file called web.config that IIS assumed was an ASP.Net config file, so it was having problems. I renamed it to web_old.config and now WP seems to be loading. It was in my wordpress folder.
BUT, now I cannot seem to view the actual post or the actual blog.
It just gives me a directory listing.
But I can do all administration tasks via the web-panel including edit posts and everything else. But when I click on link it goes to the list of files. Here is the address it is going to:
http://localhost/?p=1
Any ideas?
Thank you.
–w.
If it is just giving you a directory listing it is probable that index.php is not defined as one of the default documents. Look at the site in IIS Manager and see what the default documents are set to. I move index.php to the top.
Also keep in mind that web.config is the IIS equivilant of .htaccess any changes to this web sites config that differ from the server defaults will be saved here. For wp, rewrite rules (pretty permalinks) are the most common.
You are an officer and a gentleman.
If a woman: An officer and a lady.
the default document was not set, even though I can swear I had set it.
Thank you so much.
–w.
Hi,
I’d like to thank you guys for posting this, I’ve been up all night fixing one thing after another with my PHP and MySQL set up on the Windows 2008 and IIS 7.5 to run WordPress out of it, and this final piece of the puzzle was this issue with the host file, which is very obscure. I’m rebooting now after changing it and I’m hoping to see it resolved after a long night, now afternoon.
I wanted to just inform wpfiend that the reason your Default Documents configuration was changed was that you deleted your Web.Config file, don’t delete that file, it’s the local configuration of your web folder and web site if it’s in the root directory. What you did was delete it and then start a new one by setting the Default Document directive in the IIS GUI admin. If you still can, you should get that web.config file back out of your Recycle Bin and restore it back to where it was. If there were any settings on it that were important you would need them back. At least back the file up before doing any changes or deleting it, so you can easily restore it if something goes wrong.
When you edit configurations in the IIS Admin, what you are actually doing is writing directives to the Web.config file – so if you delete that file you deleted all your configurations and the site falls back to the defaults in the app.config for the whole server. When you started with a new directive for your Default Documents, you wrote a new Web.config file with just that one directive. As a rule of thumb, don’t do drastic things like deleting files you don’t know about, just move them and see what happens. That way you can always move them back.
The reason things still worked in your wp-admin folder was that there’s a seperate web.config in that folder that wasn’t effected by the deletion of the one in the root folder, because the closer one in the hierarchy overrides those above it.
Lastly, the Web.config file is not strictly for Asp.Net use, it effects the whole web site as it is the Settings holder for the IIS system, now after IIS 6, like the metafile used to be for IIS 6. In other words all the settings you set in the IIS Admin GUI are stored as text in the Web.config, so understand that and don’t delete it. If you need to change something copy the Web.Config file to another folder and see what changes yu need to bmake. If your changes have no effect or aren’t a fix. Overwrite your Web.Config file with the one you moved away and you’re back to where you were before you started making the changes.
Yup, just restarted my server and finally loaded up the WordPress install and got everything going. Hurray !!
It’s really nice on PHP 5.3.1 optimized fro Windows and the new WinCache PHP Extension, runs great. That set up caused the headaches getting all those latest and greatest things installed and configured right, but it’s worth it, it runs smoothe.
I’m getting the server 500 error due to the admin re-writing the web.config and duping up a load of rewrite rules. When it updates this file, it then brings down the php app in that directory and oddly doesn’t log anything either.
anyone experienced this and found a workaround?
