Bug #17074
closed
Install tool 123 mode only creates 26 out of 36 tables
0%
Description
A fresh installation of 4.1RC2 gave me a lot of "supplied argument is not a valid MySQL result resource", and made it impossible to get into the BE. I think this is a big problem for new users.
Back in the install tool clicking Compare in the Database Analyser gave me a list of 10 CREATE TABLE statements for cache_hash, cache_imagesizes, sys_history, sys_log, cache_pages, cache_pagesection, cache_typo3temp_log, cache_md5params, fe_session_data and fe_sessions.
Having the install tool write those changes to the database solved the problems.
Using "Compare with $TCA" now still tells me static_tsconfig_help and tx_impexp_presets are in the database, but not in TCA, and shows me a lot of other differences such as "Fields from database, but not in $TCA" and "Actual and suggested field definitions". Probably not an issue.
The database already existed; as I do not have enough rights on this machine to create a new database, I dropped all existing tables (actually an old TYPO3 installation) using phpMyAdmin before I deleted all the old TYPO3 files and installed the fresh copy of TYPO3. I think any indexes et cetera will also have been deleted at that point.
In 123 mode I could only select "Create default database tables" and click "Import database".
MySQL 3.23.56-Max, PHP 4.3.10, Linux
On the (empty) site, before showing "No pages are found on the rootlevel"
Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php on line 79
Warning: Cannot modify header information - headers already sent by (output started at /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php:796) in /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_userauth.php on line 311
When trying to login to the BE:
Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php on line 796
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php on line 783
Warning: Cannot modify header information - headers already sent by (output started at /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php:796) in /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_userauth.php on line 311
(issue imported from #M5125)
Files
Updated by Oliver Hader about 17 years ago
Please turn on the "sqlDebug" in the Install-Tool at "All configuration" and tell us the SQL statements producing errors/warnings.
Updated by Palahala about 17 years ago
Please turn on the "sqlDebug" in the Install-Tool
Ok, nice feature!
First of all note that after running the steps given in the bug report above, my problem was solved. So if others do not suffer this then that might be all right, as I know I'm using an old version of MySQL and PHP (but I cannot find any minimum MySQL version on pages such as http://typo3.org/about/system-requirements/ )
To enhance this bug report I enabled the debug mode and ran 123 mode again to see if any errors were shown. In detail:
- enabled SQL debug mode
- used a standalone installation of phpMyAdmin to drop all tables
- explicitly started 123 mode using /typo3/install/index.php?mode=123&step=1
- as I did not replace localconf.php with a clean copy, the database name etc. were already known this time, so I just clicked Continue in steps 1 and 2
- step 3, "Please select a database dump", only gave me a single option: "Create default database tables"
- now, with the debug enabled, the next screen showed the errors below, and no "Done" screen at all
- manually going to /typo3/install/ allowed me to run the Database Analyser, to fix the missing tables using the Compare option; problem fixed
Final note: I do not have root access to the database. So, the credentials I entered were those of a user of an existing, empty database.
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 7
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 9
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near ')' at line 14
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 21
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 14
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 7
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 7
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 7
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 9
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDB' at line 6
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR You have an error in your SQL syntax near 'ENGINE=InnoDb' at line 11
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
caller t3lib_DB::admin_query
ERROR Key column 'pid' doesn't exist in table
lastBuiltQuery
debug_backtrace require // tx_install->init // tx_install->checkthedatabase // t3lib_db->admin_query // t3lib_db->debug
Warning: Cannot modify header information - headers already sent by (output started at /web/typo3_src-4.1.0RC2/t3lib/class.t3lib_db.php:1094) in /web/typo3_src-4.1.0RC2/typo3/sysext/install/mod/class.tx_install.php on line 3649
Updated by Palahala about 17 years ago
Just in case this should not have happened either: following the procedure above, upon first login in the BE I get
"The Reference Index table is empty which is likely to be the case because you just upgraded your TYPO3 source. Please go to Tools>DB Check and update the reference index."
This is, of course, easily solved by following the instructions that are given, so not a problem.
Updated by Michael Stucki about 17 years ago
I just rechecked this and found out that there is indeed a problem with the 1-2-3 wizard: Due to a typo in the SQL definition, the table "sys_history" is not created automatically. I will take care of this problem.