Either the Macromedia application server(s) are unreachable or none of them has a mapping to process

Report · Apr 18, 2010

We have been running Multi-Instance ColdFusion 9 64-bit on 64-bit Windows Server 2003 with 8gb of ram for the last 5-6 weeks with no issue.

All of a sudden the automated backups failed and there were errors about:

"Windows - Low on Registry Space"

"The system has reached the maximum size allowed for the system part of the registry, Additional storage requests will be ignored"

After a server restart, coldfusion pages/sites all displayed

"Either the Macromedia application server(s) are unreachable or none of them has a mapping to process this request."

We were unable to find anything to fix it and could not uninstall ColdFusion because it said JRun had to be uninstalled first, even after we couldn't find any more evidence of a JRun installation it still said it had to be uninstalled first.

Does this sound at all familiar to anyone? We can't get CF uninstalled/reinstalled in multi-instance set up and haven't found anything helpful through web searches.

Thanks for your time

Report · Apr 18, 2010

It sounds to me like you've got your client variables set to be stored in the registry. Despite this being the defaul setting, it's really not a suitable option for a production situation (for the reasons you are now experiencing).

Change the setting to store them in a DB, clean out your registry (I cannot remember the key under which they are stored, but it's in the docs), and things should come right.

I am not sure about the advice you're seeing to uninstall JRun before uninstalling CF. I've deinstalled CF stacks of times and the CF deinstaller has never said that was a requirement, and it's happily deinstalled JRun for me. It's not even a logical suggestion to make, as CF runs atop of JRun, so even if there was some deinstall order to consider, it would seem to make more sense for the requirement to deinstall CF first. Odd.

--

Adam

Report · Apr 19, 2010

Thanks very much Adam. Client variable storage had been switched to the DB, but I believe there may have been a software upgrade/reinstallation after that fact and that setting may have been missed at that time.

We're still not sure why we cannot get CF9 to uninstall at this point, but that probably explains the registry issue at least.

Thanks again.