This is a list of some common errors you may encounter during the database installation. Usually they are caused by one of three issues:

 - Default character set not correctly chosen
 - Default correlation not correctly chosen
 - "Continue On Error" option turned-off during database load

Here is some specific information on these issues:

 - Default character set not correctly chosen

The most common error that occurs if this is not set properly is a error loading the Translation Table.

If you take a look at the message, it kinda of tells you what the problem is but I admit the MySQL error messages could be better. This kind of error happens when you are trying to insert the Unicode translation characters into a database that does not support the special characters. So the database you are trying to load the script into did not have the proper character set selected, or the database was not created properly.

Your character set selection should look something like the following:

/*!50003 SET character_set_client  = utf8 */ ;
/*!50003 SET character_set_results = utf8 */ ;
/*!50003 SET collation_connection  = utf8_unicode_ci */ ;

 - "Continue On Error" option turned off during database load

The most common sympton of this problem is some kind of error concerning missing functions, like fnRound()

When you build a script, the MySQL system just dumps everything out in alphabetical order. So, if you are calling a stored procedure that it didn’t load yet, due to the order, it gives an error message.

For example, there is a function in the system called “fnRound()” and this stored procedure is called by many other stored procedures. Now, some systems when they load the stored procedures, check them for errors as they load, and, they find that fnRound() does not exist, but, this is only because it is near the end and has not been loaded yet. There are a few ways to fix this.
  1. Turn on the option “Continue on error” (you should most likely do this anyway actually) It will ignore the missing fnRound() error then load fnRound() anyway and everything works fine
  2. Cut the function out of it’s place in the script and make it the first stored procedure. Basically, just Move fnRound() to be the first stored procedure
  3. Create an empty fnRound() in the database then load the script
Basically any of those methods or similar methods will overcome this error. The best method is to simply turn on "Continue on Error" option