PHP can be run as a handler, as a CGI, or under FastCGI. There are three ways to set up PHP to work with Apache 2.x on Windows.
Windows 2008 php 5.2 manual#
I am on PHP 5.2.9.2 and MySQL ver 4 that ships with hMailserver ver 4. Follow the Manual Installation Steps and come back to go on with the integration of PHP and Apache. I use PHP IIS CGI rather than the Fast CGI that you have gone to, without error on IIS 6.0 (on Server 2003 and previously on XP). Have you tried re-setting the DCOM permissions? The OP used Server 2008 which has IIS 7.0 rather than IIS 6.0 that windows XP runs. I am not sure if this might shed a light on the solution, but if anyone has any further tips I'd like to know. So I think the problem probably lies with FastCGI somewhere, unless it doesn't have something to do with the MySQL upgrade.
![windows 2008 php 5.2 windows 2008 php 5.2](https://3.bp.blogspot.com/-9J1q2QHG06w/TiB8JWPDlPI/AAAAAAAAASA/lGoIulIRzOk/s1600/install-php-on-windows7-3.png)
The only difference between then and now (aside from a new version of MySQL) is that before I had PHP configured using ISAPI and now I use FastCGI since from PHP 5.3 onward ISAPI has been discontinued. I put back PHP to 5.2.10 in case that would provide a quick fix (my php.ini settings are the same between versions) but the error remained.
Windows 2008 php 5.2 full#
the ntwdblib.dll is in c:\php (ACL for c:\php is IUSR IISXXX NETWORK SERVICE full control) - environment include -> pathc:\php\ and and PHPRCc:\php\. uncommented the extension for phpmssql.dll. After the upgrades the error then occurred, whereas before it worked with no problem. Consequently, Windows 2008 R2 hosts are required to have SHA-2 code signing support installed on. - installed and setup PHP 5.2.14 as fastcgi. My problem only started after upgrading PHP from 5.2.10 to 5.3 and MySQL from 5.0.24a to 5.1.36. I am running XP Pro SP3 and I had no problems with the web interface using my original DCOM settings, so I think the solution lies elsewhere. There is one important difference in my case, however. I have the same error and tried all the recommended solutions thus far but with no luck. I wonder if anyone found a concrete solution to the problem yet. Set the Local Launch and Local Activation permissions for this user to Allow For Apache: add the Apache user accountġ0. For IIS6: add the built-in anonymous IIS user accountĩ. Under "Launch and Activation Permissions", select Customize and click on Editħ. Right-click on hMailServer and select propertiesĦ. Expand down to Computers | My Computer | DCOM ConfigĤ. In the Component Services program, expand the Component Services folderģ. Start DCOM config by selecting Start, Run, enter dcomcnfg.exe and press OK.Ģ. Also, Apache run as a user account with restricted permissions is not allowed to connect by default.įollow these steps to give IIS or Apache the required permissions to connect to hMailServer using DCOM.ġ. By default, IIS6 is not allowed to connect to hMailServer because of the Distributed COM permissions that Windows uses.