Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
1) I have installed 32 bit version wamp 2.2E, on windows XP 32bit. The icon is currently orange. I do not have skype.
2)The windows hosts file does have the line:
127.0.0.1 localhost
3a) Trying to enter //127.0.0.1/ in the browser results in error:
"Navigation to the webpage cancelled"
3b) or //localhost/ results in error:
"Access denied"
4)Apache and PHP error logs are empty even after restarting services.
5) restarted under services.msc the service "wampmysqld", doesn't help
6) stopping first then restarting all services doesn't help [I should add the icon has never been green from the first installation of wamp has been going to orange]
Please note this happens because there is some other application running on port 80 , which is used by wamp.
You can check by wamp-> apache-> service -> Test port 80. It will list out applications used by port 80.
In our case IIS server was running http service, so start task manager, first click show all processess, put a stop to HTTP
After this fix i got IIS page issue on localhost which got solved when we did below step check in your hosts file in WINDOWS folder, if entry 127.0.0.0 localhost is commented then uncomment it by removing # infront of that line.
Problem solved:
I downloaded the older version wampserver 2.1e - and bam, it works.
Note: during the installation process, the windows firewall popped up and asked me if I wanted to continue to block certain elements from apache http, I chose unblock, and bam it works! Now I wonder if that was the problem with 2.2e, if I needed to go into the firewall and something is blocking apache.
Make sure applications like Yahoo Messenger, Skype, or ICQ are not running when you try to start WAMP. If any of the 3 apps are running, WAMP will fail to start because for some reason they also use the local address. Stop the apps first, restart WAMP, and when it is green, you may restart your IMs. Hope this helps.
You can often get stuck in this position when the wamp services are not running correctly. From the start menu run "services.msc" look for any services that mention wamp (sort alphabetical) and ensure they all say "started".
If this still doesn't work try stopping the services for wamp and restarting them, it may take a moment or two for the menus to refresh and work.
Related
I know this is similar to a lot of questions on here, but I feel it's worth a new question since I have yet to discover a question that fully encompasses my problem. I've been struggling with this for a couple weeks, read pretty much every answer to every question about it on here, as well as countless blogs, articles and other Q&A forums. So, here goes:
I created a service to monitor several things on our network and update a database with the information. Moved it to a server and went threw a lot of frustration with getting the WMI and DCOM settings right so that it would work.
I recently had my computer crash on me and so I lost my code and had to recreate the service from scratch/memory. It runs perfectly fine on my laptop. I moved it to a server(different than the one that is running the old version of the service). It runs there, but it is unable to reach the PCs I am monitoring. I try running the command line WMI query and can't connect there either. Getting the 'RPC Server is unavailable' error.
I've tried changing settings as per all of the articles/answers I've been able to find and cannot get it to connect.
A few relevant things:
All the RPC/WMI related services are running on both server and
monitored PCs.
The firewall is disabled on both server and monitored PCs.
I know the user and password are correct and have admin rights
on monitored PCs.
Server in question is (I believe, will confirm with someone later)
Windows Server 2008 R2 on a virtual server, if that makes a
difference.
Able to ping PCs and run tracert from server.
Here's where it doesn't make sense to me. I am able to run the wmic command from my laptop to the monitored PC. And from my laptop to the server. Wmic works locally on the server, but whenever I try to make a remote call, it fails with the RPC error.
I don't know much about networking, and we are a small company so we don't really have a Network Admin or anything. So, any and all advice would be appreciated.
Ok, I have a quick question to ask all the veteran Wamp users on this board.
At work, we are currently working on a web application. We are trying to use Wamp to design everything, but we have a problem. All the computers right now have wamp installed to the default location (C:/wamp).
Our problem is, we all want to have access to the same MySQL database so we can edit it at the same time. Right now, only one person can edit it at a time to prevent losing the work of someone else.
When done, we just dump the mySQL folder onto a network drive so whoever wants to edit it next can take it and use it.
This isn't very time efficient, so we're wondering if its possible to install Wamp directly to a network drive in some way. We tried doing it just now but we can't get Wamp to start services.
So any type of advice will be helpful
i think these two thing would help you :
1: install wamp in only one system then in apache configuration file listen to his lan ip in order to others can access it in this way you have just one database server
2: as you've installed wamp to all systems choose one system's database as main and in mysql configuration define a new server wich server's ip is that system's lan ip
then users instead of using localhost for connecting to mysql will use that ip
I have a previously installed ColdFusion 10 Multi-server installation that is up and running well. When I create a new instance, via the ColdFusion Administrator, with "Create Windows Service" checked, all seems to go well; the new instance shows up in the Administrator and the new directory structure is created on the server, but the new instance won't start. If I go to the Windows Services panel, on the server, and try to manually start the new service, I get:
Windows could not start the ColdFusion 10 Application Server newServer on Local
Computer. For more information, review the System Event Log. If this is a
non-Microsoft service, contact the service vendor and refer to the service
specific error code 2.
The Windows System Event log contains the following:
The ColdFusion Application Server newServer service terminated with non-specific
error. The system cannot find the file specified.
I have searched both the web and the Adobe site for a solution, but have come up empty handed. I would appreciate any insight.
Thanks in advance.
Update from the comments
Starting the service from the command prompt I see this error:
C:\ColdFusion10\newServer\bin>coldfusion.exe -start -console
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197):
No transports initialized [../. ./../src/share/back/debugInit.c:741]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_E RROR_TRANSPORT_INIT(197)
It could be a port conflict issue. You can check the Event Viewer logs. Try the following:-
Stop ColdFusion service
Launch Command prompt as Administrator
Browse to cf_root\cfusion\bin and run the following command coldfusion.exe -start -console
Try to access the CF admin, once the services are started.
In case it gives an error message, please share the same.
This error was actually caused by conflicting port numbers in the debugger. Reference ColdFusion Administrator interface ==> Debugging and Logging ==> Debugger Settings. The Debugger Port must be set to a unique value for each server instance. If two or more instances are set to the same value, a port conflict results.
This worked for me. First, if you are in a windows environment use
netstat -ano
to get a list of ports in use. Then, open
c:\ColdFusion11{instancename}\bin\jvm.config and find the port address in your JVM arguments, if the port isn't unique, change it to one that is. Then fire up CF from the command line like this:
c:\coldfusion11{instancename}\bin\coldfusion.exe -start -console
Should now start properly or indicate if there is still a problem.
This happened to my local Dev install after a system update. I just tried changing the default port from 8500 to 8501 and it worked.
Maybe I can save someone else from the frustration I faced with some update I didn't explicitly authorize.... this was the cause and fix for my scenario...
JRE version On PC was updated and out of sync with CF settings JRE version...
JRE on PC and CF Settings out of sync...
Solution: updated the jvm.config file to have the same JRE version number as the version on my PC, started CF services, and Bob's your uncle.
tldr; This question was to get help setting up Micro Cloud Foundry on Windows XP behind a corporate firewall as an innovation-demonstration project for a Fortune 500 IT departent. Basically, the project stalled, despite this stackoverflow page - the magic wasn't strong enough. I am accepting #DanHigman answer below, but if anyone sees this and can provide a simple straight-forward answer, by all means...
Can anyone provide a clear step-by-step on setting up MCF on a Windows (XP in my case) machine behind a corporate firewall, for demostrating the feasibility of PaaS in the corporate IT world?
My VM is installed and running and I can use the menu ok. I have vmc working. I have a test Node.js server app, that works on local, ready to push. But I can't get past that stage.
The firewall gave me trouble so I lowered my goal to just work offline. I followed the instructions noted below as best I could, but often the instructions are mac oriented - I would like them for a Windows command line (especially SSH tunneling):
http://blog.cloudfoundry.com/2011/09/08/working-offline-with-micro-cloud-foundry/
http://support.cloudfoundry.com/entries/20332921-micro-cloud-foundry-trouble-shooting-help
This blogger may have half-way covered my problem doing the SSH tunnel settings, but all it gives is "use Putty" - more detail would help:
http://support.cloudfoundry.com/entries/20419943-using-micro-cloud-locally
Also, whenever the vmc obviously gets an error or other message, it only outputs the following in the command line:
vmc target http://api.vcap.me
<<<
[200, "<html><body>SNP/2.0/102/Unknown Command 'info'</body></html>\r\n\r\n", {}
]
>>>
Thanks for any help. BTW - I know I could do this on my mac, the big obstacle is the windows and firewall environment.
Update:
#Dan and #ebottard: Thanks to your help, I'm almost there. ping is working now, hosts file seems right, but the vmc target api.vcap.me still does not find the VM at that 192.168.253.128 IP - even tho ping does. In the first link above, Martin wrote the following, but assuming we are doing it on a mac:
After the update is complete, you will need to make some changes on your local system. What you will need to do is to set up an SSH tunnel to access your Micro Cloud Foundry VM (note that you will need to supply the IP address in the command below with the actual IP of your VM, which is displayed in the console).
sudo ssh -L 80:192.168.168.149:80 vcap#192.168.168.149
Password:
vcap#192.168.168.149's password:Â
The first password being prompted is the sudo password for your machine, as it is needed to open port 80 which requires root privileges. The second password is the vcap user password which you entered during the initial configuration of your Micro Cloud Foundry.
I need to have these instructions translated into Windows, and all I have to go on is that I might use puTTy (which I have downloaded) to do it. Any more ideas?
Looks like you're running an application on your Windows machine called "Snarl" (a poor Windows-based clone of the OS 10 app Growl :-p). It looks like it's interfering with communication to the MCF intstance, close it and have another try.
Alright, so I've downloaded wamp server before an hour. I was trying to put it online and I just couldn't. I'm getting the following exception: "could not execute menu item internal error exception could not perform service action". I was googling it and I found 2 solutions.
1 of them is to change the ports of the skype, and other programs from port 80 to another one.
I don't have any of these programs, so it's should be OK.
The second solution is to change the port of the wamp to 8080 or whatever, I tried this also and it's still not working.(The icon of the wamp is orange).
What am I doing wrong? Am I missing anything?
I use WampDeveloper Pro, so it's a bit different, but I'll assume that your problem is that Apache will not start.
You'll need to get the specific Apache error message to understand what the problem is.
Open the command line (run cmd.exe), and within type in: httpd t.
This will perform a syntax check. If it's okay, then type in: httpd -k start.
This will attempt to start Apache, and if unsuccessful, will print out the error.
If the error is something like "can't bind to 0.0.0.0:80, port already in use" (the error will be a bit more clinical than that) then you are right, something else is already taking up port 80.
In which case, type in: netstat -aon. Look for the line that says "0.0.0.0:80" and note the PID number. Then get in your Windows Task Manager (ctrl-alt-del), into the Processes Tab, click "Show process from all". Find the process that has the same PID number. This is what you need to shut down or reconfigure to listen on another port.
hey have you tried to put off any othe installed server like IIS for example ?? if you have IIS turned on go to services and stop world wide publishing service and than try restart all wamp services and then put it online it sould work :)
Mostly its Apache problem.
I had the same problem. The problem is that the port Apache is trying to use is actually being used by some other application. Either
Change the port no. from the file http.conf or httpd.conf from 80 to smething else Listen 8080 change 8080 to something else.
check out which application is using the port and shut it down. Check the port status using "cports" aplication or any other that you prefer. Then it will work just fine.