cancel
Showing results for 
Search instead for 
Did you mean: 
marios
Level 7
Report Inappropriate Content
Message 1 of 6

Unable to open ePO 4 console

I have a windows 2003 server sp 2 with epo 4 patch 2 and MS SQL 2005 express . All of a sudden, i am unable to start the console.

The following error messages appeared in the Application event viewer:

Source: MSSQLSERVER
Type: Error
Category: 4
Event ID 17806
Description :
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT:my eposerver IP]

Source: MSSQLSERVER
Type: Failure Aud
Category 4
Evend ID: 18452

Description:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT:my eposerver IP]

When I open the epo console I got the following messages


GROUPSHD6000 - Dependency EPOCore had initialization error
scp - Dependency CommonEvents had initialization error
AvertAlerts - Dependency scheduler had initialization error
LYNXSHLDPARSER - Dependency core had initialization error
GSD7REPORTS - Dependency core had initialization error
SPAMKILR2100 - Dependency EPOCore had initialization error
VIRUSCANREPORTS - Dependency EPOCore had initialization error
Notifications - Dependency PolicyMgmt had initialization error
VIREXREPORTS - Dependency core had initialization error
remote - Dependency core had initialization error
SITEADV_1500 - Dependency EPOCore had initialization error
EPOCore - Dependency scheduler had initialization error
help - Dependency core had initialization error
SMDWIN__7000 - Dependency ComputerMgmt had initialization error
aramid - Dependency CommonEvents had initialization error
VIREXUB_8500 - Dependency ComputerMgmt had initialization error
LYNXSHLD1300 - Dependency EPOCore had initialization error
EPOAGENT3000MACX - Dependency EPOCore had initialization error
NSHLDNW_4600 - Dependency EPOCore had initialization error
EPOAGENTMETA - Dependency ComputerMgmt had initialization error
scheduler - Dependency console had initialization error
LYNXSHLD1400 - Dependency EPOCore had initialization error
EPOAGENT3000LYNX - Dependency EPOCore had initialization error
VIREX___7700 - Dependency ComputerMgmt had initialization error
EPOAGENT2000NVNW - Dependency EPOCore had initialization error
ComputerMgmt - Dependency scheduler had initialization error
LYNXSHLD1500 - Dependency EPOCore had initialization error
PolicyMgmt - Dependency scheduler had initialization error
console - Dependency core had initialization error
VIRUSCAN8600 - Dependency EPOCore had initialization error
VIRUSCAN8000 - Dependency EPOCore had initialization error
SKE2REPORTS - Dependency core had initialization error
rs - Dependency console had initialization error
RepositoryMgmt - Dependency scheduler had initialization error
core - Error creating bean with name 'core.db' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.mcafee.orion.core.db.base.Database]: Constructor threw exception; nested exception is java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
GSE6REPORTS - Dependency core had initialization error
CommonEvents - Dependency ComputerMgmt had initialization error


Can you please let me know how can I resolve this issue.
Thanks for your time
5 Replies

RE: Unable to open ePO 4 console

Did you change anything on your eposerver such as the name or anything else?

Go to https://your_epo_server:8443/core/config and review your SQL settings
marios
Level 7
Report Inappropriate Content
Message 3 of 6

RE: Unable to open ePO 4 console

Thanks a lot

My username was located on the username of the database. I do not know how I made this happend.
I replaced it with the domain admin and the problem is solved.

Thanks a lot for you time !!!

RE: Unable to open ePO 4 console

I had this very same problem. This happened right after I did a Windows Update. There weren't many things installed, see the following:
* Security Update for Windows Server 2003 (KB958690)
* Security Update for Windows Server 2003 (KB960225)
* Security Update for Microsoft XML Core Services 6.0 Service Pack 2 (KB954459)
* Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB954430)
* Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)
* Hewlett-Packard Company - Networking - HP NC7760 Gigabit Server Adapter

, but after i did this, i was not getting access to the Orchestrator.

All I had to do was go to https://your_epo_server:8443/core/config and re-entered the password to access the db in the field, then I restarted the server.

Hope this info is helpful to others out there. I don't know if anyone out there can shed any light on why this would have happened

RE: Unable to open ePO 4 console

Make sure your database server is running and connecting to ePO server. I had the same case before. In fact, both ePO 4.0 server and database server are running fine. The reason is that when I planned to restart both server for test, the ePO services start before the SQL services start. So that the same error occured and just restart ePO services to let SQL connection run again. Then, logon OK.

RE: Unable to open ePO 4 console

A bit late reply for somebody looking for a solution like me:
The options I found on the Internet didn't solve my problem. What I did was mayby a dirty solution but I renamed the file C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Data\ePO4_EPO_log.LDF (first stop the sql service). When you open the EPO console then automatically a new ldf is created. EPO is now running ok again
More McAfee Tools to Help You

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community