cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Cannot access ePO 5.9, database error

Jump to solution

I went ahead and rebooted the server, here is the results of the orion log:

2019-07-01 07:05:51,947 ERROR [http-nio-8443-exec-14] base.Database - Unable to get the version from the database
java.sql.SQLException: Login failed for user 'Domain\XXXXX'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:373)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2985)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2418)
at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:646)
at net.sourceforge.jtds.jdbc.JtdsConnection.(JtdsConnection.java:365)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:180)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at com.mcafee.orion.core.db.sqlserver.JtdsJdbcDriver.getConnection(JtdsJdbcDriver.java:107)
at com.mcafee.orion.core.db.base.DriverRegistry.getConnection(DriverRegistry.java:323)
at com.mcafee.orion.core.db.base.DriverRegistryConnectionFactory.createConnection(DriverRegistryConnectionFactory.java:34)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
at com.mcafee.orion.core.db.base.DbConnectionPool$LoggingConnectionFactory.makeObject(DbConnectionPool.java:232)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
at com.mcafee.orion.core.db.base.DbConnectionPool$CountingGenericObjectPool.borrowObject(DbConnectionPool.java:183)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at com.mcafee.orion.core.db.base.DbConnectionPool.getConnection(DbConnectionPool.java:63)
at com.mcafee.orion.core.db.base.Database.getConnectionInternal(Database.java:610)
at com.mcafee.orion.core.db.base.Database.getVersion(Database.java:952)
at com.mcafee.orion.core.db.base.Database.init(Database.java:924)
at com.mcafee.orion.core.db.base.Database.(Database.java:433)
at com.mcafee.orion.core.db.base.DatabaseUtil.test(DatabaseUtil.java:402)
at com.mcafee.orion.core.db.base.DatabaseUtil.test(DatabaseUtil.java:441)
at com.mcafee.orion.core.db.sqlserver.SqlServerConfigServlet.test(SqlServerConfigServlet.java:108)
at com.mcafee.orion.core.db.sqlserver.SqlServerConfigServlet.doPost(SqlServerConfigServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:485)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:410)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:337)
at com.mcafee.orion.core.servlet.Forward.respond(Forward.java:143)
at com.mcafee.orion.core.servlet.ConfigureDatabaseServlet.handleTest(ConfigureDatabaseServlet.java:209)
at com.mcafee.orion.core.servlet.ConfigureDatabaseServlet.doPost(ConfigureDatabaseServlet.java:129)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.filters.ExpiresFilter.doFilter(ExpiresFilter.java:1201)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.mcafee.orion.core.server.MdcFilter.doFilter(MdcFilter.java:31)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.mcafee.orion.core.server.DisableUrlSessionFilter.doFilter(DisableUrlSessionFilter.java:58)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
at com.mcafee.orion.core.server.mfsvalve.ValveContext.invokeNextInChain(ValveContext.java:27)
at com.mcafee.orion.core.server.mfsvalve.MfsValve.invoke(MfsValve.java:38)
at com.mcafee.orion.core.server.AjaxValve.invoke(AjaxValve.java:84)
at com.mcafee.orion.core.server.OrionUserSetupValve.invoke(OrionUserSetupValve.java:34)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:270)
at com.mcafee.orion.core.server.OrionSingleSignOn.invoke(OrionSingleSignOn.java:203)
at com.mcafee.orion.core.server.ClientCertValve.invoke(ClientCertValve.java:59)
at com.mcafee.orion.core.server.ExternalAuthenticationStrategyExtPointValve.invoke(ExternalAuthenticationStrategyExtPointValve.java:140)
at com.mcafee.orion.core.server.ParameterEncodingValve.invoke(ParameterEncodingValve.java:34)
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683)
at com.mcafee.orion.core.server.ThreadLocalInfoCleanupValve.invoke(ThreadLocalInfoCleanupValve.java:25)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1760)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1719)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

 

I changed the domain name and user name, so I could post this.

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 12 of 36

