TROUBLESHOOTING TIPS
Posted by: RiggsFolly (---.as43234.net)
Date: August 17, 2015 10:49PM

Checks to be made if you have a problem after installing Wampserver.

Most of these checks can be done before installing WampServer.

Note : Do not reply to this message. Create a New discussion to describe your problem in a clear and detailed manner (With Versions of your System, Apache, PHP, MySQL, EXACT error message, etc.)

Prerequisites :
--- The Wampmanager icon in the taskbar MUST be GREEN.
--- If the icon is not green, there is no point expecting everything to work as it means that one of both of the Apache/MySQL services has not started.
--- Read ALL this document, do not stop at the first problem you have.
--- In order to be sure you are working on the right file, it is imperative to be able to "see" hidden files and all extensions. To do this, launch Explorer -> Tools -> Folder Options -> View and check:
- Show files, folders and hidden drives is checked
- Hide extensions of known file types is unchecked

Note :
- "Offline" Does not mean that Apache is down. It means that Apache is configured to only accept connections from the PC running WAMPServer.
- "Online" means Apache is configured to accept connections from any ip address. As long as you have not port forwarded your router in reality this just means any IP address in your local network. If you do port forward your router this means any ip address in the universe. This is not recommended for beginners however much you want to show your friends what you have done.

- 01
- If you are trying to upgrade your existing version of WAMPServer to a newer version or the latest versions
- - Did you follow this post Installing a new release of Wampserver, If not, it may not be too late to do so!

- 02
- You must install WAMPServer as an Administrator (This is an Absolutely must)
- - Right-click the install *.exe file and select "Run as Administrator" from the menu.

- It is highly recommended to install Wampserver at the root of a partition (C:\Wamp, D:\Wamp, etc) and do not use an installation folder name with spaces or diacritical characters. So do not install in "Program Files".

- 03
- Do you have Skype installed or running?
- - If so, it is imperative to change the Skype configuration to NOT use port 80 or 443.
- - Do this by starting SKYPE and using the menus do - Tools -> Options -> Advanced Settings -> Connection:
- - Uncheck "Use ports 80 and 443 as an alternative."
- The Windows 8/8.1/10 tiled app versions of SKYPE may not allow you to change this, so uninstall the tiled app and install SKYPE from a download, it will work just the same, but it will also allow you to make the above configuration changes.


- 04 - If Wampserver icon is not GREEN, it is because one or both the services (Apache/MySQL) has not started.
What service(s) is(are) not Started?
- To check from the Services Manager: click Start, Run, and type services.msc or Administration Tools->Services and check the status of wampapache and wampmysqld services (or wampapache64 and wampmysqld64 with Wampserver 2.5 64 bit)
- 05 - Always check, with the Services Manager that there is no Apache or MySQL services OTHER THAN wampapache(64) and wampmysqld(64) (See Note 1)

- 06 - Do you have other "php.ini" files on your system not contained in the wamp tree? If so, delete them.
- To check it in command line: Start, Run, cmd.exe
-- Go to the root of the disc CD / then Enter
dir /s php.ini


- 07 - Are there other "my.ini" files on your system not contained in the wamp tree? If so, delete them.
--- The search procedure is similar to php.ini

- 08 - Do you have IIS installed?
(XP) Control Panel, Add/Remove Programs, Windows Components
(W7/W8/W10) Control Panel, Programs and Features, Turn Windows features on or off
(XP/W7/W8) Uncheck :
-- Main Web Internet service instance (IIS)
-- All items of the branch : Internet services(IIS)
-- All items of the branch : Activation Windows service process
(W10) Uncheck :
-- Main instance Web of Internet Information Services (IIS)
-- All items of the branch : Internet Information Services

- 09 -In the file "Windows\System32\drivers\etc\hosts" you MUST have the following lines active that is to say not starting with # comment symbol. Some malware tools place a large number of bad sites in the HOSTS file to stop you ever accessing them. It is OK to leave those in the hosts file, but ensure the entries below are also there.
You are a Systems Administrator now, so it would be a good idea to know something about the use of the host file

