Leave a Comment:
26 comments
I am getting following error during installation of R-12 with Linux 5 (with 2GB memory). Can you please guide me about this problem.
Thanks
Syed
HTTP
checking URL = http://machine1.localdomain:8014
RW-50015: Error: – HTTP Listener is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
==========================================================
Virtual Directory
RW-50015: Error: – Http Server Virtual Directories is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
=======================================================
Login Page
RW-50015: Error: – Login Page is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
Syed, Installation failed at some points (check installation logs) or services did not start properly (check startup logs)
other issue I noticed with 2 GB memory is that 2 GB is not enough for R12 as DB’s SGA itself is 1GB and then PGA and other things like CM and JVM’s (third thing to try is , reduce SGA PGA and try )
ReplyThan you very much, you have very clear information and after a couple of hours of frustration trying to solve this problem, you have a so easy solution 🙂
Replyhi
Thanks a lot for your input.it helped a lot to come out the problems while installing!
Keep up the good works!
thanks once again! 🙂
Check and rename this file as well..
C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\hostd\datastores.xml
ReplyApós longas horas consegui resolver o problema com a ajuda das dicas dos colegas.
Simplesmente entrei no local:
C:\PROGRAMDATA\VMWARE SERVER\HOSTD
e mudei o nome dos arquivos:
– datastores
– datastores.xml.default
para
– old-datastores
– old-datastores.xml.default
Fui em serviços do windows e startei o:
VMWARE HOST AGENT
Fiz isto em um SERVER 2008 64.
ReplyThanks for pointing out the service names. Restarting them fixed the issue, it seems a different IP via DHCP confuses VMware Server as it expects the Host OS to have static I guess.
ReplyThank you! I’ve been searching for a solution for several days, and this is the only one with the answer.
ReplyThanks a lot. Spent lot of time figuring what the issue maybe and stumbled on this site.You really are the best
ReplyHello Atul,
I am having the same problem. Today morning I was able to open VMware and allow of the sudden it stopped working. Two days back I installed Loopback adapter to install Oracle 11g R2 on Windows 7. I was not able to install Oracle 11g R2 so I disabled Loopback adapter and all of the sudden VMware was not working.
When I again enable the loopback adapter it started working.
Can you explain me what exactly happened. I want to disable the loopback adapter and use the previous settings. Is it possible to do that?
Thanks
ReplyI believe this is the fix you’re looking for
http://www.n2networksolutions.com/2011/02/21/vmware-server-503-service-unavailable-fix/
ReplyI have the same issue with Windows 7 x64, and fix it with this instructions:
ReplyHi Atul,
I have installed vmware server 2 on windows vista (64-bit) os. vmare hostd agent was working fine and when I tried last week after long time, my browser not able to connect to hostd agent.
After troubleshoooting, i found my hostd agent service is not started. I tried manually but it gives me following error.
“The VMware Host Agent service terminated with service-specific error 4294967295 (0xFFFFFFFF).”
I do not have datastores.xml anywhere in my c drive. Also, I do not able to find %SYSTEMROOT%\VMware\ VMware Server\ hostd\ datastores.xml file.
Please help. Thanks in advance.
ReplyThe file “datastores.xml” is located C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\hostd and follow the instructions by Atul Kumar to move it.
ReplyThanks for posting this. I was running into the same error and replacing the datastore.xml file did the trick for me. Thanks!
Jeremy
ReplyThanks: it worked for me.
In event viewer it was an uncomprensible error %%-1.