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.
Each Forms module has a Help property (under the Form node in Forms Builder). This property should contain the full virtual path to the help file, relative to the Forms application’s web context.
Example: If your help file myapp.chm is placed in $ORACLE_HOME/forms/help/, and your Forms servlet is mapped to /forms/, set the Help property to:
/forms/help/myapp.chm
Correction steps:
Try opening the help file outside Oracle Forms (double-click the .chm or .hlp). If it fails to open or shows "Navigation to the webpage was canceled," unblock the file:
For Forms 6i and earlier, ensure this registry key exists: frm-18105 failed to start the help system
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\FORMS6I\HELP_SYSTEM = winhelp32.exe
While you troubleshoot, you can suppress the error by creating a KEY-HELP trigger at the form level:
-- KEY-HELP trigger
NULL; -- Does nothing, but prevents the error popup
Use sparingly—this removes user help entirely.
In simple terms, Oracle Forms is trying to call the Windows Help API (or a browser-based help viewer), but the request fails. The root causes typically fall into one of three buckets:
If you are unable to install legacy WinHelp due to corporate IT restrictions, or if the files simply won't open, the most useful feature is ignoring the error.
Summary Recommendation: If you want the Help button to work, use Feature #1 (Install WinHelp). If you just need to get your work done, use Feature #5 (Ignore it), as the error is usually non-fatal. In web mode, the Forms client runs inside
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. Correction steps: Try opening the help file outside
If the Java Importer opens correctly, the JVM is likely fine, and the issue is specific to the help configuration or permissions. Technical Context
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.
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: