|
Teamwork seems to stop and crash after creating 117 empty tables. I would assume that means Tomcat is running and JDBC can connect. First 3 entries from "platform.log" file are shown below. I'm trying to run TW from a QNAP TS-509 NAS (MySQL,JRE,Tomcat installed). 2011 Dec 01 09:23:47 ERROR platformLogger:431 - com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'teamwork.twk_issue' doesn't exist 2011 Dec 01 09:23:52 ERROR platformLogger:235 - Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' java.sql.SQLException: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' This is Jean S. I am working with Alex C. on this problem. We followed Silvia's directions to solve this problem. We did these steps but the 117 tables are still empty. Do you have any suggestions? Here is the original answer: Teamwork should create exactly 117 tables, so it seems that all of them have been created. If you have all of them empty (you should check the olpl_operator that should contain the first administrator users), try stopping Tomcat, open the global.properties (TEAMWORK_ROOT/webapps/ROOT/commons/settings) file and remove the line "setup_notified_admin_wizard=yes". Then restart tomcat. In this way Teamwork should create the first installation data and you should be able to login. let me know. Thanks, Jean S. |
