This is the same thing that happens to me when I attempt to use the vb_test.php file. I put in my server info and click on Run Test and get the same 404 page.
I set up IIS to use c:phpphp.exe for .php .phtml and .php3 in the home directory and checked the Cache ISAPI Applications box. When I tried to set up PHP to run as using the php4isapi.dll under the ISAPI filters tab as well as changing the home directory. That made it worse and I couldn't even get a script to run at all. I also tried the isapi_fcgi.dll that I read about somewhere on these forums and had the same result of nothing running at all. So I put it all back to the php.exe and removed any reference to the two .dll in IIS setup.
Anyways...now I'm in the "poke it with a stick" mode of troubleshooting which is dangerous with my level of skill with PHP and MySQL. After reading a LOT of stuff from these boards I have come to the conclusion that I will not figure this one out alone. Can someone help me?
Here are my answers to the list of questions that you all ask for
1. This is a dedicated server
2.
-cpu speed single p4 2.8ghz
-how much memory installed: 128mb ram ( I will put in a full GB as soon as I get vB running)
-hard drive type/configuration: (2 physical drives)OS resides on a 4GB EIDE non raid/while webroot and mysql reside on a 10GB EIDE non raid
-Windows version 2000 Server SP4
-IIS version: 5
-PHP version: php 4.3.1
-MySQL version: mysql 5.0.0
4. I have no idea how MySQL was compiled
5. No MySQL stats yet. It's a new server
6. my.ini contents for MySql are:
[client]
port=3306
[mysqld]
port=3306
basedir=D:/Progra~1/MySQL/MySQLS~1.1/
datadir=D:/Progra~1/MySQL/MySQLS~1.1/Data/
default-character-set=latin1
default-storage-engine=INNODB
max_connections=100
query_cache_size=8M
table_cache=256
tmp_table_size=7M
myisam_max_sort_file_size=100G
myisam_max_extra_sort_file_size=100G
myisam_sort_buffer_size=10M
key_buffer_size=8M
read_buffer_size=64K
read_rnd_buffer_size=256K
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=8M
innodb_log_file_size=10M
innodb_thread_concurrency=8
7. I have no MySql stats yet since the server has never been live.
8. vB is the only thing on this server that uses scripts
9. how many average and max concurrent users on your vB forum ? and what your cookie timeout is ?
I don't have a forum yet.
10. http://www.swinklink.com/phpinfo.php
11. N/A since I have an IIS server
12. what version of vB are you running ?
It's not running yet but I am trying to install 3.0.7
I unchecked the Cache ISAPI Applications box and restarted IIS but I still get the same result.
Isn't the "web service extensions" part an IIS 6 feature? In IIS 5 I have setup the home directory to use PHP.EXE for php extentions (.php, .phtml, and .php3). Does that accomplish the same thing you were recommending or am I misunderstanding you?
Bottom line it it still isn't working but I'm learning a lot.:(
Could this be an NTFS permissions issue?
On a good note though I replaced the 10G hard drive with an 80G ATA drive for web directories and also popped in a couple of 512M RAM sticks. Something about having to post the previous stats out there for the public to read was a little embarassing.
Now to get to work on these MySql faulires in vb_test.
EDIT: I found that answer too. I had to turn OFF "Use Old Passwords" in MySql. I don't want someone else searching for MySql in the forums and following what I said above about reading somewhere that PHP needed MySql to use old passwords. It must have been an old piece of documentation that I found. I'll edit my above post so it won't be there to trip up someone else.
Make sure these settings are correct in your php.ini.
cgi.force_redirect = 0
cgi.fix_pathinfo=1
fastcgi.impersonate = 1
cgi.rfc2616_headers = 1
browscap = C:WINNTsystem32inetsrvbrowscap.ini
Also remove the trailing in your path to php extensions.
Make sure in web service extensions that php is allowed.
#If you have any other info about this subject , Please add it free.# |
edit
