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.
Related
I am trying to install Oracle Client 19c when i starts the installation its freezes at stage 1, checked logs it hangs on "INFO: Checking whether the IP address of the localhost could be determined...", i refer some article to skip stage mentioned step but it also stuck on stage 7.
My System is in Domain
I tried the installation on recently formatted System and it worked with antivirus.
also tried to disable the Antivirus from my system but faced the same freezing issues. if unjoin the Domain and try it works.
I suspect the issue with any Domain Policy but dont understand the which policy is creating the problem, please suggest the solution.
If you are seeing "Reading from the pipe" message in ...\Inventory\logs OUT files then, login Windows with an admin account and run the services called "Server" and "Workstation".
I added in Coldfusion administrator => Java and jvm => JVM arguments -Dfile.encoding=UTF8 and application server service not starting.
Here is the error. So is there a way to undo what I have done. Because there is no way access to the Administrator panel.
For those, who would encounter the same problem,
open the ColdFusion10\cfusion\bin\jvm.config file as you would see the JVM arguments which you have added. I deleted the Dfile.encoding=UTF8 and service begin running again.
I have installed Adobe ColdFusion builder 2 and was able to set it up, using this tutorial
http://www.adobe.com/devnet/coldfusion/articles/setup_dev.html
After I restarted my computer (for some updates to take effect), I am unable start the server I added using ColdFusion Builder (cfserver). I get the following error -
'starting cfusion' has encountered a problem
Ensure that the server is not already running, or another application is not using the WebServer port.
Does anyone know what to do about this? I am completely lost
EDIT: This is the error the console prints out
[cfusion]:07/13 12:50:14 Error [Thread-13] - Platform, Locale, and Platform Name must not be null
If you are using Vista or Windows 7 I used to have a problem with trying to start the ColdFusion server unless I launched CFB with Administrator privileges and ran it in XP Compatability mode.
We occasionaly have a problem where we attempt to start the Jrun service and it fails with the following two errors:
error JRun Naming Service unable to start on port 2902
java.net.BindException: Port in use by another service or process: 2902
info No JDBC data sources have been configured for this server (see jrun-resources.xml)
error java.net.BindException: Port in use by another service or process: 8300
We then have to reboot the machine and Jrun comes up with no problem. This is very intermittent - happens perhaps one out of every 10 times we restart Jrun services.
I saw another reference on StackOverflow that if Windows Services take longer than 30 seconds to restart Windows shuts down the startup proccess. Perhaps that is the issue here? The logs indeed indicate that these errors are thrown about 37+ seconds after the restart command is issued.
We are on a 64bit platform on WinServer 2008.
Thanks!
We've been experiencing a similar problem on some of our servers. Unfortunately, netstat never indicated any sort of actual port conflict for us. My suspicion is that it's related to our recent deployment of a ColdFusion "cumulative hotfix" to our servers. We use the multi-server edition of CF 8.0.1 enterprise with a large number of instances on each machine -- each with its own JVM and its own distinct set of ports. Each CF instance is attached to its own IIS website and runs as its own Windows Service.
Within the past few weeks, we started getting similar "port in use" exceptions on startup, on our 32-bit machines as well as our 64-bit machines, all of which are running Windows Server 2003. I found several possible culprits and tried the following:
In jrun-jms.xml for each CF instance, there's an entry for the RMI transport layer that reads <port>0</port> -- which, according to the JRun documentation, means "choose a random port." I made that non-random and distinct per instance (in the 2600-2650 range) and restarted each instance. Things improved temporarily, perhaps coincidentally.
In the same file, under the entry for the TCPIP transport later, every instance defaulted to <port>2522</port> -- so I changed those to distinct ports per instance in the 2500-2550 range and restarted each instance. That didn't seem to help at all.
I tried researching whether ports in the 2500-3000 range might be used for any other purpose, and I couldn't find anything obvious, and besides, netstat wasn't telling me that any of my choices were in use.
I found something online about Windows designating ports from 1024 to 5000 as the "dynamic port" range, so I added 10000 to the port numbers I had set in jrun-jms.xml and restarted each instance again. Still didn't help.
I tried changing the port in jndi.properties, also by adding 10000 to the port numbers. Unfortunately this meant wiping out all my wsconfig connections to IIS and creating them again from scratch. I had to edit wsconfig_jvm.config as well, adding -DWSConfig.PortScanStartPort=12900 to java.args, so it could detect my CF instances. (By default it only scans ports 2900-3000. See bpurcell.org for details. It's an old post but still relevant.) So far so good!
My best guess is that Adobe (or MS Windows) changed the way some of its code grabs "random" ports. But all I know for sure so far is that the steps outlined above appear to have fixed the problem.
Have you verified that the services are in fact stopping? Task manager should show no instances of jrun.exe. You can also check to see what is bound to that port by opening a command window and running
netstat -a -b
This will list all your open ports, plus what program is using them. You can also use
netstat -a -o
Which does the same thing as the above, but will list the process id instead of the program name. You can then cross-reference those with task manager. You'll need to enable showing the PIDs in task manager by going to View->Select Columns and making sure PID is checked. My guess would be that the jrun processes are not shutting down in a timely fashion.
After installing VMware Server I get the following error when I try to access the VMware web-based server manager:
The VMware Infrastructure Web Service
at "http://localhost:8222/sdk" is not
responding
Go into the services manager and check that the 'VMware Host Agent' service is running. If not, then start it and then try browsing to the site again.
Vmware Hostd was not working for me either.
However, in trying to start the service it stopped automatically. Typically when this happens it is because there is an error in your config.xml.
C:\ProgramData\VMware\VMware Server\hostd\config.xml
In my case, checking the logs at:
C:\ProgramData\VMware\VMware Server
showed it erroring out after "Trying hostsvc".
Searching the config.xml for hostsvc showed references to several things, the first thing was the datastore. In checking my datastores.xml file:
C:\ProgramData\VMware\VMware Server\hostd\datastores.xml .
I found it full of all sorts of random characters instead of a properly formed XML document.
Renaming datastores.xml to datastorex.xml.bad allowed me to start the service. At which point I had to add back my datastores through the GUI.
Hopefully this will help someone else out. I did not find any other references in Google to this issue.
Try accessing via "http://localhost:8222" without the /sdk. You can also try the secure site via "https://localhost:8333".