CGI Error after IIS Installation. No resolution. Anyone with success PLEASE HELP!
Page: 1, 2
Recent posts in this topic
Pro
Any resolution to this issue. I have the same problem. Sits at 'public/index.php/login?re_route=homepage' -- I see that your link works now:) How did you get this fixed? Any help eternally appreciated.
Pro sflowers:Any resolution to this issue. I have the same problem. Sits at 'public/index.php/login?re_route=homepage' -- I see that your link works now:) How did you get this fixed? Any help eternally appreciated.
No progress. We need to form a support group!
I'm stuck at the "blank white page" at the link you refer to above. With the silence on the thread, I've stopped researching it. After 6 hours or more digging through the php.ini and trying everything under the sun, I think the only solution is to use Apache. Unfortunately, that's not an option for me here at my company.
Keep me posted if you solve it... I'll do the same.
Staff
Oliver Maksimović
on Jan 25. 2008. 9:39 pm
I've been looking for a solution for this problem, too, but so far didn't get any results.
What about setting Apache to work on separate port, other than the one which IIS is using? IIS is using default port 80 (most likely), but you can have both servers running as long as they are using different ports.
That way you could have both IIS and Apache working at the same time, meaning that you would be able to use IIS as a web server for your company's regular work and having Apache on custom port - running activeCollab (http://youractivecollab:8080, for example).
What about setting Apache to work on separate port, other than the one which IIS is using? IIS is using default port 80 (most likely), but you can have both servers running as long as they are using different ports.
That way you could have both IIS and Apache working at the same time, meaning that you would be able to use IIS as a web server for your company's regular work and having Apache on custom port - running activeCollab (http://youractivecollab:8080, for example).
activeCollab team member, too ;)
Pro Oliver Maksimović:I've been looking for a solution for this problem, too, but so far didn't get any results.
What about setting Apache to work on separate port, other than the one which IIS is using? IIS is using default port 80 (most likely), but you can have both servers running as long as they are using different ports.
That way you could have both IIS and Apache working at the same time, meaning that you would be able to use IIS as a web server for your company's regular work and having Apache on custom port - running activeCollab (http://youractivecollab:8080, for example).
This would certainly work (in theory) but unfortunately, I don't think installing Apache will be an option for us. I wish it was!
Staff
Oliver Maksimović
on Jan 26. 2008. 12:01 am
Well, it does work in practice, too - just try to google for "apache and iis" or "running apache and iis" and you'll get a confirmation that it does work :) You can have as many web servers as you wish, it's all OK if they are running at different ports (the same rule applies to running multiple database servers and others).
I don't understand why you (your company, actually) are avoiding Apache - you don't need to pay for it, it's reliable, fast, it works on so many hosting servers worldwide, blah blah... so far it is the only safe and reliable way for you to run activeCollab because the solution for this PHP bug seems unavoidable. Can't you even use it as a temporary solution, until someone finally says "eureka" and solves the weird problem we are dealing here?
I don't understand why you (your company, actually) are avoiding Apache - you don't need to pay for it, it's reliable, fast, it works on so many hosting servers worldwide, blah blah... so far it is the only safe and reliable way for you to run activeCollab because the solution for this PHP bug seems unavoidable. Can't you even use it as a temporary solution, until someone finally says "eureka" and solves the weird problem we are dealing here?
activeCollab team member, too ;)
Pro
Rusty Thompson
on Feb 1. 2008. 9:13 pm
I had the same problem though my errors and results were different.
My solution: http://www.wampserver.com/en/
So far so good on win2k server, win2003 server and win2k3 on VMware.
Small issue with GD but nothing a restart doesn't fix.
My solution: http://www.wampserver.com/en/
So far so good on win2k server, win2003 server and win2k3 on VMware.
Small issue with GD but nothing a restart doesn't fix.
Pro
We ended up installing it under apache on another port. This worked out fine, been using it pretty religiously for about 4 days now. Though I'd love to know why it wasn't working under IIS.
i am having the same issue. i've tried installing on iis 6 as isapi and as cgi and both have their own problems. if the isapi extension crashes, it seems to bring down iis with it but as cgi, it will won't. so at the moment, cgi is my preference until i get this hotfix through my email from microsoft. has anyone tried it with good results?
i believe i have found something...if you check php.ini, and if you have the exif extension (http://uk.php.net/exif) enabled, it must be put after the mbstring extension. that's what i did and everything seems to be working well now (i've only been testing for the past 10 minutes but it's the most successful i've been with php and iis all weekend). let me know if this fixes anyone elses problems so i don't get too relaxed about this issue...thanks!
oh yeah, the hotfix didn't even manage to install cause it said some file in service pack 2 was newer or something so that wasn't a prerequisite for my solution above.
oh yeah, the hotfix didn't even manage to install cause it said some file in service pack 2 was newer or something so that wasn't a prerequisite for my solution above.
