title: ColdFusion Server Monitoring - Not Working
body: <p>I am trying to launch the ColdFusion Server Monitor on a Windows Server 2003 (Web Edition) machine running ColdFusion 8 (ver. 8,0,0,176276). It is running in stand-alone configuration. </p>
  
  <p>The pop-up window launches as <a href="http://www.mydomain.com/CFIDE/administrator/monitor/launch-monitor.cfm" rel="nofollow noreferrer">http://www.mydomain.com/CFIDE/administrator/monitor/launch-monitor.cfm</a>. However, I get a Flash dialogue box then with the error information 'ColdFusion Server is unavailable'. The dialogue box also has a place to fill out the server details (such as port number and username/password). All of this info seems in order, and again the error message is to do with it thinking that ColdFusion is not running. Obviously the CF server is available, but perhaps the server monitor can't see it. </p>
  
  <p>The interesting thing is that on some other boxes we have that run Windows Web Server 2008 and the same version of CF, we have NO PROBLEMS launching the CF Server Monitor. </p>
  
  <p>Obviously I am missing something here. Has anyone come across this issue. Any and all replies are greatly appreciated! </p>
  
  <hr>
  
  <p>Thanks Iain - many thanks for your reply. </p>
  
  <p>I can usually go to a particular machine's sub-domain to launch start CF admin and run the monitoring, for example:</p>
  
  <p><a href="http://server1.mydomain.com/CFIDE/administrator/" rel="nofollow noreferrer">http://server1.mydomain.com/CFIDE/administrator/</a></p>
  
  <p>Here I enter the my usual CF admin password. Then when I click the 'Launch Server Monitor' button it should just popup a new window. I would expect it to use the same credentials as other servers that do work, but it doesn't seem to work. Do I need to log onto the server using terminal servers and try this? Is that what you are suggesting?</p>
  
  <p>But one thing that makes me think it may not be credentials is the fact I get that 'ColdFusion Server is unavailable' message on the Flash dialogue. This suggests there is perhaps another problem. </p>
  
  <p>Does anyone know are there any log files for the server monitoring I can take a look at? I need to understand why I am getting this message!</p>