ERROR: setup detected an error reading db.properties file required to continue installation (issue: TCP/IP Dynamic Port used)

  • Post reply
No replies
Sun, 19/04/2009 - 23:00
Admin
Offline
ModeratorRegular Member
Joined: 16/08/2008
Posts:
Points: 263

Courtesy McAfee KB: KB53935

Environment

McAfee ePolicy Orchestrator 4.0 Patch 2
Microsoft Windows (all supported versions, see KB51109 )

Problem 1

The following error reported when installing ePolicy Orchestrator 4.0 Patch 2:

Error: Setup detected an error reading db.properties file required to continue installation. Verify that this file is in the correct location.
Problem 2
The following error is recorded in the Patch 2 installation log (EPO400-Patch-MSI.LOG):
1: Setup successfully read the db.properties file .
1: Loading the following DLL for Use: [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{35976AC6-D42C-4E19-BFA5-8F77131DB81E}\ CommonSetup.DLL]
1: Setting the current directory to [C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{35976AC6-D42C-4E19-BFA5-8F77131DB81E}].
1: VerifyOurDatabase function returned code [2].
 
The following error is recorded in the EPO400-CommonSetup.Log:
Testing NT Authentication to SQL Server.
Failed to connect to SQL Server [WIN2003E] with error code [0x80004005]
Description for error code is [[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
Failed in connectToSQLServer with error code [183].
Cause
SQL server is configured to use a dynamic port.
Solution 1
NOTE: McAfee does not recommend using dynamic port assigning within the SQL Server, but in the short term use the solution below to both verify the cause and resolve the installation of ePO 4.0 Patch 2.
 
Solution 2
Identify the port specified in the ePO 4.0 Server configuration page or file.
Method 1 - Via the ePO Configure Database Settings page:
  1. Access the Database Configuration page. If you are using the default settings, launch Internet Explorer and go to https://locahost:8443/core/config.

    See KB51465 for more details on accessing the ePO database configuration page:
     

  2. Note the Database server port value: ####
 
Method 2 - Via the db.properties file:
  1. Launch Windows Explorer.
  2. Navigate to the following location (default specified)
    ..\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\ contains\db.properties
  3. Right-click on db.properties and select Edit.
  4. Make a note of port number specified in db.port=####
  5. Click File, Exit.
 
Use the above port with the telnet command to verify the problem relates to the SQL TCP dynamic port:
  1. Click Start, Run, type cmd, then click OK.
  2. Type telnet <SQL_ServerName> <PortNumber>, then press ENTER.

    Example:
    telnet SQLServer 1489

    The following error will be reported which confirms the dynamic port is the cause:
    Connecting to <server_name>... Could not open a connection to host on port #### : Connect failed

  3. Close the command window.
 
Identify the current SQL TCP dynamic port setting:
SQL 2005

Method 1 - SQL Server Configuration Manager

  1. Click Start, Programs, Microsoft SQL Server 2005, Configuration Tools, SQL Server Configuration Manager.
  2. Click the IP Address tab.
  3. Scroll down and locate the section IPALL.
  4. Make a note of the TCP dynamic Ports value ####
  5. Close the TCP/IP Properties window.
Method 2 - Using sqlservermanager.msc to access the SQL Server Configuration Manager
  1. Click Start, Run, type: sqlservermanager.msc then click OK.
  2. In the left pane under SQL Server Configuration Manager, expand SQL Server 2005 Network Configuration.
  3. In the right pane right-click TCP/IP and select Properties.
  4. Click the IP Address tab.
  5. Scroll down and locate the section IPALL.
  6. Make a note of the TCP dynamic Ports value ####
  7. Close the TCP/IP Properties window.
Method 3 - Registry
  1. Click Start, Run, type regedit, then click OK.
  2. Navigate to the following key:
    [HKLM\Software\Microsoft\Microsoft SQL Server\ePOSERVER\MSSQLServer\SuperSocketNetLib\TCP\]

    NOTE: This path shown above is only the default path within the default instance of the ePO 4.0 installation. This does not cover installations with different instances or local instance installations.

     

  3. Make a note of the TcpPort key value: ####
  4. Click Registry, Exit.
 
SQL 2000

Method 1 - SQL Server Network Utility
  1. Click Start, Programs, Microsoft SQL Server, Server Network Utility.
  2. On the General tab, in the right pane select TCP/IP then click Properties.
  3. Make a note of the Default Port value ####.
Method 2 - Using svrnetcn to access the SQL Server Network Utility
  1. Click Start, Run, type: svrnetcn, then click OK.
  2. On the General tab, in the right pane select TCP/IP then click Properties.
  3. Make a note of the Default Port value ####.
 
Verify Telnet with port obtained from registry value obtained in the above section (Identify what the current SQL TCP dynamic port setting)
  1. CMD, Type telnet <SQL_Server_Name> ####

    Where:

    • #### is the port number
    • <SQL_Server_Name> is the server hosting the SQL Server

      The following will be displayed if the correct port is used:

      You see a blank screen with a blinking cursor verifying that this is the correct port
       

  2. Close the telnet session
 
Change the port used by ePO 4.0 to use the above successfully tested SQL dynamic port number:
 
Method 1 - Via the ePO Configure Database Settings page (Preferred method):
  1. Access the Database Configuration page. If you are using the default settings, launch Internet Explorer and go to https://locahost:8443/core/config.

    See KB51465 for more details on accessing the ePO database configuration page:

     

  2. Change the value of the Database server port value to the one obtained in the previous step (Identify what the current SQL TCP dynamic port setting:)
  3. Click Apply.
  4. Click test Connection.
  5. Close the Configure Database Settings page.
 
Method 2 - Via the value db.port= in the file db.properties:
  1. Launch Windows Explorer.
  2. Navigate to the following location (default specified)
    ..\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\ contains\db.properties
  3. Right-click on db.properties and select Edit.
  4. Change the value of db.port= to value obtained in Step 1 via the SQL interface.
  5. Click File, Save.
  6. Click File, Exit.
 
Stop and Start the ePO 4.0 Services
  1. Click Start, Run, type: services.msc then click OK.
  2. Right-click on each of the Services below and select Stop:

    McAfee ePolicy Orchestrator 4.0.0 Server
    McAfee ePolicy Orchestrator 4.0.0 Event Parser
    McAfee ePolicy Orchestrator 4.0.0 Application Server

  3. Right-click on each of the Services below and select Start:

    McAfee ePolicy Orchestrator 4.0.0 Application Server
    McAfee ePolicy Orchestrator 4.0.0 Event Parser
    McAfee ePolicy Orchestrator 4.0.0 Server

     

  4. Close the Services window.
Reinstall ePO 4.0 Patch 2.
With the correct port specified in the ePO environment the ePO Patch 2 will now successfully allow the patch to install.
Previous Document ID
616898

 

Bookmark/Search this post with
__________________

For Official Aztech Networks Support - email to support@aztech.net.au

If you appreciated this help, please donate so we can keep the tech info flowing!

 

Top
  • Quote

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <table> <td> <tr> <b> <i> <u> <div> <span> <p> <br> <option> <form> <input>
  • Lines and paragraphs break automatically.
  • Images can be added to this post.
  • You may use [inline:xx] tags to display uploaded files or images inline.
  • Textual smileys will be replaced with graphical ones.

More information about formatting options

Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.