Instalation problem - IIS related?

[abakus]

Hi everyone,

I am using IIS on W2k3 Server Web Edition, PHP 5.0.3 and MySQL 5.0.45.

I followed the installation manual but everything crashes just after filling the install page. I get an error message:

Warning: fopen(../config.php) [function.fopen]: failed to open stream: Permission denied in C:\www\www.abc.com\wb\install\save.php on line 314

Warning: Cannot modify header information - headers already sent by (output started at C:\www\www.abc.com\wb\install\save.php:314) in C:\www\www.abc.com\wb\install\save.php on line 80

Of course every requirement in install page is marked green.
In php.ini I have allow_url_fopen = On
It is not web client related problem, I tested it in IE7 and also in freshly installed FF2.0.0.6

Any idea?

[doc]

Hello,

it may be that you will never get WebsiteBaker running on IIS servers. Serach the forum for IIS. WB was developed on Unix using Apache webserver and never tested on IIS. See http://start.websitebaker.org/en/requirements.html for details.

Try a forum search, there are tons of posts dealing with problems related to IIS servers. Some people posted solutions for some of the errors, so give it a try.

Good luck
Christian

[abakus]

After hours of desperate efforts I gave up. 

As I cannost stop using IIS on my webserver I downloaded xampp and installed it on another virtual wxp machine (virtual machines are just cool, I love it  - of course if you have enough OS licences).

Everything works fine but it uses another public IP address which is something I don't like. But WB is really fine.

btw: the problems with IIS are in my opinion caused by unsufficent development from wb's side - drupal works with no problem with IIS (but I don't like it).
I understand the reason, I am not complaining, just commenting.
I just don't understand why it's webserver-related problem while php and mysql are working well.  I know, I am not alone

[doc]

Hello,

as mentioned before, some people here in the forum managed to get WB working on IIS, but I am sure it was a real pain. Some of the problems were related to the IIS settings.

Regards Christian