Also, my sometimes it will show Error 500: Internal Server Error.

Try with some other machine, in case this is a hardware issue. And if it fails on some other machine too, please tell use how you installed PHP and configured it.

Well, I just moved the server to a different machine that has a 1ghz Athlon Thunderbird w/ 512mb PC3200 RAM and Server 2003. It still does it. I had it working fine this morning right after a clean install....I just installed Server 2003 and all of that on this one. I installed PHP by getting the zip file and moving it to a folder called PHP. Then I moved the php4_ts.dll to Windows/system32...then moved php.ini to Windows. Then in IIS I set it to look for php4isapi.dll. How can it be a hardware issue? Could I need more RAM? I mean it says that it is using around 150mb of the page file.

I think I should mention that I've had PHP 4.3.1 running perfectly with Windows 2003 Enterprise Server.

Do note that Windows .NET Enterprise Server is an older beta version (available to only MSDN subscribers, I believe...) and may have bugs that the RTM does not.  I, personally, am still using the Windows 2003 Enterprise Server CPP (RC2) which does not exhibit this problem.  (yeah, they renamed it because someone realized that .NET had nothing to do with it.)

However, this could be a bug in phpBB on that platform.  Being a developer of YaBB SE, I do only a marginal amount of testing with phpBB.  Yet, I sincerely doubt this is the problem.

However, on another note, it'd be nice if the Win32 installer supported IIS 6.0.

-[Unknown]

Not enough info very much likely not PHP problem.
(there are a lot of people for whom php works fine on win32)

I have three copies of Win Server '03. I have build 3718, 3725(?), and 3790. All of them except build 3790 say .NET and if I am not mistaken 3790 was the last build. This copy that I am using now came in a CD from Microsoft.

I mean how can it not be a php problem? I mean I have just moved it to another server that it is an Athlon XP 2600 overclocked to an Athlon XP 3200 w/ Geil 512mb PC3200 soon to be 1gb. I mean it has done this on three machines so far using the ISAPI. By the way, it didn't just do this with PHPBB. It does this with every page that has php on it on my site. What other info could you want?

Bogus? i have been running into it. Im using 4.3.5 on Windows 2003 server with iis 6.0. Its sparatic though, so i dont know which situation will always reproduce it. Refreshing the page will sometimes show it, maybe 1 in 5. I'll post more if i tract down anymore info.

I guess i do got another update. Restarting the IIS service seems to stop it. Odd. Might be an issue in IIS or a combination of the two. I'll post again if it reappears

If you are running the ISAPI version of PHP, expect problems (did you read the documentation where it says not to use it in production?).  Likewise with Apache 2.

I havent been able to find anything in the documentation saying i should use the isapi module over cgi binary or visa versa for iis in the documentation. It does say the benift of the isapi module is speed and thats why i used it. I did see the warning for apache 2, but i found nothing for IIS.

If there really is an issue, the documentation needs to be updated. It needs to be updated for installation on IIS 6 as well as there are a couple extra steps.

Then I suggest you check your eyeglasses prescription, and re-read install.txt that ships with the win32 php distribution again.

Ok i found it, just not where I exepected to find it. I would appricate a message being added to the iis specific instructions since i pretty much just skipped to that.

But isnt this the wrong attitude to take? Instead of using my case to fix a bug, your telling me i should not use the isapi version. I would be willing to help run tests to find the source of this bug and getting it fixed.

It's a matter of how we want to spend our free time; Apache on win32 and FastCGI under IIS are much more stable alternatives that work.

If we're not being paid to do it, why should we sit down and debug something when we can be doing pretty much anything else and feel happier about it? :-)

Having said that, if you can isolate the cause of the problem, someone might look into it, it's just that there are no guarantees (just like with any part of PHP; no guarantee for anything).