Hi Matt,
I think that the error is being reported by CF which is trying to find
the file fService.cfm. CF won't / can't find this file because it
doesn't really exist, it's a part of FusionReactor. So the question is
why is CF reporting that? Here I think the reason is that one of the
FusionReactor instances is polling this instance Enterprise metric
data (on port 80?) and FusionReactor is not active on that port.
To fix the problem I think you need to look into the FusionReactor
instance that you use for monitoring the other instances. Go to the
Manage Servers and check that all of the URL's entered are correct.
You could also look into the FusionReactor->Log for the instance that
you use for monitoring, you may find details of which instances are
not responding to being polled. You'll need to delete or correct the
server that is causing the problem in the Manage Servers screen.
Hope that's the problem and it helps,
Darren