Loading...

Knowledge Center

Error 500 displays in web browser when attempting to access the ePO console
Technical Articles ID:   KB81737
Last Modified:  7/9/2018
Rated:

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Problem

The following error displays in the Orion.log:

2014-01-15 11:40:42,813 ERROR [main] plugin.PluginManager  - Initialization of plugin core failed.

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'core.ext.taskGlobals' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: The following extensions are in a partially installed state: [dlp_93100_help:]

Caused by: java.lang.IllegalStateException: The following extensions are in a partially installed state: [dlp_93100_help:]

Problem

The following error displays in the Orion.log:
 
2014-04-04 15:15:56,124 ERROR [main] plugin.PluginManager  - Initialization of plugin core failed.

org.springframework.beans.factory.BeanCreationException: 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.

Caused by: 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.

Caused by: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

Cause

Error 500 on the ePO console has two common causes:
  • Partially installed extension 
    OR
  • Database connection issue
To determine the cause of this issue, do the following:
  1. Restart the ePO application server service.
  2. Review Orion.log.
    NOTE: By default, Orion.log is located in the following path: <ePO installation directory>\Server\logs\
     
    • For ePO 4.6.x - Scroll to the bottom of Orion.log and search for the term starting coyote. Look for the error message below the line with this term.
    • For ePO 5.x - Clear out the Orion.log, restart the ePO Application Server service, and check Orion.log for errors.


    Partially installed extension issue:
    The Orion.log displays an error similar to the following:

    2014-01-15 11:40:42,813 ERROR [main] plugin.PluginManager - Initialization of plugin core failed.

    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'core.ext.taskGlobals' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: The following extensions are in a partially installed state: [dlp_93100_help:]

    Caused by: java.lang.IllegalStateException: The following extensions are in a partially installed state: [dlp_93100_help:]

    NOTE: This error indicates that [dlp_93100_help:] is in the OrionExtensions table database, but missing from the ePO file system.


    Database connection issue
    The Orion.log displays an error similar to the following:

    BeanCreationException: 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.

    Caused by: 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.

    Caused by: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
     
 

Solution

There are two ways to fix this issue:
  • If the extension in error is not needed, remove it from the ePO database and file system.
    In the database, run the following query to delete the entry:

    Delete from OrionExtension where name = 'dlp_93100_help'

    NOTE: Confirm that a full backup of the database exists before making any changes to the database.
     
    • Check for dlp_93100_help.xml in <ePO installation directory>\Server\Conf\Catalina\localhost. If it is present, move it out to the desktop.
    • Check for the dlp_93100_help folder in <ePO installation directory>\Server\Extensions\Installed. If it is present, move it out to the desktop.
       
  • Because the extension is already in the database, check in the file system to find out where it is missing from and place the copy of the file or folder in its designated location.
     
    • Check for dlp_93100_help.xml in <ePO installation directory>\Server\Conf\Catalina\localhost. If it is missing, copy the extension .xml from backup or another ePO server to the impacted ePO server. Make sure you check for the correct version and install path. The installation path in the .xml file should match the impacted ePO server's installation path.
       
    • Check for the dlp_93100_help folder in <ePO installation directory>\Server\Extensions\Installed. If it is missing, copy the folder from backup or another ePO server to the impacted ePO server. Make sure you check the version of the extension.

 

Solution

To troubleshoot the database connection issue, start with the UDL test (see KB70929) and ensure that all of the information in DB.properties is accurate. Ensure the account has the correct permissions by verifying the account used to access the SQL server has the following permissions:
  • The default database must be Master:
    1. Click Start, Programs, Microsoft SQL Server 2005, SQL Server Management Studio.
    2. Expand Security, Logins.
    3. Right-click the account and select Properties.
    4. Ensure the default database is set to Master.
    5. Expand User Mapping and ensure that the account has dbo in the schema for the database.
       
  • This account must the db_owner in the database security properties:
    1. Click Start, Programs, Microsoft SQL Server 2005, SQL Server Management Studio.
    2. Expand Databases, your ePO database, Security, Users.
    3. Right-click the dbo account and select Properties.
    4. Ensure that the account has dbo in the Default schema for the database.
      NOTE: If you use an NT account to authenticate to the ePO 4.x database, ensure that the account has Local Admin rights on the ePO 4.x server. See KB75766 for detailed information on the required SQL permissions.
       
  • Ensure Auto Close is set to False for the ePO database:
    1. Click Start, Programs, Microsoft SQL Server 2005, SQL Server Management Studio.
    2. Right-click the ePO database and select Properties.
    3. Click Options and ensure Auto Close is set to False. If it is not, click Auto Close, select False, and click OK.
       
  • Ensure the SQL browser service is running:
    1. Click Start, Run, type services.msc and click OK.
    2. Locate the SQL Server Browser service and ensure that it is started and running. If it is not, right-click the SQL Server Browser service and select Start.
       
  • Ensure SQL Force Encryption is disabled in SQL server environments. If it is enabled:
    1. Click Start, All Programs, Configuration Tools, SQL Server Configuration Manager.
    2. Right-click Protocols for <instance_name> (MSSQLSERVER by default) under SQL Server Network Configuration, and click Properties.
    3. Click the drop-down menu for Force Encryption and select No.
    4. Click OK.
       
  • Enable TCP/IP on the ePO 4.x server:
    1. Click Start, Run, type Cliconfg and click OK.
    2. Ensure the TCP/IP protocol is Enabled and at the top of the Enabled protocols by order list.
       
  • Verify the correct DB collation is set on the SQL server:
    NOTE: ePO 4.0 uses SQL_Latin1_General_CP1_CI_AS as the default collation for the database when an upgrade or fresh installation of ePO is performed.

    Do the following to verify collation in SQL Server 2005:
    1. Click Start, Programs, Microsoft SQL Server 2005, SQL Server Management Studio.
    2. Log on to the server using Windows Authentication or SQL Server Authentication, as applicable.
    3. In Object Explorer, expand Databases and locate the ePO database.
    4. Right-click the ePO database and select Properties.
    5. Review the Collation field in the General page.
       
  • In a pure IPv6 environment, ensure that only IPv6 is enabled on the SQL server that hosts the ePO database.
     

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.