Thank you for all the feedback folks.
We have since been able to recover from this situation, by restoring the Oracle home folder from a backup prior to when this started happening...we had attempted previously to start the service manually and also from the command prompt all unsuccessfully.
I think it is closely tied in to the start sequence as well...I'll do some further digging as well.
I have seen this before and it’s was due to one of the oracle services being set to start or automatic instead of manual. Oracles process manager controls the starts and though it seems weird that one being set to automatic would make it load before process manager and prevent it from happening it did. I will look for my paperwork on this but I can’t promise I’ll find it due to it occurring well over a year ago. I’d recommend researching what services process manager controls and what their start up state should be.