Can’t Select Database …

No, they are not fine – if you got that message. (99.99% of cases it is the user’s fault, despite stating “it is fine” ??

Did you add the user to the db? Is the DB name correct? (it’s case sensitive) Did you put it in the right place?

Fortunately, I’m not a total noobe. I’ve checked to ensure all is right (text pasted below). I’ve tried with the username_db and that didn’t work (different error).

I like your 99.99% line, and it’s probably true, but a quick search turned up umpteen of these same errors, many of them having to do with GoDaddy (what I use). Surely someone could easily figure this out by now.

Thanks for the help, but I need help beyond telling me to check all the stuff the error message tells me to check.

Further thoughts? I’m not trying to be sarcastic, I really do appreciate the help.

My bad … here’s my text (changed my username and password out for those words):

<?php
// ** MySQL settings ** //
define(‘DB_NAME’, ‘prville’); // prville
define(‘DB_USER’, ‘username’); // username
define(‘DB_PASSWORD’, ‘password’); // password
define(‘DB_HOST’, ‘mysql111.secureserver.net’); // 99% chance you won’t need to change this value

// You can have multiple installations in one database if you give each a unique prefix
$table_prefix = ‘wp_’; // Only numbers, letters, and underscores please!

// Change this to localize WordPress. A corresponding MO file for the
// chosen language must be installed to wp-includes/languages.
// For example, install de.mo to wp-includes/languages and set WPLANG to ‘de’
// to enable German language support.
define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

define(‘ABSPATH’, dirname(__FILE__).’/’);
require_once(ABSPATH.’wp-settings.php’);
?>

If it’s godaddy… then you should continue to search ?? As you may have found already there are challenges installing on that host, but I remember threads where users posted back what they did to succeed.

Are you on Win or Linux package?

Here’s what I figured out for myself:

“DB Manager is installed with a default database that uses the same name as your domain name (with underbars replacing periods).”

Now I went ahead and created an additional database: my_domain_wordpress, and I got the error as cited in this thread.

When I retreated to just using the default database “my_domain” created by DB Manager it worked fine. Moreover, once I put stuff in the default db, then I could get wordpress to work in the 2nd db just fine.

So, you can’t create use secondary db if the default one is empty? I don’t know, but perhaps this will be useful for the next guy.