127.0.0.1 localhost
and exist only once.
ONLY if your system and your network supports IPv6 you can add a second line:
127.0.0.1 localhost
::1 localhost

Note: 09-1 : By default, the hosts file is provided with the system attributes: hidden, read-only. It is therefore imperative to remove these attributes before you want to edit. Also some AV/Firewall apps also add protection to the hosts file. You may have to check if you are using one of these, so you can allow access to this file while you are making amendments. (See 10)

Note: 09-2 : Support of Ipv6
To see if your system supports IPv6, open a command window and run in this window the ping
Test for IPv4
C:\Windows\System32>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
We can see that the four test 127.0.0.1 have been received, without any loss.
Test for IPv6
C:\Windows\System32>ping ::1

Pinging ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
We can see that the four tests have all been received, without any loss, so the system supports IPv6
If your system or connections (WiFi, Internet, etc.) do not support IPv6 or if you are unsure, disable the Internet Protocol Version 6 (TCP / IPv6) in properties of all your network connections.

- 10 - Make sure your antivirus or protection system does not block access to:
-- file Windows\System32\drivers\etc\hosts
-- wamp\Wampmanager.exe
-- wamp\bin\apache\apache2.2.x\bin\httpd.exe
-- wamp\bin\mysql\mysql5.x.y\bin\mysql.exe
-- wamp\bin\mysql\mysql5.x.y\bin\mysqlcheck.exe
-- wamp\bin\mysql\mysql5.x.y\bin\mysqld.exe
-- wamp\bin\php\php5.3.x\php.exe

- 11 - Any other installation of a server (EasyPHP, XAMPP, IIS, or other) is incompatible with Wampserver and must be uninstalled completely before installing WAMPServer.

- 12 - Are there any ERRORS in MySQL or Apache log file? (Log files are in the /wamp/logs/ folder)

- 13 - Are there any errors in the Windows Event Viewer?
(Using the Event Viewer: [www.sevenforums.com])

- 14 - Make sure your firewall and your antivirus protection permits (and do not prohibit) the access to ports 80 and 3306

- 15 - If you have previously uninstalled Wampserver, verify that both services wampapache(64) and wampmysqld(64) had been deleted before installing a new version? (See note 1)

- 16 - Install Wampserver 64bit ONLY if you have a Windows 64bit Operating System, in this case, always take the latest version of WampServer.
-- With 64-bit Apache, PHP and MySQL and all extensions and modules must always be compiled 64bit Thread Safe.
Nota 16-1 : Apache and PHP in 64-bit versions are considered experimental and are reserved for Geeks and especially not for beginners, especially since they bring absolutely nothing more to the environment than the 32bit versions. And in fact you may have trouble getting some of the less mainstream extensions compiled for the 64bit Apache and/or PHP.

- 17 - Access to PhpMyAdmin message "Forbidden You don't have permission to access /phpmyadmin/ on this server."
Edit "wamp\alias\phpmyadmin.conf" file
If you use Apache 2.2.x, remplace
Allow from 127.0.0.1
by
Allow from localhost 127.0.0.1
or, if your system supports IPv6, by
Allow from localhost ::1 127.0.0.1
******* With Apache 2.4.x it is only :
Require local
For :
- Consider Apache 2.2.x and Apache 2.4.x
- Have some additional capabilities without modifying php.ini
you can have a file wamp\alias\phpmyadmin.conf which contains:
Alias /phpmyadmin j:/wamp/apps/phpmyadmin4.x.y/

<Directory j:/wamp/apps/phpmyadmin4.x.y/>
	Options Indexes FollowSymLinks MultiViews
  AllowOverride all
  <ifDefine APACHE24>
		Require local
	</ifDefine>
	<ifDefine !APACHE24>
		Order Deny,Allow
    Deny from all
    Allow from localhost ::1 127.0.0.1
	</ifDefine>

  php_admin_value upload_max_filesize 256M
  php_admin_value post_max_size 256M
  php_admin_value max_execution_time 360
  php_admin_value max_input_time 360