Re: Cannot access ePO 5.9, database error

Jump to solution

Look at KB84438 - it will show how to get the database account changed.  If using a windows account, it also needs to be a local administrator on the epo server.

As for changing the epo services logon account, changing the service account ePO uses is not supported. The permissions it needs *are* the ones granted by local system. Changing them to give something else could have unforeseen consequences. Just as an example if you give the account the ePO services run under “local logon permissions” that can cause problems.

As for changing sql services account, that would be a Microsoft question.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Cannot access ePO 5.9, database error

Jump to solution

I have tried a variation of this article. Once i get to the https://localhost/core/config page, any attempt to put in a new user and password fails, because it says it cannot authenticate to the domain. I have removed the server from the domain and rejoined it, but still get the above error. The server is able to do the normal operations with the domain, only ePO seems to have problems connecting. I have reboot the server and posted a copy of the orion log . I also have a copy of the SQL log, if needed. 

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 14 of 36

Re: Cannot access ePO 5.9, database error

Jump to solution

Is that Windows account also a local admin account on the epo server?  Have you verified the port is correct?  Sometimes sql is using dynamic ports and they can change.  Have you tried using the SA account or other sql authentication account with appropriate permissions?  Have you verified you can log into sql management studio with that account?  You would have to be logged into the server with that account to test that.  Also, that account can't be in the deny local logon group, or it will fail.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Cannot access ePO 5.9, database error

Jump to solution

The 'sa' account is both local to the server, and a member of the Administrators group on the server. When I go into the SQL Management Studio and put in the sa as user and it's password as an SQL Server Authentication, I get the following:

TITLE: Connect to Server
------------------------------

Cannot connect to NETWORKSERVICES.

------------------------------
ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&Evtsrc=MSSQLServer&EvtID=233&LinkId...

------------------------------

No process is on the other end of the pipe

McAfee Employee cdinet
McAfee Employee
Report Inappropriate Content
Message 16 of 36

Re: Cannot access ePO 5.9, database error

Jump to solution

If sa is an sql account, then it can't also be a windows account.  You may have a local windows account called SA, but it is not the same as the actual sql sa account.  So from the error, it seems like there is a problem with the sql server itself.  Are the sql server services started, do they exist, errors in sql error log?  I would get sql working first.

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Cannot access ePO 5.9, database error

Jump to solution

This is the most recent SQL Log:

019-07-01 09:48:29.14 Server Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64)
Jul 3 2017 02:25:44
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)

