I created a website jackieevancho.uuuq.com and created a MySQL database
then created and assigned privileges to a user for that database per the documentation.

After each operation I got the following message:

"The requested operation has been completed successfully."

No indication of a problem, in other words.

When I tried to access the database via phpmyadmin I got "username/password" errors. At least the database existed but something wasn't happening like it should. I deleted the user and database and tried again, taking care with spelling and case. I tried this three times and could not get it to work.

At the same time, I researched the forum for some clue as to what I was doing wrong and I noticed a few posts from people having a similar problem. Some
workarounds were suggested and I tried those.

+ trying phpminiadmin did not work
+ someone went to the trouble here at the forum of putting up a webpage
to help get around the phpmyadmin problems but that did not work for me,
either.


I finally tried another approach -- I created a shorter sub-domain name: jetest.uuuq.com and I was careful to keep all names within a 15 character limit since I recalled something about MySQL having such a limit in previous versions.

Guess what? That worked.

I've tried it a couple more times ... I can create and use a mysql database
on jetest.uuuq.com via phpmyadmin but not on jackieevancho.uuuq.com.
The only difference I can tell is that the names are less than 16 characters on
jetest.uuuq.com but I can't make the names less than 16 characters on
jackieevancho.uuuq.com.

I doubt this is coincidence.

I do get some strange error messages on the opening phpmyadmin page
when first working with the database on jetest.uuuq.com:

"The mbstring PHP extension was not found and you seem to be using a multibyte
charset. Without the mbstring extension phpMyAdmin is unable to split strings
correctly and it may result in unexpected results."

"Connection for controluser as defined in your config.inc.php failed."

I assume the last message is a result of the first but I'm not sure and have
not researched it.

I'm thinking that 'mbstring' (multi-byte string) may be an indication of
an underlying problem. If I'm not mistaken, MySQL is multi-byte by default now
so an inability to correctly process multi-byte strings could yield some strange
results like those some of us are getting.

I'm just wondering if some of the problems popping up on phpmyadmin are due
to:

1. Scripts not all updated to reflect the longer names mysql allows now.
2. No or inconsistent multi-byte support in the scripts.

Arnold

When you were able to login, what was the format you used? ex:site_99k_org_databasename <<---Is it like that or different?

On the 'uuuq.com' domain the prefix is "subdomain_" for both database name and database user name. So, in one case for 'jetest.uuuq.com' I was using

database: jetest_db1
user: jetest_dbuser1

I've since experimented with 'jeforum.uuuq.com' and I was able to make it work, as well, by simply keeping the names 16 characters or less. I tried using different browsers and slightly different security settings and that had no impact -- the focal point of failure was always when the name length reached that critical 16 characters.

Since finding the workaround to this, everything else at Zymic has worked extremely well. I was able to install phpBB3 and myBB (for comparison shopping) without a great deal of effort. The interface to MySQL seems very stable right now and response time has been excellent.

By the way, the FTP program everyone recommends, 'FileZilla' -- it is superb. I highly recommend it. It also allows you to do CHMODs that seem to work quicker and with greater certainty than via Zymic's file manager (which, for some strange reason, fails to execute requested CHMODs now and then).

Arnold