A

Anonymous

Answered

Web Server Configuration Tool Fails

Forum|Forum|19 years ago
February 4, 2007
5 replies
4497 views

I remove Coldfusion MX 6.1 "Working fine" from Windows XP Professional and installed MX 7. Received an error during install about possible fire wall issues preventing complete install.

I went to the Web Server Configuration Tool to setup IIS. When I clicked the Add button I get the following message:
Could not connect to any JRun/ColdFusion servers on the host localhost. Possible causes: Server not running ---Server running and fire wall blocking JNDI ---Host restriction in security.properties.

I have virus protection turned off and window firewall off as well.

I reconfigured the jrun.xml and ColdFusion will run on its own server, but I wanted it on IIS for some testing.

Thanks in advance.

Mike

Getting started

This topic has been closed for replies.

Correct answer BKBK

Sorry Yes is to all three. I ran the two statments you gave me and this is the result.

C:\CFusionMX7\runtime\jre\bin>java.exe -jar C:\CFusionMX7\runtime\lib\wsconfig
ar -host localhost -list

Could not connect to any JRun/ColdFusion servers on host localhost.
Possible causes:
o Server not running
-Start Macromedia JRun4 or ColdFusion MX server
o Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall
on server
-host restriction in security.properties blocking communication with server

C:\CFusionMX7\runtime\jre\bin>java.exe -DWSConfig.PortScanStartPort=2920 -DWSCon
fig.PortScanCount=1 -jar C:\CFusionMX7\runtime\lib\wsconfig.jar -host localhost
-list

JRun servers: coldfusion

The first message is what I have been getting all along.

> Yes is to all three. I ran the two statments you gave me and this is the result.

We might finally be on to something. Follow the bpurcell.org link I gave you earlier and scroll to the bottom. You will see a post about Windows XP SP2 and socks.

Apparently, there is a limit to the number of open socks allowed on operating systems like Windows XP SP2 and Windows 2003 SP1. If we are to believe that, then your problem is caused by Windows XP. The default behaviour of the wsconfig tool is to scan all ports in the range 2900-3000, thereby exceeding Windows XP SP's socks limit.

One solution would therefore be to run wsconfig with a reduced number of scanned ports. Do this then on the command-line:

C:\CFusionMX7\runtime\jre\bin\java.exe -DWSConfig.PortScanStartPort=2920 -DWSConfig.PortScanCount=1 -jar C:\CFusionMX7\runtime\lib\wsconfig.jar

BKBK

Community Expert

!

A

Anonymous

Thanks BKBK,

That did the trick. I guess I owe you a beer. It is up and running.

BKBK

Community Expert

There is apparently no communication on the ports 2900-3000 on your machine. Suggests the next experiment. Turn on your Windows Firewall and configure it to open port 2920, the one you configured in the JNDI.properties file.

A

Anonymous

Sorry,
I was looking at 9920 instead of 2920. Here it is again. I've been very busy today.
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING 1412
TCP 0.0.0.0:1099 0.0.0.0:0 LISTENING 1412
TCP 0.0.0.0:2522 0.0.0.0:0 LISTENING 1412
TCP 0.0.0.0:2920 0.0.0.0:0 LISTENING 1412

Image Name PID Sess Name Session# Mem Usage
========================= ====== ================
jrun.exe 1412 Console 0 55,924 K

So it looks like it is there but still the same error.

Thanks,
Mike

BKBK

Community Expert

1) Did you save the jndi.properties file after changing that line to

java.naming.provider.url=localhost:2920

2) Did you then restart Coldfusion?

3) Did you turn on the Windows Firewall and use it to open the ports 2920 and 51011?

4) If you answered yes to 1), 2) and 3), then run the following code (in italics) at the command line, in that order

code to list JRun servers on your machine:
C:\CFusionMX7\runtime\jre\bin\java.exe -jar C:\CFusionMX7\runtime\lib\wsconfig.jar -host localhost -list

code to confirm JRun server running on port 2920:
C:\CFusionMX7\runtime\jre\bin\java.exe -DWSConfig.PortScanStartPort=2920 -DWSConfig.PortScanCount=1 -jar C:\CFusionMX7\runtime\lib\wsconfig.jar -host localhost -list

BKBK

Community Expert

2901?

A

Anonymous

Same error as 2925....

BKBK

Community Expert

1) Restore the file jndi.properties to its original state (port 2920) and save it.

2) Ensure that the default proxy port is 51011, to enable Coldfusion to connect to a web server other than its own default web server. You do so by editing the file C:\CFusionMX7\runtime\servers\coldfusion\SERVER-INF\jrun.xml. Locate the service element named ProxyService. Make the following changes within the element

<attribute name="port">51011</attribute>
<attribute name="deactivated">false</attribute>

3) Restart Coldfusion.

4) At the Windows command prompt, run netstat -an and look for the port 2920 (protocol: TCP, state: listening). If port 2920 is not in the list then it is most likely it has been blocked by the Windows Firewall. You will then have to open it.

5) Follow the procedure in this Microsoft article on the Windows Firewall to manually open the ports 2920 and 51011.

6) Restart Coldfusion.

BKBK

Community Expert

Check this bpurcell.org wsconfig article out

A

Anonymous

I did run it manually and read the articles, but this is what I get.

Could not connect to any JRun/ColdFusion servers on host localhost.
Possible causes:
o Server not running
-Start Macromedia JRun4 or ColdFusion MX server
o Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall
on server
-host restriction in security.properties blocking communication with server

BKBK

Community Expert

Coldfusion MX7's default JNDI port is 2920. Perhaps, some other process is already using that port.

Do an experiment. Locate the file C:\CFusionMX7\runtime\servers\coldfusion\SERVER-INF\jndi.properties. Edit the line

java.naming.provider.url=localhost:2920

by changing the port number to some other value between 2900 and 3000, for example, 2901. Restart Coldfusion.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded