WampServer

Hi,

I upgraded from WAMP 2.5 to 3.0.3 using the wampserver2.5_x64_update_3.0.3.exe download. I ran this as administrator.

All seemed to install fine; I installed it in the same directory as the 2.5 install - not sure whether that was correct or not.

Now when I run Wamp server (as Administrator), the icon very briefly flashes orange, and then reverts back to red. No services are running.

The PHP/MySQL errors (see below) seem to indicate a permissions/access issue, but I'm not well-versed enough in Window permissions etc to know how to get around this.

As help or advice would be much appreciated; please see answers to questions below.

Thanks,
Sarah


1 - Windows version used (Specify version number AND whether 32 or 64 bit)
>> Windows 10 Pro 64-bit OS, x64-based processor


2 - Version WampServer (Specify version number AND whether 32 or 64 bit)
>> 3.0.3 64-bit, upgrading from 2.5 (not sure but presumably 64-bit)

3 - Apache Version
>> 2.4.9

4 - PHP Version
>> Currently set on 5.5.12. Want to use 7, hence the upgrade!

5 - MySQL Version
>> 5.6.17

6 - What color is the WampServer icon (in the notification area of the taskbar)
>> Red

a - Apache error log
>> Checked; no errors, only notices

- Apache access log
>> Checked, last entry is 127.0.0.1 - - [17/Aug/2017:10:02:44 +0100] "GET / HTTP/1.1" 200 8939

b - MySQL error log
>> Checked, no errors, only Notes, last is 2017-08-17 10:13:41 5024 [Note] wampmysqld64: Arrêt du serveur terminé

c - PHP error log
>> Errors! See below (there are more lines previous, but I think all similar to these):

[17-Aug-2017 11:10:44 Europe/Paris] PHP Stack trace:
[17-Aug-2017 11:10:44 Europe/Paris] PHP 1. {main}() C:\wamp\scripts\switchPhpVersion.php:0
[17-Aug-2017 11:10:44 Europe/Paris] PHP 2. switchPhpVersion() C:\wamp\scripts\switchPhpVersion.php:7
[17-Aug-2017 11:10:44 Europe/Paris] PHP 3. linkPhpDllToApacheBin() C:\wamp\scripts\wampserver.lib.php:139
[17-Aug-2017 11:10:44 Europe/Paris] PHP 4. symlink() C:\wamp\scripts\wampserver.lib.php:84
[17-Aug-2017 11:10:44 Europe/Paris] PHP Warning: symlink(): Cannot create symlink, error code(1314) in C:\wamp\scripts\wampserver.lib.php on line 93
[17-Aug-2017 11:10:44 Europe/Paris] PHP Stack trace:
[17-Aug-2017 11:10:44 Europe/Paris] PHP 1. {main}() C:\wamp\scripts\switchPhpVersion.php:0
[17-Aug-2017 11:10:44 Europe/Paris] PHP 2. switchPhpVersion() C:\wamp\scripts\switchPhpVersion.php:7
[17-Aug-2017 11:10:44 Europe/Paris] PHP 3. linkPhpDllToApacheBin() C:\wamp\scripts\wampserver.lib.php:139
[17-Aug-2017 11:10:44 Europe/Paris] PHP 4. symlink() C:\wamp\scripts\wampserver.lib.php:93
[17-Aug-2017 11:10:44 Europe/Paris] PHP Warning: chmod(): Permission denied in C:\wamp\scripts\config.inc.php on line 95
[17-Aug-2017 11:10:44 Europe/Paris] PHP Stack trace:
[17-Aug-2017 11:10:44 Europe/Paris] PHP 1. {main}() C:\wamp\scripts\refresh.php:0
[17-Aug-2017 11:10:44 Europe/Paris] PHP 2. require() C:\wamp\scripts\refresh.php:8
[17-Aug-2017 11:10:44 Europe/Paris] PHP 3. chmod() C:\wamp\scripts\config.inc.php:95
[17-Aug-2017 11:10:44 Europe/Paris] Impossible to modify the file C:\WINDOWS\system32\drivers\etc\hosts to be writable
[17-Aug-2017 11:10:44 Europe/Paris] The file C:\WINDOWS\system32\drivers\etc\hosts is not writable

d - The windows event viewer
>> Errors: The following sequence of four MySQL errors appears multiple times

Failed to open log (file '.\mysql-bin.000370', errno 2)
Could not open log file
Can't init tc log
Aborting

7 - In the file c:\Windows\System32\drivers\etc\hosts, what are the active lines with the name [localhost] in them?127.0.0.1 localhost
127.0.0.1 localhost

Hi,

Apply the WAMPServer 3.0.9 upgrade. This can be done directly over 3.0.3.
This will only update wamps own code and not change any version of Apache/MySQL/PHP

Also check that your C drive is not formatted as FAT, it must be NTFS for SYMLINKS to work.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Thanks for your help @RiggsFolly. I managed to get a green WAMP icon before I saw your message (didn't get email notification for some reason).

I had to:

1) Set WAMP to always run as administrator (& restart). Then I was getting an orange icon; PHP issue solved.

2) I was then getting the following in mysql.log, so removed the last line in wamp/bin/mysql/mysql5.6.17/data/mysql-bin.index

wampmysqld64: File '.\mysql-bin.000370' not found (Errcode: 2 - No such file or directory)
2017-08-18 09:07:02 1224 [ERROR] Failed to open log (file '.\mysql-bin.000370', errno 2)
2017-08-18 09:07:02 1224 [ERROR] Could not open log file
2017-08-18 09:07:02 1224 [ERROR] Can't init tc log
2017-08-18 09:07:02 1224 [ERROR] Aborting

I have also now upgraded to 3.0.9 as per your post.


However... (things are rarely straightforward!) I now find that my WordPress database tables do not exist. I can see the databases and tables listed in phpMyAdmin, but when I click on a table to view, I get the message '#1146 - La table '...' n'existe pas'. And I get a whole load of new errors in mysql.log (see bottom of post).


I did a backup of the whole wamp directory before the upgrade process; can you direct me to which files I should pull back into the live directory? - if this is recoverably?!!

Many thanks

--

017-08-18 09:38:15 11360 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2017-08-18 09:38:15 11360 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50524, now running 50617. Please use mysql_upgrade to fix this error.
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
2017-08-18 09:38:15 11360 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure

Fixed it! (I think/hope!)

I had to delete ib_logfile0 and iblogfile1 from wamp/bin/mysql/mysql5.6.29/data (after backing up to temp location), then restart server.

That seemed to fix it.

Now I just get the following warnings in mysql.log:

2017-08-18 11:09:41 3508 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2017-08-18 11:09:41 3508 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2017-08-18 11:09:41 3508 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2017-08-18 11:09:41 3508 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See [dev.mysql.com] for how you can resolve the problem.
2017-08-18 11:09:41 3508 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.

1. Swicth MySQL version to your old version.
2. Backup your databases.
3. Switch MySQL to the new version
4. restore you databses.


NOTE: Only your databases, not those used by MySQL iteslf.

NOTE2: You may need to re-create the user accounts in MySQL that were in the old version of MySQL

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Ok, thank you - I will maybe try giving that a go when I have a free moment.

Many thanks for all your help on this issue.