cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Event Parser fails to start

Good morning friends

I could also help with this issue, I get in the log, connectivity problems would appreciate if you give me a hand

I copy the log

thanks

Database initialization: Starting.
RSA BSAFE  Crypto-C Micro Edition FIPS 140-2 Module 3.0.0.1
COM Error:  0x80004005
File:  .\ePOData_Connection.cpp(494)
Function:  DAL2_CConnection::GetConnection
Source:  Microsoft OLE DB Provider for SQL Server
Description:  Cannot open database "ePO4_SERVIDOR" requested by the login. The  login failed.
COM Error:  0x80004005
File:  .\ePOData_Connection.cpp(525)
Function:  DAL2_CConnection::GetConnection
Source:  Microsoft OLE DB Provider for SQL Server
Description:  Cannot open database "ePO4_SERVIDOR" requested by the login. The  login failed.
COM Error:  0x80004005
File:  .\ePOData_Connection.cpp(309)
Function:  DAL2_CConnection::Init
Source:  Microsoft OLE DB Provider for SQL Server
Description:  Cannot open database "ePO4_SERVIDOR" requested by the login. The  login failed.
DAL2_CConnection::Init:  Error 0x80004005 returned from credentials callback. Database NOT available
Database  initialization: Failed (hr=0x80004005).
Failed to  initialize database layer. Cannot continue.
EventParser  Stopped.
Cleaning up  Server...
Initializing  Server...
Database  initialization: Starting.
RSA BSAFE  Crypto-C Micro Edition FIPS 140-2 Module 3.0.0.1
Microsoft  SQL Server 2005 - 9.00.4035.00 (Intel X86)

Re: Event Parser fails to start

please read through this trail, and follow instructions to run /core/config test - and let us know the results.  From the output you have provided, this points to incorrect DB credentials.

Re: Event Parser fails to start

good morning

performed the steps requested, admission and test the connection and I get the connection to the database was successful

Re: Event Parser fails to start

Please check on SQL server, listener port and then compare it to value in https://EPO_URL:8443/core/config

Folcan
Level 10
Report Inappropriate Content
Message 35 of 39

Re: Event Parser fails to start

The Event Parser can't start because credentials to your DB are wrong.

Description:  Cannot open database "ePO4_SERVIDOR" requested by the login. The  login failed.

Go to : https://EPO_URL:8443/core/config

Test your DB settings


alexn
Level 14
Report Inappropriate Content
Message 36 of 39

Re: Event Parser fails to start

Good Morning all.

Hey, I would suggest this.

1.Check the sql port in db.properties and change it to the port in SQL Manager.

that would surely help.

Highlighted
alexn
Level 14
Report Inappropriate Content
Message 37 of 39

Re: Event Parser fails to start

OR

If you have done something with IIS then do the following

Go to Windows 2008 Server Manager, 'Roles -> Web Server (IIS) -> Add Role Services' and install 'IIS 6 Management Compatibility.

Please lem me know if it doesnt work.

robrow
Level 7
Report Inappropriate Content
Message 38 of 39

Re: Event Parser fails to start

ciberpuch,

What version of ePO and SQL is installed?

If you follow the suggestions above and go to the https://EPO_URL:8443/core/config url, test the DB connection and it is succssful and the ports listed in db.properties and the TCP Port in use in SQL configuration are the same, then I would check to ensure you have not run out of space in one of two places:

1) If the ePO installation is using the default SQL 2005 Express installation, then ensure the DB has not exceeded it's 4 GB space limitation. If it has you will need to purge some data from the DB  to provide more room.

2) Check the HDD where ePO and the DB are installed to ensure the HDD has not run out of space.

Re: Event Parser fails to start

good afternoon Robrow

The Epo version is 6.3 and SQL Server R2

My disks have plenty of space and has 16GB of ram, I commented that when services low, raise and there manually consumes 100% CPU and hangs just restarting normalizes

Also the ports are the same

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator