@Sir, thanks for the reply and the kind regards, and sorry for my not being able to respond sooner. Besides seeing that Adobe was working more directly with you (and others), I was also on kind of a vacation last week, so while I was working, I had limited time other than that to keep up on mailing lists/forums.
I see now what you mean about thinking that the monitoring tools wouldn’t help, since this problem is about the startup of CF, and you feel you can’t get any CF requests (let alone the Admin) to process.
But note that if you look at the logs you shared, you’ll see that the CF Server Monitor feature was already functional:
Apr 30, 2014 13:39:44 PM Information - Starting Monitoring...
Apr 30, 2014 13:39:45 PM Information - Starting Monitoring Server on port 5500.
(BTW, this is from your forum thread posted on May 29, but note that the log entries refer to Apr 30. Is it that you had not tried to start CF again in the month since that error happened? Just curious.)
Anyway, note that in your case it also indicated that the monitor is listening on port 5500 (that’s an option for the monitor, on the Monitoring Settings page, which you must have chosen to enable, as by default it listens on the external web server). As such, you may find you can get into it even when you can’t get other requests to run. It’s worth a shot. Again, once you’re in it, you should be able to take a snapshot, which may show something interesting (or it may not).
As for your being on 2012 and running as DC and DNS roles, we’ve seen the others since write that they have what seem similar problems on 2k3 and 2k8, so it may not be unique to your version of Windows (and they may confirm on seeing this that they are not running as DC or DNS roles on their servers.)
Finally, again, thanks for the kind regards on your recalling how I’d helped a previous employer of yours. Sorry we didn’t get to meet then. While I can appreciate that your new employer may think this is not something they should pay for help with, I’ll just reiterate that if you don’t get it solved with Adobe, and you tried with me and we did NOT solve it, then you would NOT pay for that time. So you’d only be paying IF I helped you solve it, and I would NOT drag it on to be a long engagement. I’d not be surprised if we found something within an hour or two.
If we did, then at that point, while I can’t waive my consulting fees if it’s determined to be an Adobe bug, at least you’ll have solved it, if getting to 11 is worthwhile. It does have new features that perhaps you’re hoping to use, so you can decide if this is worth pursuing. But until then, I hope you or the Adobe folks or others experiencing this may get to the bottom of it. Again, I shared still another tool which could help, and I’d help you or anyone else best use such tools to try to get to the bottom of this. As always, though, I have also offered the info in my last reply to let those who prefer to try to work it out on their own.
/charlie