Frm-18105 Failed To Start The Help System 'link' (2024)

The error FRM-18105: Failed to start the help system typically occurs in Oracle Forms when the application cannot launch the help viewer (usually a .hlp or .chm file, or Oracle's internal help).

Here’s a helpful troubleshooting guide to resolve it:

1.1 What Does the Error Mean?

In Oracle Forms, the help system refers to one of two things:

• WinHelp (.hlp) or HTML Help (.chm) – Used in older client‑server (C/S) Forms applications (Forms 6i, 9i, 10g).
• WebHelp / Oracle Help for Java (OHJ) – Used in web‑deployed Forms (Forms 10g, 11g, 12c).

When you trigger online help, Forms tries to launch an external help viewer (e.g., hh.exe for .chm files, or a Java‑based help viewer). Error FRM‑18105 means the launch attempt failed. Possible reasons include:

• The help file is missing, corrupted, or inaccessible.
• The associated help viewer is not installed or is misregistered.
• The registry entries pointing to the help file are incorrect.
• File system permissions prevent execution of the help viewer.
• In web environments, the help file URL or mime type is misconfigured.

5.3 File Locking or Antivirus

Some antivirus software blocks .chm files from being opened via COM/OLE calls (how Forms invokes the help viewer). Temporarily disable real‑time scanning for help files to test.

Step 5: Consult Oracle Support and Forums

1. If the issue persists, consult Oracle Support for specific guidance related to your Oracle Forms version and configuration.
2. Oracle forums and communities can also be a valuable resource, offering insights and solutions from users who have encountered and resolved similar issues.

Conclusion

The "FRM-18105 failed to start the help system" error can seem daunting, but by understanding its causes and systematically troubleshooting, you can resolve it efficiently. Regular maintenance, correct configuration, and ensuring that environmental variables and permissions are correctly set can prevent this error from occurring in the future. If you're dealing with this issue, follow the steps outlined in this guide to get your Oracle Forms help system up and running smoothly.

In the world of Oracle development, the error FRM-18105: Failed to start the Help System is often the final hurdle after a fresh installation or upgrade of Oracle Forms Builder. It typically surfaces when a developer attempts to access the internal help documentation (often via the F1 key), only to find that the Java-based help engine is unable to launch. Common Root Causes

The "story" behind this error usually involves a breakdown in how the Form Builder interacts with its Java environment or the Windows operating system: frm-18105 failed to start the help system

Incomplete Installation Steps: Often, the post-installation configuration (like starting Node Manager or Admin Server as an elevated user) wasn't fully completed.

Pathing and Classpath Issues: The environment variable FORMS_BUILDER_CLASSPATH is frequently missing or incorrectly set in the Windows Registry, preventing the builder from finding the necessary JAR files (like ohj.jar) to run the help system.

Permissions Constraints: On modern Windows systems, the Help System sometimes requires "Run as Administrator" privileges to access specific files or initialize the Java Virtual Machine (JVM) correctly.

Java Version Conflicts: Older Oracle installations on the same machine can "disturb" the call to the help system due to mismatched DLLs or conflicting Java versions. Standard Solutions

To resolve the error and get the help system back online, developers typically follow these steps:

Run as Administrator: Right-click the Oracle Forms Builder executable and select Run as Administrator to see if it's a simple permission block.

Verify Environment Variables: Ensure FORMS_BUILDER_CLASSPATH exists in your system variables and contains the correct paths to your Oracle home, specifically including the help-related JARs.

Check the Registry: Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_. Ensure that FORMS_BUILDER_CLASSPATH matches your actual file paths. The error FRM-18105: Failed to start the help

Re-register the Oracle Home: In some cases, bringing the Oracle 12c (or current version) path to the first position in the system PATH variable can resolve conflicts with older installations.

For more specific troubleshooting, check the Oracle Forums or official documentation for your version of Oracle Middleware.

The error FRM-18105: Failed to start the Help System occurs in Oracle Forms Builder (typically version 12c) when the application cannot initialize its help documentation or the underlying Java Virtual Machine (JVM). Direct Solutions

Run as Administrator: The most common quick fix is to right-click the Oracle Forms Builder executable and select "Run as Administrator". This often resolves permission issues that prevent the help system from launching.

Elevated Post-Installation Steps: If you just installed the software, ensure you have started the Node Manager, Admin Server, and WLS_FORMS at least once using an elevated DOS shell (Run as Administrator).

Check FORMS_BUILDER_CLASSPATH: Ensure your environment variables are correctly set. Missing or incorrect entries in the system environment variables for FORMS_BUILDER_CLASSPATH can break the help system.

Java Conflicts: Having multiple versions of Java or older Oracle installations (like 11g) can interfere with the 12c help system. Check your system PATH and ensure the current Oracle home bin directory is at the beginning. Diagnostic Check To determine if the issue is a complete JVM crash: Attempt to open the Java Importer within the Builder.

If the Java Importer opens correctly, the JVM is likely fine, and the issue is specific to the help configuration or permissions. Technical Context WinHelp (

This error is often bundled with FRM-18122: Form Builder Debugger failed to Initialize, as both systems rely on a properly configured Java environment and registry entries created during the initial server startup.

Are you running a standalone installation or a full Fusion Middleware infrastructure setup?

FRM-18105: Failed to start the Help System. Form Builder 12.

4. Test with a Minimal Example

Create a simple form with one button. Set its Help File property to a known working .chm file. Run the form and press F1. If it works, your main form’s help configuration is the issue.

4. Fixing FRM-18105 in Web‑Deployed Forms (Forms 10g, 11g, 12c)

In web mode, the Forms client runs inside a browser, and help is usually displayed through Oracle Help for Java (OHJ) or a simple browser window.

3. The Registry Variable Fix

If the path configuration isn't in the environment file, it might be missing from the Windows Registry.

• The Fix:
  1. Open the Windows Registry (regedit).
  2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Oracle (or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oracle for 64-bit OS).
  3. Look for a string value named UI_ICON.
  4. If it is missing or points to the wrong folder (e.g., a folder that existed on the server but not on your client), update it to the correct path where the help files reside.

4. The File Extension Association

Sometimes the help files exist, but Windows doesn't know which program to use to open them.

• The Fix:
  1. Find a .hlp file in your Oracle installation directory.
  2. Right-click it and select Open with.
  3. Select Windows Help (if installed via feature #1).
  4. Check "Always use this app to open .hlp files."

2. Handle the ".hlp" Deprecation (Windows 8, 10, 11)

Microsoft discontinued native support for WinHelp (.hlp) files after Windows 7. If you are still using old .hlp files:

• Option A (Recommended): Convert your help to .chm (HTML Help) and update the form property Help File Name accordingly.
• Option B (Quick fix): Download the WinHelp32 viewer from Microsoft and install it. Then set the registry key:

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WinHelp\AllowWinHelp
  = 1 (DWORD)