Installation on WAMP stuck on "Installing dashboard"
Permalink 2 users found helpful
So this is pretty much the issue, I am installing concrete 5.6 on wamp server, everything is going great until I get to installing dashboard then nothing happens, it just cycles for eternity. So i went on the forums and tried to install 5.5 and still same problem. Any ideas?
See anything in the Apache logs?
[Wed Dec 26 15:24:26 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Wed Dec 26 15:24:26 2012] [notice] Server built: May 13 2012 13:32:42
[Wed Dec 26 15:24:26 2012] [notice] Parent: Created child process 5328
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Child process is running
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Acquired the start mutex.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting 64 worker threads.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting thread to listen on port 80.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting thread to listen on port 80.
[Wed Dec 26 15:24:30 2012] [error] [client ::1] client denied by server configuration: C:/wamp/www/
[Wed Dec 26 15:31:10 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Wed Dec 26 15:31:10 2012] [notice] Child 5328: Exit event signaled. Child process is ending.
[Wed Dec 26 15:31:11 2012] [notice] Child 5328: Released the start mutex
[Wed Dec 26 15:31:12 2012] [notice] Child 5328: All worker threads have exited.
[Wed Dec 26 15:31:12 2012] [notice] Child 5328: Child process is exiting
[Wed Dec 26 15:31:12 2012] [notice] Parent: Child process exited successfully.
[Wed Dec 26 15:24:26 2012] [notice] Server built: May 13 2012 13:32:42
[Wed Dec 26 15:24:26 2012] [notice] Parent: Created child process 5328
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Child process is running
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Acquired the start mutex.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting 64 worker threads.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting thread to listen on port 80.
[Wed Dec 26 15:24:26 2012] [notice] Child 5328: Starting thread to listen on port 80.
[Wed Dec 26 15:24:30 2012] [error] [client ::1] client denied by server configuration: C:/wamp/www/
[Wed Dec 26 15:31:10 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Wed Dec 26 15:31:10 2012] [notice] Child 5328: Exit event signaled. Child process is ending.
[Wed Dec 26 15:31:11 2012] [notice] Child 5328: Released the start mutex
[Wed Dec 26 15:31:12 2012] [notice] Child 5328: All worker threads have exited.
[Wed Dec 26 15:31:12 2012] [notice] Child 5328: Child process is exiting
[Wed Dec 26 15:31:12 2012] [notice] Parent: Child process exited successfully.
This line got my attention:
It's kind of looking like an Apache configuration issue. Just a guess...
[Wed Dec 26 15:24:30 2012] [error] [client ::1] client denied by server configuration: C:/wamp/www/ [Wed Dec 26 15:31:10 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
It's kind of looking like an Apache configuration issue. Just a guess...
yea it is, I loaded 32bit wamp on vista system this morning, got a 404 error when I was accessing local host and php, fixes the php issue by editing alias but still working on local host which is having an impact on my root folder.
If anyone knows any good references for working with apache give a holler :)
If anyone knows any good references for working with apache give a holler :)
I was able to install a copy of concrete5.5.2.1 then deleted it to try 5.6 (why I don't know, I was really tired at the time) It is now getting stuck on 5.5 again, as well as 5.6 at "installing dashboard" going to root around that file to see if I notice anything then try xampp. Will keep everyone updated as there are a few threads about this issue
I am running windows 8
fresh install of wamp 2.2e php 5.4.3 httpd 2.2.22 mysql 5.5.24 x64
changed mysql engine to innodb
trying to install Concrete5.6.0.2
I can manually create a folder with an index.php and make it work but the install script for C5 seems to be having an issue?
Always halts on installing dashboard.
Always builds 166 tables in the db
Never finishes?
I will keep tinkering but this is not good.
fresh install of wamp 2.2e php 5.4.3 httpd 2.2.22 mysql 5.5.24 x64
changed mysql engine to innodb
trying to install Concrete5.6.0.2
I can manually create a folder with an index.php and make it work but the install script for C5 seems to be having an issue?
Always halts on installing dashboard.
Always builds 166 tables in the db
Never finishes?
I will keep tinkering but this is not good.
Hi guys. I found a helpful discussion at http://www.concrete5.org/developers/bugs/5.6.0.1/5.6.0.1-installati... .
The issue I had encountered was that the PHP installer was taking too much to time to install and timing out. You can give yourself more time by going to your WAMP console and edit the php.ini. Look for
and change the value to 180. That should increase your execution time to 3 minutes.
I hope that helps.
The issue I had encountered was that the PHP installer was taking too much to time to install and timing out. You can give yourself more time by going to your WAMP console and edit the php.ini. Look for
max_execution_time = 30
and change the value to 180. That should increase your execution time to 3 minutes.
I hope that helps.
Here is another link
http://www.concrete5.org/community/forums/installation/installation...
The solution to that Dashboard issue was to go under [mysqld] and write: default-storage-engine=MyISAM .
http://www.concrete5.org/community/forums/installation/installation...
The solution to that Dashboard issue was to go under [mysqld] and write: default-storage-engine=MyISAM .
For what it's worth, here's the long and short of my own development-centered (local) installation ups and downs:
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
For what it's worth, here's the long and short of my own development-centered (local) installation ups and downs:
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
For what it's worth, here's the long and short of my own development-centered (local) installation ups and downs:
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
First: I was going through the standard WAMP stack and coming across a number of issues.
Second (and third and fourth): I continued trying to go through the standard WAMP stack and was coming close to calling it a night.
FINALLY: I remembered an intriguingly simple little server called Uniform Server (UniformServer.com) and decided to give it a go. Low and behold, it worked!
Why use Uniform Server? Because it's simple. It comes pre-configured for development, meaning that there's a default mysql username and password of 'root' and 'root,' though the default settings also keep the server strictly local, meaning there are no security risks unless you connect it to the net.
So if you're having trouble, or generally would like to make it all a bit more simple, check out Uniform Server (full disclosure: I DO NOT work for Uniform Server or have any association with it beyond being a pleased and happy user, eager to pass along good news of good software).
i have just installed concrete5.6.0.2 on my wamp2.2e 64bit i just followed the instructions although it gave me a hustle at the beginning. i then removed the alias folder and re-copied the original renamed to concreate and a database with the same name. then i made sure that the server was online and restarted the services. Lastly i copied the wamp favicon into the wamp/www/ folder and started the installation.
Hi Folks,
this issue was solved very easily for me thanks to a very simple fix supplied by exchangecore and bbeng just correct the following with notepad
You said you are using wamp, so if you left-click the wamp icon in your system tray, then go to MySQL and click my.ini it will open the configuration file. Then you can do a ctrl+f and find the default_storage_engine setting and set it to MyISAM. If it doesn't exist just add it under the [wampmysqld] heading see attached file
this issue was solved very easily for me thanks to a very simple fix supplied by exchangecore and bbeng just correct the following with notepad
You said you are using wamp, so if you left-click the wamp icon in your system tray, then go to MySQL and click my.ini it will open the configuration file. Then you can do a ctrl+f and find the default_storage_engine setting and set it to MyISAM. If it doesn't exist just add it under the [wampmysqld] heading see attached file
Adding default_storage_engine=MyISAM to my.ini worked for me!
Followed the procedures in this thread and it solved the issue for me.
Using Bitnami WAMP stack. (not the concrete5 stack.)
http://www.concrete5.org/community/forums/installation/installation...
The answer in the thread:
find [mysqld] in your mysql.ini
replace with below code
[mysqld]
#port=3306
lower_case_table_names = 2
default-storage-engine=MyISAM
DON'T FORGET TO RESTART YOUR SERVERS
Using Bitnami WAMP stack. (not the concrete5 stack.)
http://www.concrete5.org/community/forums/installation/installation...
The answer in the thread:
find [mysqld] in your mysql.ini
replace with below code
[mysqld]
#port=3306
lower_case_table_names = 2
default-storage-engine=MyISAM
DON'T FORGET TO RESTART YOUR SERVERS
i was getting same error i.e stuck at creating database tables and or dashboard
added code to my.ini as stated above
[mysqld]
#port=3306
lower_case_table_names = 2
default-storage-engine=MyISAM
I restarted wampp
I used 127.0.0.1 instead of localhost
installed ok
added code to my.ini as stated above
[mysqld]
#port=3306
lower_case_table_names = 2
default-storage-engine=MyISAM
I restarted wampp
I used 127.0.0.1 instead of localhost
installed ok
It appears to be an issue with the most recent version of MySQL, server recently updated. There is a workaround posted in this forum thread:http://www.concrete5.org/community/forums/installation/mysqlt-error...
James Blue Host: Okay, this is really going outside our scope of support, but I want to make sure you're taken care of and I don't think most of our technicians would have been able to fix the MySQL issues, since it's a code compatibility problem that our developers need to release an update for. So after you install on the other domains,
I'd like you to email jameshostingtests@gmail.com if you're still having the MySQL issue on those new installations
My error message I have not fixed. I think it is in simple scripts download for C5.
mysqlt error: [1048: Column 'uID' cannot be null] in EXECUTE("INSERT INTO Config (cfKey,cfValue,uID) VALUES ('NEWSFLOW_LAST_VIEWED','FIRSTRUN',NULL)")
James Blue Host: Okay, this is really going outside our scope of support, but I want to make sure you're taken care of and I don't think most of our technicians would have been able to fix the MySQL issues, since it's a code compatibility problem that our developers need to release an update for. So after you install on the other domains,
I'd like you to email jameshostingtests@gmail.com if you're still having the MySQL issue on those new installations
My error message I have not fixed. I think it is in simple scripts download for C5.
mysqlt error: [1048: Column 'uID' cannot be null] in EXECUTE("INSERT INTO Config (cfKey,cfValue,uID) VALUES ('NEWSFLOW_LAST_VIEWED','FIRSTRUN',NULL)")