2019-07-01 09:48:29.15 Server UTC adjustment: -4:00
2019-07-01 09:48:29.15 Server (c) Microsoft Corporation.
2019-07-01 09:48:29.15 Server All rights reserved.
2019-07-01 09:48:29.15 Server Server process ID is 8064.
2019-07-01 09:48:29.15 Server System Manufacturer: 'Intel', System Model: 'S5000PAL'.
2019-07-01 09:48:29.15 Server Authentication mode is WINDOWS-ONLY.
2019-07-01 09:48:29.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2019-07-01 09:48:29.15 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2019-07-01 09:48:29.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2019-07-01 09:48:29.15 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2019-07-01 09:48:29.64 Server SQL Server detected 2 sockets with 2 cores per socket and 2 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-07-01 09:48:29.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-07-01 09:48:29.64 Server Detected 32762 MB of RAM. This is an informational message; no user action is required.
2019-07-01 09:48:29.64 Server Using conventional memory in the memory manager.
2019-07-01 09:48:29.84 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2019-07-01 09:48:30.12 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-07-01 09:48:30.12 Server This instance of SQL Server last reported using a process ID of 1956 at 7/1/2019 9:48:27 AM (local) 7/1/2019 1:48:27 PM (UTC). This is an informational message only; no user action is required.
2019-07-01 09:48:30.13 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-07-01 09:48:30.37 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2019-07-01 09:48:30.37 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2019-07-01 09:48:30.40 spid8s Starting up database 'master'.
2019-07-01 09:48:30.45 Server CLR version v4.0.30319 loaded.
2019-07-01 09:48:30.58 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2019-07-01 09:48:30.69 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-07-01 09:48:30.69 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-07-01 09:48:30.73 spid8s SQL Trace ID 1 was started by login "sa".
2019-07-01 09:48:30.74 spid8s Server name is 'NETWORKSERVICES'. This is an informational message only. No user action is required.
2019-07-01 09:48:31.11 spid13s A self-generated certificate was successfully loaded for encryption.
2019-07-01 09:48:31.12 spid13s Server is listening on [ 'any' 1433].
2019-07-01 09:48:31.12 spid13s Server is listening on [ 'any' 1433].
2019-07-01 09:48:31.13 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2019-07-01 09:48:31.13 spid13s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2019-07-01 09:48:31.13 Server Server is listening on [ ::1 1434].
2019-07-01 09:48:31.13 Server Server is listening on [ 127.0.0.1 1434].
2019-07-01 09:48:31.13 Server Dedicated admin connection support was established for listening locally on port 1434.
2019-07-01 09:48:31.14 spid13s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-07-01 09:48:31.14 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-07-01 09:48:31.26 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/networkservices.floristnet.g5p ] for the SQL Server service.
2019-07-01 09:48:31.26 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/networkservices.floristnet.g5p:1433 ] for the SQL Server service.
2019-07-01 09:48:32.56 spid14s A new instance of the full-text filter daemon host process has been successfully started.
2019-07-01 09:48:32.74 spid17s Starting up database 'msdb'.
2019-07-01 09:48:32.74 spid19s Starting up database 'ReportServerTempDB'.
2019-07-01 09:48:32.74 spid18s Starting up database 'ReportServer'.
2019-07-01 09:48:32.75 spid20s Starting up database 'ePO_NETWORKSERVICES'.
2019-07-01 09:48:32.75 spid9s Starting up database 'mssqlsystemresource'.
2019-07-01 09:48:32.82 spid9s The resource database build version is 12.00.5000. This is an informational message only. No user action is required.
2019-07-01 09:48:33.00 spid9s Starting up database 'model'.
2019-07-01 09:48:33.13 spid9s Clearing tempdb database.
2019-07-01 09:48:33.32 spid9s Starting up database 'tempdb'.
2019-07-01 09:48:33.50 spid9s The tempdb database has 1 data file(s).
2019-07-01 09:48:33.51 spid21s The Service Broker endpoint is in disabled or stopped state.
2019-07-01 09:48:33.51 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2019-07-01 09:48:33.52 spid21s Service Broker manager has started.
2019-07-01 09:48:33.61 spid8s Recovery is complete. This is an informational message only. No user action is required.
2019-07-01 09:49:00.51 Server Software Usage Metrics is enabled.

Re: Cannot access ePO 5.9, database error

Jump to solution

Also, in the ePO core/config web page, where I try to change the login and password, it shows the Database server port to be 1433. is that correct?

McAfee Employee Hawkmoon
McAfee Employee
Report Inappropriate Content
Message 19 of 36

Re: Cannot access ePO 5.9, database error

Jump to solution

Hi skeating,

Can you Open 'SQL Server Configuration Manager'

SQLSvrConfMan.JPG

 ... and expand 'SQL Server Network Configuration' in the left side frame(panel/window) and click on Protocols for your SQL Server Instance name.
You should be offered/you should see all protocols on the right side frame(panel/window).

example:

details.JPG

Are all of the three offered 'enabled'?
If not can you 'enable' any that are not please?
(A restart of services is needed if any changes are made here)

Edit: 1433 is ok! 🙂

Secnd edit: Your SQL browser service is running (automatic) ? 

Was my reply helpful?

If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: Cannot access ePO 5.9, database error

Jump to solution

All three protocols are enabled, and a restart of services has been done. When i try to do a Windows Authentication in SQL Management Studio, I cannot change the login account nor put in a password, as the area is grayed out.

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