I've got the same issue. If I find a solution I'll post it here. Anybody have any insight into this issue?

I see no errors, the installer does not timeout, it just hangs permanently at the "creating dashboard" screen.

I'm also using WAMP on localhost, I wonder if there is a connection there. Could it involve paths or permissions that are different on local than on a server?

I got past this issue by adding a new user to the database with a password. I'm hesitant to admit it, but my database user was "root" without a password... and I think might trip up some part of the installer, I think it "salts" the password and maybe the resulting hash cannot match when there is no pass? I'm not sure the reason, but adding a new user with full permissions and the install completed right away.

I am having the same problem on my Wamp localhost. I tried your solution using a user with a password (I was doing the same thing before, using root without a password) but the install is still stopping at "Installing Dashboard" :/ not sure what to do, this is the only place I have found information so far on this topic.

Alright, I figured out what worked for me. I suppose having a password was part of it, but in addition I had to change my "Storage Engine" for the database I was using with Concrete5.

http://www.concrete5.org/community/forums/installation/concrete-5.5...

To quote this thread:
"To solve the problem you have to go in the my.ini file and go under [mysqld] and write: default-storage-engine=MyISAM
and you have to save the file... "

So yeah, you have to use this MyISAM storage engine for the database you want to use with Concrete5. Good luck!

Is it correct you end up with this?

[mysqld]
default-storage-engine=MyISAM
port=3306

i did the above and made a new user with pw but no luck
anybody got something different?

just got it to work, you have to remove the port line

Thanks xb385, I followed your advice after having exactly the same problem. I changed the my.ini file as you suggested, but found it kept still hanging on the dashboard installation.

Finally I changed the site name to all lowercase with no spaces and finally the installation worked; so I think that might have actually been my problem all along.

did you follow the "how to" in documentation?

if so skip the step that suggests to add the following to my.ini

print("lower_case_table_names=0");

I have just spent 3 days tearing my hair out over this (and i didn't have much to begin with lol) and after removing this line of code it worked perfectly... :)

Thanks! I will try this.

The idea with the lowercase side name did not work in my case.

Does somebody has access to an php error log about this? Would be helpful to post an error log to this bug-report here:

http://www.concrete5.org/developers/bugs/5.6.0.1/5.6.0.1-installati...

Hey everyone,

Did anyone find a fix for this problem, ive tried all the changes i can find on this site and the install still hangs on installing dashboard.

Thanks in advance..

I just had all the problems many of these threads outline, had tried every fix to no avail. max_execution_time, default storage engine, with or without print("lower_case_table_names=0"), nothing worked until I ran the install using Firefox instead of Chrome, worked first time.

My server gives e this error. Any thoughts?

mod_fcgid: read data timeout in 45 seconds, referer:http://everydayvba.com/index.php/dashboard/system/backup_restore/up...
Premature end of script headers: index.php, referer:http://everydayvba.com/index.php/dashboard/system/backup_restore/up...

It looks like you are trying to restore a database and the database is too big for it to run within the server timeout.

It is possible to get round this by:
- put the site in maintenance mode
- use phpMyAdmin to import from the sql backup file
- check the site from the dashboard
- take it out of maintenance mode

With phpMyAdmin, it will use slightly less resources, so may actually do the import/restore all in one go.

If that still runs out of time, you can use a text editor to chop the sql backup file into 2 or more pieces - only split it between tables (not within a table) - then import each piece. (Do not visit your site between pieces - it will break). So:

- put the site in maintenance mode
- use phpMyAdmin to import the first piece of the sql backup
- use phpMyAdmin to import the second piece of the sql backup
... etc.
- check the site from the dashboard
- take it out of maintenance mode

I had same problem i modified the my.ini file adding [mysqld]
default-storage-engine=MyISAM, but i forgot to restart the server after i saved the file for the changes to take effect. once i did that all was fine. Hope this helps

SOLUTION: For anyone out there that might still be having issues after doing everything above ^, try increasing the max execution time in your php.ini. This solved the problem for me.