</Directory>

- 18 - Access to localhost gives "Forbidden You don't have permission to access / on this server."
-- For Apache 2.2.x
Edit the file "wamp\bin\apache\Apache2.2.xx\conf\httpd.conf" and replace
Allow from 127.0.0.1
by
Allow from localhost 127.0.0.1
or, if your system supports IPv6, by
Allow from localhost ::1 127.0.0.1
-- For Apache 2.4.x
The file "wamp\bin\apache\Apache2.4.xx\conf\httpd.conf" must has only :[/b]
Require local

- 19a - If you have set a password on the root username via the Privileges option of phpMyAdmin or the MySQL Console, and you no longer have access to phpMyAdmin with the message: "MySQL replied:#1045 - Access denied for user 'root'@'localhost' (using password: NO)"
Completely replace the file "wamp\apps\phpmyadminx.y.z\config.inc.php" (x.y.z denote the version number of PhpMyAdmin) :
<?php
/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *                config.inc.php file for PhpMyAdmin               *
 * phpMyAdmin initially load the libraries/config.default.php file *
 * then overwrites those values with those of the config.inc.php.  *
 * It is therefore not necessary to include all values in the file *
 * config.inc.php.                                                 *
 * Are set as that different from the defaults.                    *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * **/
//Extension to be used (By default mysqli - can be mysql)
$cfg['Servers'][1]['extension'] = 'mysqli';
/*
 * First server
 */
$i++;
/* Authentication type */
$cfg['Servers'][$i]['verbose'] = 'mysql wampserver';
$cfg['Servers'][$i]['auth_type'] = 'cookie';
/* Server parameters */
$cfg['Servers'][$i]['host'] = '127.0.0.1';
$cfg['Servers'][$i]['connect_type'] = 'tcp';
$cfg['Servers'][$i]['compress'] = false;
/* Select mysql if your server does not have mysqli */
$cfg['Servers'][$i]['extension'] = 'mysqli';
$cfg['Servers'][$i]['AllowNoPassword'] = false;
This will cause phpMyAdmin to throw a login page each time you run it. User Username=root and Password=blank if you have not set a password or use the new password if you have set one. This also allows you to create new MYSQL Username/Passwords and test they work from the phpMyAdmin login page.

Note 1: If you have not set a password, the line $cfg['Servers'][$i]['AllowNoPassword'] = false; must be commented out, using // at the beginning of the line.

Note 2: This line $cfg['Servers'][$i]['extension'] = 'mysqli'; tells phpMyAdmin to use the mysqli_* PHP database access extension. Ensure that the extension "php_mysqli" is loaded on the PHP extensions menu. For information, the mysql_* extension is deprecated for PHP >= 5.6.0 and is completely removed in PHP 7 or greater.

- 20 - Systematic error "Tray Menu Aestan has encountered a problem and needs to close" when launching Wampserver
Or sometimes white pages (no loaded page) to localhost and/or PhpMyAdmin

The "old" versions of Wampserver were compiled VC6 (Microsoft Visual C ++ 2005)

Recent versions (thus also recent versions of Apache, PHP or MySQL) are compiled VC9 (Microsoft Visual C++ 2008), VC10 (Microsoft Visual C++ 2010), VC11 (Microsoft Visual C++ 2012) and even VC14 (Microsoft Visual C++ 2015) for PHP 7
We must therefore ensure that you have installed the latest versions of all "package" Microsoft Visual C++

Make sure you are "up to date" in the redistributable packages VC9, VC10, VC11, VC13 and VC14
Even if you think you are up to date, install each package as administrator and if message "Already installed", validate Repair.

