Most of us who runs an Apache server using WAMP or XAMPP, have once upon a time run into this error Could not execute menu item (internal error). I must admit it has given one or two headaches in the past, but luckily I have found a easy fix that resolved the problem for me in no time at all. Since my original solution was a bit specific, I decided to add 2 more.

“Wamp Could not execute menu item” – Solution 1

Some of the following applications can cause conflicts with Wamp. If you are running any of these, please close them and restart all services on Wamp. These are: IIS, Skype, Zone Alarm, NOD32, Eset, Internet Optimizer, Google Accelerator, Xfire, steam, other database servers. Im not saying they are causing the problem, but one of these could.

“Wamp Could not execute menu item” – Solution 2

Click the wamp icon in the bottom right hand corner of your screen, then apache and then open the httpd.conf.
 
Scroll down a bit and find the lines:
 

Listen 12.34.56.78:80
Listen 80

 
and change them to
 

Listen 12.34.56.78:80
Listen 8080

 
Ok, so if none of the above works, here is my original solution that worked for me in my quest for solving the problem. (Thanks to emalik’s blog for solution 1 & 2)
 

“Wamp Could not execute menu item” – Solution 3

The very simple solution is to uncheck the “Enable LMHOSTS Lookup” box in the TCP/IP protocol setup (under WINS setting). Here are the steps to do this:

1. Open “Control Panel” then “Network Connections.”

2. Right-click on “Local Area Connection” and select “Properties.”

3. Double-click on the “Internet Protocol (TCP/IP)” line to open the “Properties.”

4. On the “General” tab, click the “Advanced” button.

5. Select the “WINS” tab and uncheck the “Enable LMHOSTS Lookup” box.”

Now, check the Apache test page at http://localhost/. This time, it should work!

NOTE: If your "Enable LMHOSTS Lookup" Box is unchecked from the start, I have found that if you check the box and close the window and then once again go in and uncheck the box, it fixes the problem as well.

Please visit the blog I found the solution on here

(7 votes, average: 4.29 out of 5)

 Loading ...