By ZanderZ on

Using:
- Win 7 32bit
- php 5.6.10
- mySQLserver 5.6.25.0
- Drupal 7.38
- IIS 6.1 SP1

This image shows that I've completed the setup successfully:
Drupal install completed

When I click "Visit your new site". It sends me to the Drupal directory.
If I click index.php in the Drupal folder, the page is displayed correctly but If i click
on anything on this page, it sends me back to the Drupal directory.

There must be a reference or parameter missing somewhere.
I have analysed more forum posts and Drupal guides than I care to mention. I can't find the solution.

It keeps sending me to this page:
Drupal folder

Please help :'(...

I have fixed many issues during 2 full days of learning to install Drupal;
A few notes for other new people:
- web.config in the folder drupal-7.38 is not named correctly and should be web.config.XML
- do not change the default.settings.php to settings.php before running the Drupal install.

⋅ Categories: Drupal 7.x

Comments

ZanderZ’s picture

ZanderZ commented

I have fixed this by adding "default page" though IIS Manager, using index.php.
suddenly, everything works...

teachyourselfdrupal’s picture

teachyourselfdrupal commented

I have never used IIS, only Apache. So, I'm having to guess at things.

As far as your issue with the directory showing up, it seems that IIS needed to know what to serve when visiting a directory. That's what the "default page" configuration must be doing. In Apache you use the DirectoryIndex directive. Since it was previously showing the directory structure, you must have something similar to Options Indexes (or Options -Indexes to prevent the directory from being shown).

You should not need to change web.config to web.config.XML. I've installed Drupal probably hundreds of times and have never changed this.

ZanderZ’s picture

ZanderZ commented

Thanks for your reply.
I can assure you the install will not complete without renaming the web.config to .XML.

I got the error "HTTP Error 500.19 - internal Server Error, the requested page cannot be accessed because the related configuration data for the page is invalid."

Which pointed me towards the XML, after renaming, it was fixed.
It must be an IIS issue.