The following packages (VC9, VC10, VC11) are imperatively required to Wampserver 2.4 and 2.5 and 3.0.0, even if you use only Apache and PHP versions VC11 and VC13 and VC14 are required for Apache 2.4.17 and PHP 7
    VC13 Packages (Required for Apache 2.4.17 and PHP 7)
    Windows 7 Service Pack 1; Windows 8; Windows Server 2008 R2 SP1; Windows Server 2012; Windows Vista Service Pack 2
    The two files VSU4\vcredist_x86.exe and VSU4\vcredist_x64.exe to be download are on the same page:
    Visual C++ Redistributable Packages for Visual Studio 2013
    VC14 Packages (Required for Apache 2.4.17 and PHP 7)
    Windows 10, Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2003 Service Pack 2, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012, Windows Vista Service Pack 2
    The two files vcredist_x86.exe and vcredist_x64.exe to be download are on the same page:
    Visual C++ Redistributable Packages for Visual Studio 2015 Update 3
- 20-a You may also need to install
    Update for Universal C Runtime in Windows
    Windows 10, Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012, Windows Vista Service Pack 2
    Follow the links on this page for your specific environment
    Update for Universal C Runtime in Windows

If you have a 64-bit Windows, you must install both 32 and 64bit versions, even if you do not use Wampserver 64 bit.

WARNING : Sometimes Microsoft disables surreptitiously certain pages on VC ++ redistributable packages, without redirecting and without specifying the new page. You can find all the necessary files onhttp://wampserver.aviatechno.net/ in section Visual C++ Redistribuable Packages.

It may be that if you were not "up to date" with the redistributable packages VC9, VC10 and VC11 before installing WampServer, it has not been properly installed and that even this update does not resolve your problem. We must therefore uninstall Wampserver and verify that both services wampmysqld and wampapache (wampmysqld64 and wampmyapache64 for Wampserver 64 bit) no longer exist - if necessary remove them, see Note 1.
Restart the machine and install Wampserver.
- 20-b - Verify that all VC ++ packages are installed and with the latest versions.
To do this, use the tool:
Checks VC++ packages installed
And you will find all the packages on [wampserver.aviatechno.net] in section Visual C++ Redistribuable Packages
Do not forget that if you have a 64 bit Windows, you must install both 32 and 64 bit versions of each package.
You must install each package "as an administrator", so right-click the exe file and then run as Administrator.

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
(Note 1) To remove a service:
Start, Run, Type "SC DELETE <service name>"
Or open a command window As an administrator and type the command above in this window. It is imperative that the commands of deletion of services are performed as Administrator , otherwise the deletions will not occur.
---------------------------------------------------------------
(Note 2) To Edit the hosts file and rights, not only must be in as an administrator, but in addition, you must verify that such administrator is owner of C:\Windows\System32\drivers\etc\hosts.
I know it sounds silly, but the administrator is not necessarily the owner of the file.
(In principle, this file owner is "System"winking smiley
1) To change the permissions of a folder or file, you must:
- Be awarded the "total control" over this folder or file
- Or be the owner (or be a member of the group that owns it), allowing THEN to assign full control of this folder or file.
2) To be the owner of a folder or file, you must:
- Or by the creator
- Or belong to the Administrators group, allowing the change of the owner, therefore, to declare as the owner.
So Explorer, right-click on "C:\Windows\System32\drivers\etc\hosts", Security then Properties, Advanced, Owner.
If you are not the current owner: Edit and select the desired owner then Apply and OK twice. Once the ownership change applied, it must leave (Imperative) the properties window for this to be updated.
Back to file properties "C:\Windows\System32\drivers\etc\hosts" Security tab, select the new owner and verify that Full Control applies, otherwise Modify to choose the new owner and validate Full Control.
It is only from there that you can change permissions on the file and remove the read-only.

