Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ePO Server down for the count...HEEEEEELLLLP!!!

Status
Not open for further replies.
Sep 16, 2003
76
US
Hello All,


Here's the deal:

The server I'm running ePO on has experienced problems in the past such as locking up and rebooting on its own. Today I went to log into the server and it locked up, so I figured this was typical and proceeded to give it a hard reboot. It seemed to come back up fine, but once I logged in I found out to my horror that ePO would not boot due to an unknown error! I tried to manually start the service, but I get the error:

"Could not start the McAfee ePolicy Orchestrator 3.0 Server service on Local Computer. Error 2147500037: Unspecified error."

So I looked in Event Viewer and there is an event ID: 7023 with the ultra clear description:

"The McAfee ePolicy Orchestrator 3.0 Server service terminated with the following error: Unspecified error."

Has anyone ever had this experience? Is there anyway to repair the installation? Any help is VERY MUCH appreciated!! =)


Thanks,


Jay
 
Thanks for the reply P3dr0, but after getting frustrated I started rebuilding the server... =(

Thanks again,


Jay
 

I've had this same problem on several occasions. I'm still trying to figure out why it is happening but suspect it has something to do with licensing.

I can get ePolicy up and running by restarting the database and then starting 'McAfee ePolicy Orchestrator 3.0 Server'.
 
Are you running your ePO database on an SQL server? If so, check the log size. On ePO 2.5.1, I had this problem where the server would drop out if the database log file filled up. Strangely 3.0 didn't have same problem (not sure if logging was turned on). 3.0.1 doesn't kill the server if the log fills up (problem back sort of) but it just quits doing anything.
 
I had a similar problem. It was caused by the username that the epolicy orchestrator was using to access the sql database having the password changed. run cfgnaims and change the username pword domain to a valid one.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top