Having a bit of trouble with my ePO and thought this may be the best place to start. Will lay out the background before the problem because it may help for responders.
I am active duty military working at a small unit in the middle of nowhere. We have a legacy network which is required to provide critical functions. Because it is legacy and not our main network, there are very few users and only a handful of servers on it. HBSS/ePO are on it because it is a requirement for all DoD Networks, legacy or not. I am an electronics tech with a couple IT certs. The command determined I was the 'most qualified' to replace the sole HBSS admin. The civilian HBSS admin resigned because her spouse was military and transferred, but was able to give me a 1 week crash course on the ePO.
So there we are. I've touched it, I've poked it, but primarily tried not to break it. It sits on a legacy network that provides a critical function, so doing the wrong thing in HBSS/ePO has the potential to break that function. So I treated it like a firewall for the most part, looking and checking up on it... But not really digging in or making changes to see what would happen. After about 60 days sitting in the primary SysAdmin seat, I was recalled back to the antenna field to fill holes there as well, as a few personnel had left. Electronics Tech sometimes translates to 'everything tech'... Made evident as 60 days after that I am back in the SysAdmin/HBSS seat which has been vacant the last 2 months. I was called upon again because some patches are due. And my initial findings...
Upon reaching the server, "number five" which hosts both the SQL database and ePO, I found that it was still locked out with my user name and password from when I had departed SysAdmin 2 months prior. So no one has touched it. "Five" also has RDP disabled and can only be accessed locally, so I am fairly certain nothing has happened user/admin wise with 5 since I left. When I unlocked the system the ePO dashboard was already up, but unresponsive. There were some other items not responding as well so I decided to do a reboot.
After reboot, before logging in there was a "one or more services failed to start.... see event viewer for details" popup. I logged in, checked the event viewer, and while I didn't find any service errors, I did find numerous "failed audit" errors. 441,000 in the past 9 days... But no one had logged into the machine in at least 45. The error (paraphrased) says "The user '' does not have an authorized SQL profile". The logs wouldn't go back further because of the quantity of errors. Lower down on the error it specifies that it's server 5 and my login name. Shouldn't be an issue, it all worked before. I can also access SQL studio with my login and recieve no errors or challenges.
Starting the ePO results in about 50 errors in red below the login prompt, and also will not allow me to login. All I know about SQL is that it's a database. I don't think anyone here knows SQL well either. But I'm not entirely sure this is solely a SQL error... So... Where to begin troubleshooting?