Loading...

Knowledge Center


The license for ePolicy Orchestrator is invalid (ePO console log on page if the connection with the SQL database fails)
Technical Articles ID:   KB66166
Last Modified:  9/27/2019
Rated:


Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Problem

The following error displays when trying to log on to the ePolicy Orchestrator (ePO) console:
 
The license for ePolicy Orchestrator is invalid

Failed to load license data. To enter a new license, go here

Cause

ePO has to get the license key from the SQL database at log on. If ePO can't connect to the database currently, it fails with the invalid license message. 

If an incorrect port is specified for the Database Server Port port within the core/config page, the connection is still likely to test successfully. But could cause an issue when ePO tries to get the license from the database.

Workaround

If the SQL Server is installed on the same server as ePO, verify the db.server.name entry is listed correctly in the db.properties file and change it, if needed:
  1. Click Start, Run, type explorer, and click OK.
  2. Right-click My Computer, Properties.
  3. Click the Computer Name tab and note the server name.
  4. Navigate to the following location (default specified):

    c:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\db.properties
     
  5. Right-click db.properties and select Open. Open this file with Notepad. 
  6. Compare the value of db.server.name= to the computer name obtained in Step 3.
  7. Modify the value if the SQL Server is installed on the same server as ePO. If the entry does not match.
     
    NOTE: If the SQL Server is on a different server, this value identifies the server name as that SQL Server.
     
  8. Verify that the account listed in the db.user.name field is not locked out. If so, reset the account on the server and skip to Step 14.
  9. Click File, Save.
  10. Click File, Exit.
  11. Click Start, Run, type services.msc, and click OK.
  12. Right-click each of the services below and select Restart:

    • McAfee ePolicy Orchestrator x.x.x Server 
    • McAfee ePolicy Orchestrator x.x.x Event Parser
    • McAfee ePolicy Orchestrator x.x.x Application Server
       
  13. Close the Services window.
  14. Attempt to log on to the ePO console again.

Workaround

Identify the port on which SQL is listening:
  1. Open SQL Configuration Manager from the SQL Server and connect to the database instance to which ePO is pointing.
  2. Expand SQL Server Network Configuration and select Protocols for 'x' (where 'x' is the name of the instance).
  3. Double-click TCP/IP on the right side and select the IP addresses tab.
  4. Scroll to the bottom. The TCP Port is listed under the IPAll section.
Change the database Server Port to the correct port (if needed):
  1. Click Start, Run, type explorer, and click OK.
  2. Navigate to the following location (default specified):

    c:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\db.properties
     
  3. Right-click db.properties and select Open. Open this file with Notepad. 
  4. Compare the value of db.port= to the port number obtained in the Check the port SQL is listening on section above.
  5. Modify this value if the port entry does not match. 
  6. Click File, Save.
  7. Click File, Exit.
  8. Click Start, Run, type services.msc, and click OK.
  9. Right-click each of the services below and select Restart:
     
    • McAfee ePolicy Orchestrator x.x.x Server
    • McAfee ePolicy Orchestrator x.x.x Event Parser
    • McAfee ePolicy Orchestrator x.x.x Application Server
       
  10. Close the Services window.
  11. Attempt to log on to the ePO console again.

Rate this document

Glossary of Technical Terms


 Highlight Glossary Terms

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