Trevor,
Add the following lines to the top of setup-config.php, after the opening <?php tag:
error_reporting(E_ALL);
ini_set(‘display_errors’, 1);
define( ‘WP_DEBUG’, true);
This should give you a more specific error message.
Duncan Russell
[link removed – please see the forum guidelines about links in signatures]
Duncan,
Thanks for registering and responding! That didn’t really seem to have an effect on the resulting error in Internet Explorer 11 on Windows 8.1. I even disabled “friendly HTTP error messages” in IE.
Any thoughts?
Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
Oh, hold on. setup-config.php defines errors already. Open in Wordpad, and search/replace:
error_reporting(0); –> error_reporting(-1);
Or error_reporting(E_ALL);
Debugging messages may not be present if one of the files is corrupted, or has odd line endings.
You could try re-uploading the WordPress files, particularly the wp-admin folder, wp-includes folder, and the files in the base directory. If there was an issue with uploading one of the files, this may fix it. install.php is in the wp-admin folder, BTW.
I just deleted the entire contents of the wwwroot directory and re-uploaded WordPress 4.1.1. I’m still getting the exact same behavior as soon as I get to “step 2.”
Next, I’m going to try deleting the website and re-creating it on the web host’s Control Panel.
Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
Okay, so the issue turned out to be:
1. My web host (Arvixe) uses WebsitePanel as their Control Panel tool
2. WebsitePanel apparently limits password length for MySQL database user accounts. I was using a 128-bit password, and had to resort to a 38-bit password instead.
3. WordPress fails to do appropriate error checking / handling for invalid database logins.
4. Hours of my time are wasted.
Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
