I guess you’re using IIS on Windows? I usually use Apache, but Google will be of some better help. I remember once getting a similar error, but setting PHP as an ISAPI extention yielded better results (and was faster too)
Saw recently with one host, www.hostnexus.com, that with their Plesk control panel, they allowed PHP, via a check box, to run as an ISAPI extension. WordPress 2.3.3 installed just fine.
I’m going to see if they can run PHP as an ISAPI extension…that Plesk link you posted said it can be done for one domain (at least with Plesk)…I looked for a similar setting, all I can do is switch it from PHP5 to PHP4. I’ll send another note with the support ticket about it and see what they say.
I don’t believe that CGI or ISAPI would make a difference. Usually these errors are caused by URL rewriting. Your script seems to be more geared for a Linux server running Apache.
As a test, I switched your site to ISAPI and it still did not work, but didn’t show the CGI error anymore.
I left it like that for now for you to see.
Then, like an idiot, I accidentally touched the PHP setting in the control panel and it reverted back to CGI! :
I’m waiting for them to change it back, but in the meantime, I thought I’d let you know what happened. Just before the php setting got reverted, I tried loading the site again, and I got a plain blank screen when just trying to view the home page.
I thought maybe once they switch it back, I should re-install phpvms…necessary?
Revert it to ISAPI, we’ll see if there are any errors being thrown with the blank screen. I’m not sure if it’s through the php.ini. But good to know you can edit that, if need be.
I’m not using any URL rewriting though. I think we have a few people running on IIS with PHP, they haven’t had any problems though. But revert it and we can go from there