OK. I've repartitioned and reformatted my hard drive and installed Windows 2K Server with SP4 and IIS 5. I've installed PHP 4.3.3, MySQL 4.0.16 and Moodle 1.1.1, carefully following the instructions available on this website at http://moodle.org/doc/?file=install.html.
I set up a Windows user account called "moodleuser" with "moodle" as a password. This account has full rights to the moodle database folder (C:/mysql/data/moodle). Forward slashes are used here because backslashes don't display, but I assure you, the proper slash is used in the appropriate situation.
The php.ini and my.ini files reside in my C:/WINNT directory. Here's what my.ini looks like:
# set basedir to your installation path, for example, C:/mysql
# set datadir to the location of your data directory, # for example, C:/mysql/data or D:/mydata/data
...and here's a section from my config.php file:
$CFG->dbtype = 'mysql'; // mysql or postgres7 (for now)
$CFG->dbhost = 'training.kofax.com'; // eg localhost or db.isp.com
$CFG->dbname = 'moodle'; // database name, eg moodle
$CFG->dbuser = 'moodleuser'; / // your database username
$CFG->dbpass = 'moodle'; // your database password
$CFG->dbpersist = true; // Use persistent database connection?
// (should be 'true' for 99% of sites)
$CFG->prefix = 'mdl_'; // Prefix to use for all table names
I also set up a database folder using mysql.exe and the following command lines:
GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* TO <strong>email@example.com</strong> IDENTIFIED BY 'moodle';
Although PHP is running correctly and the mysql service starts and the MySqlAdmin.exe tool indicates everything is up an running (it even sees the moodle database folder), I'm still getting the following error:
Error: Moodle could not connect to the database.
It's possible the database itself is just not working at the moment.
The admin should also check that the database details have been correctly specified in config.php
Database host: training.kofax.com
Database name: moodle
Database user: moodleuser
Please HELP! This looks like a permissions issue, but I've run out of tricks.