Nov 07, 2005
PGP Conflicts with JRun Web Server Configuration t
Posted by Steven Wood having to do with Tips & Tricks
Posted by Steven Wood having to do with Tips & Tricks
Today I was tasked with setting up a new website (Jrun server) on our Coldfusion MX 6.1 servers. I was following my setup documentation when I got to the point where I needed to connect my Jrun server to my IIS website. Upon running the JRun Web Server Configuration tool, I received the following error:
We maintain 2 Coldfusion servers and BOTH of them were giving me this error. I had never seen it before. What had changed on the servers? Last week, the latest version of PGP Desktop had been installed on both servers.
I uninstalled PGP Desktop on one server and rebooted. The Web Server Configuration tool ran fine.
I don't know exactly what is going on here, but obviously the PGP install was somehow interfering with certain ports that were supposed to be accessible by the config tool.
Created file C:CFusionMXuntimelibwsconfigjrunwin32.dll
Could not connect to any Jrun/ColdFusion servers on host localhost.
Possible causes:
Server not running
-Start Macromedia JRun4 or ColdFusion MX server
Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or
firewall on server
-host restriction in security.properties blocking communications with
server
Press any key to continue...
Could not connect to any Jrun/ColdFusion servers on host localhost.
Possible causes:
Server not running
-Start Macromedia JRun4 or ColdFusion MX server
Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or
firewall on server
-host restriction in security.properties blocking communications with
server
Press any key to continue...
We maintain 2 Coldfusion servers and BOTH of them were giving me this error. I had never seen it before. What had changed on the servers? Last week, the latest version of PGP Desktop had been installed on both servers.
I uninstalled PGP Desktop on one server and rebooted. The Web Server Configuration tool ran fine.
I don't know exactly what is going on here, but obviously the PGP install was somehow interfering with certain ports that were supposed to be accessible by the config tool.
