Oracle Database Client Installation fails or hangs due to Symantec Endpoint Protection (SEP)
search cancel

Oracle Database Client Installation fails or hangs due to Symantec Endpoint Protection (SEP)

book

Article ID: 427428

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

The Oracle Database Client installation may fail or become stuck on systems where Symantec Endpoint Protection (SEP) is installed.

The installation typically terminates with the following error message: “Error in creating registry key. Permission denied.”

Environment

Oracle Database Client

Symantec Endpoint Protection client installed

Cause

The issue is caused by the Proactive Threat Protection (PTP) component of Symantec Endpoint Protection blocking the Oracle installer’s Java process.

During installation, the Oracle client launches javaw.exe, which is detected and blocked by PTP, preventing the installer from creating required registry keys.

This action is logged in the Threat Log.

Resolution

Follow the steps below to allow the Oracle Database Client installation to complete successfully.

Step 1: Confirm SEP involvement:

  1. Uninstall the SEP client.
  2. Run the Oracle Database Client installation.
  3. Confirm that the installation completes successfully without SEP installed.
  4. Reinstall the SEP client.
  5. Attempt the Oracle installation again and confirm the issue reoccurs.

Step 2: Identify the blocking component:

  1. Perform Component Isolation on the SEP client.
  2. Run the Oracle Database Client installer.
  3. Confirm that the installation succeeds when Proactive Threat Protection is disabled.

Step 3: Identify the blocked process:

  1. Re-enable Proactive Threat Protection.
  2. Re-run the Oracle Database Client installation.
  3. Review the Threat Log.
  4. Confirm that javaw.exe is being detected and blocked by Proactive Threat Protection.

Step 4: Create an Exception:

  1. Open the Symantec Endpoint Protection Manager (SEPM) console.
  2. Navigate to: Policies → Exceptions
  3. Add javaw.exe as an exception.

    4. Assign the updated policy to the affected client group.

Step 5: Reinstall Oracle Database Client

  1. Run the Oracle Database Client installation again.
  2. Confirm that the installation completes successfully without errors.