In addition, under 64-bit Windows, if you use a text editor or 32 bit software to open the hosts file, it may be that you are faced with a file open dialog, that will in windows/system32/drivers/ not show you sub folder etc, and therefore no hosts files. This is due to the fact that with a 32-bit software on Windows 64 bit, when you choose the folder system32 you are redirected transparently on the SysWOW64 folder while viewing the system32 folder. To choose the "right" system32 folder, you need to type (or select if visible) Sysnative instead of sytem32.
---------------------------------------------------------------
(Note 3) - Text editor ======
*Important Prerequisites About the text editor being used: To edit the files, you must use a text editor, but not just any one. Some text editors, such as Notepad (notepad.exe) in Windows, are not able to correctly view files with Unix line breaks*, others recode surreptitiously the line of type Unix in type Windows/DOS, others still change the used character sets or add headers ; However, it is imperative that the end-of-line types or the character sets of the Wampserver files are not altered, otherwise it will generate impossibilities and errors when it is used. That's why I strongly recommend to use a free, powerful text editor like Notepad++ that you can find at Notepad++ (If you use a text editor like UtraEdit, it will not be a problem).
* The characters indicating the end of lines are of three types:
- Windows/DOS : CR - LF (Carriage Return - Line Feed) Two bytes 0x0D and 0x0A
- Unix : LF (Line Feed) One byte 0x0A
- Mac : CR (Carriage Return) One byte : 0x0D
---------------------------------------------------------------
- 21 - MYSQL worked yesterday, but today I get an Orange wampmanager icon and MYSQL does not start.
- This applies particularly if you are using INNODB databases rather than MYISAM.
- Check the MySQL log, in "/wamp/logs/" If you see messages in the log saying that MySQL has tried to recover a database or a database table and failed, for whatever reason, then it is likely you have a corrupted database and MYSQL cannot start because it failed to recover the database.

- The simplest solution is to just Restore your last backup. Assuming you have a backup, which of course you do, because you are not stupid!
- If you have made the mistake of not having a backup, you should check the messages in the MYSQL Log as they suggest possible recovery mechanisms, alternatively, read the InnoDB Backup and Recovery

- To reduce the likelyhood of this happening, please make sure that you close down WAMPServer by either using the "Exit" on the wampmanager Menu
- - right click wampmanager -> Exit
- Or stop the MYSQL Service using
- - left click wampmanager -> Stop All services
BEFORE you REBOOT or CLOSE WINDOWS

21-a Why do I need to close Wampserver BEFORE shutting down Windows?
The "normal" closure of Wampserver performs the following actions:
- Stop the Apache service
- Stop the MySQL service
- Stop the mariaDB service

What happens when services are stopped "normally"?
- For Apache:
- Closing the Apache server
- Close all Apache processes
- Close the "child" server of Apache

- For MySQL or MariaDB
-- Purging the queue.
-- Dumping buffer pool(s)
-- Removed temporary tablespace data file
-- Close MySQL server

When Windows is shut down without having previously closed Wampserver, in certain cases, the services are not stopped normally, but the tasks httpd.exe and mysqld.exe are "killed" (TASKKILL).
So, queues and buffers are not run or dumped and this can corrupt databases, which can give symptoms like:
"It worked well yesterday, but it does not work today! "

---------------------------------------------------------------------------------------------
(Windows 7 Pro 32bit) (Wampserver 3.0.6 32bit)
<Apache 2.4.23/2.2.31> <PHP 7.1.2/7.0.16/5.6.28/5.5.38/5.4.45/5.3.29> <MySQL 5.7.10/5.6.17/5.5.28>
<MariaDB 10.1.21> <phpMyAdmin4.7.5> <MySQL Workbench 6.3.6.511>

Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin -- WAMPServer alternate Repo
-?-?-?- Backup your MySQL databases regularly Here is How dont regret it later! Yes even when developing -?-?-?-



Edited 14 time(s). Last edit at 10/05/2017 04:05PM by Otomatic.

Options: ReplyQuote


Sorry, you can't reply to this topic. It has been closed.