V2 /
InstallationFAQV2.InstallationFAQ HistoryHide minor edits - Show changes to markup Changed lines 8-15 from:
Various MySQL? installations use different hash formats for the login passwords. Make sure the admin password in 'reg_master' is set to the proper password() format to:
Various MySQL? installations use different hash formats for the login passwords. Make sure the admin password in 'reg_master' is set to the proper password() format 1.3 : A PropertyDAO? error happens after initial installPart of the installation process is setting up the default properties for an event. There is a known bug that occasionally one property isn't set up right on the very first startup. The error message is: java.lang.NullPointerException? com.stonekeep.congo.dao.PropertyDAO?.getProperty(PropertyDAO?.java:187) com.stonekeep.congo.coconut.Login.execute(Login.java:77) The way to fix this is to log into the MySQL? database instance for this event and change one column value: update config_properties set prop_scope='Global' where prop_name='Administrator' ; Changed lines 3-4 from:
Caused By: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) to:
Caused By: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) Changed lines 5-7 from:
set GLOBAL log_bin_trust_function_creators=1 to:
Changed line 1 from:
to:
1.1 : Error during InitializationChanged line 1 from:
Error during Initialization to:
Changed line 1 from:
"Error during Initialization'' to:
Error during Initialization Added lines 1-5:
"Error during Initialization'' The following text appears when setting up the database for the first time: Caused By: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable) Answer: MySQL? 5.1 changed a requirement for stored procedures. The quick solution is to change the global setting: set GLOBAL log_bin_trust_function_creators=1 |