The Oracle Forms error FRM-18105: Failed to start the Help System
typically indicates a permissions issue or an incomplete environment configuration Quick Fixes Run as Administrator : Right-click the Forms Builder executable (or its shortcut) and select "Run as Administrator"
. This is the most common resolution for accessing the help system in newer versions of Windows. Set Web Browser Preferences
: Ensure a browser is correctly linked to the builder. Go to Edit > Preferences > General and verify the Web Browser Location
field contains the full path to your browser’s executable (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe Advanced Troubleshooting
If the basic fixes don't work, the issue may be rooted in your installation or environment variables: Check Environment Variables : Verify that FORMS_BUILDER_CLASSPATH
is correctly defined in your system environment variables or the Windows registry. Elevated Configuration : For Forms 12c, ensure you ran the config_builder.cmd (or equivalent) in an elevated shell
(Run as Admin) during initial setup. Failure to do so can prevent the creation of necessary registry entries. Java Conflicts : Ensure your system
has the correct Java version (typically Java 8 for older Forms versions) at the beginning to avoid conflicts with other installed Java versions. if they are missing?
FRM-18105: Failed to start the Help System. Form Builder 12.
FRM-18105: Failed to start the Help System typically indicates that
the Oracle Forms Builder environment is missing critical configuration settings or cannot locate the necessary Java libraries required to launch the help interface Root Causes Incomplete Configuration:
If the Node Manager, Admin Server, and WLS_FORMS were not started with elevated privileges (Run as Administrator) during the initial setup, final registry entries and configuration steps may have failed to complete. Classpath Conflicts: FORMS_BUILDER_CLASSPATH
environment variables may be missing references to required help-related JAR files, such as help-share.jar Multiple Oracle Homes:
Version conflicts can occur if the system PATH includes multiple Oracle installations or incorrect Java versions. Permissions:
Running the Form Builder without the necessary administrative rights can prevent it from accessing required system components. Oracle Forums Recommended Troubleshooting Steps Verify Java Importer: Test if the JVM is functioning by opening the Java Importer
in Form Builder. If it opens successfully, the JVM is working; the issue is likely specific to the Help library paths. Correct the Classpath: Ensure your FORMS_BUILDER_CLASSPATH in the Windows Registry (typically under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_
%ORACLE_HOME%\oracle_common\modules\oracle.help\help-share.jar
%ORACLE_HOME%\oracle_common\modules\oracle.help\oracle_ice.jar Use Elevated Privileges: Always run the Form Builder and any configuration scripts (like config_builder.cmd
for standalone installations) by right-clicking and selecting Run as Administrator Check for PATH Conflicts:
Review your system PATH variable. Ensure that the current Oracle Home and its required Java versions are at the beginning of the list. Re-run Configuration (If Necessary):
If the registry entries are entirely missing, it may be necessary to recreate the WebLogic domain or re-run the configuration scripts in an elevated shell to ensure all entries are properly created. Oracle Forums full list of required JAR files
for your specific Oracle Forms version to verify your registry settings? FRM-18105: Failed to start the Help System. - Oracle Forums
FRM-18105: Failed to start the help system typically occurs in Oracle Forms Builder (specifically version 12c) when the tool cannot initialize the Java-based online help components
. This is often due to environment variable conflicts, incorrect Java pathing, or incomplete installation privileges. Common Causes Path Conflicts frm-18105 failed to start the help system
: Multiple Oracle product installations (like older versions of Oracle Client or Middleware) may appear earlier in the system
than the current Forms Home, causing the Builder to load incompatible libraries. Missing Environment Variables FORMS_BUILDER_CLASSPATH
or specific Java-related variables may not be correctly defined for the Builder's help system to locate its required Privilege Issues
: If the Oracle Fusion Middleware was not installed using "Run as Administrator," certain registry keys or configuration files required for the help system might be missing. Java Version Mismatch
: The Forms Builder requires a specific JDK version (typically JDK 8 for 12c). If a newer Java version (like Java 11 or 17) is primary in the system path, it can break the help subsystem. Recommended Solutions Adjust the System PATH
Ensure the Oracle Forms 12c bin directory is at the very beginning of your Windows System Path. Advanced System Settings Environment Variables Move the entry for your Oracle 12c Home (e.g., C:\Oracle\Middleware\Oracle_Home\bin ) to the top of the list. Define FORMS_BUILDER_CLASSPATH
Manually adding the classpath can help the Builder find the help system jars: Create a new System Variable named FORMS_BUILDER_CLASSPATH Set its value to include the help jars, typically found in:
%ORACLE_HOME%\jlib\ohj.jar;%ORACLE_HOME%\jlib\help-share.jar;%ORACLE_HOME%\jlib\oracle_ice.jar Run as Administrator Always launch the Forms Builder ( frmbld.exe ) by right-clicking and selecting Run as Administrator
to ensure it has full access to the required local resources. Verify Java Configuration
Confirm that the JDK 8 path is correctly referenced in your environment. If the help system still fails, check the
section in the Forms Builder to see which Java version it is currently utilizing. Re-installation (Last Resort)
If environment tweaks fail, the installation may be corrupted. A clean reinstall often requires deleting the Oracle registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
and the physical installation directory before starting a fresh install with full administrative privileges. or do you need help locating your Oracle Home directory
FRM-18105: Failed to start the Help System. Form Builder 12.
The error FRM-18105: Failed to start the Help System in Oracle Forms Builder typically occurs because the environment variables or registry entries required to locate the help files are missing or misconfigured. Common Solutions
Update FORMS_BUILDER_CLASSPATH: Ensure the FORMS_BUILDER_CLASSPATH environment variable includes the path to the Oracle Home where the help files are located. Users on Oracle Forums often suggest checking this variable first.
Run as Administrator: Installation or configuration issues can sometimes be bypassed by launching the Form Builder with Administrative privileges. For certain versions like Form Builder 12c, a full re-installation under an Administrator account—including deleting old Oracle registry keys—may be required to fix deep-seated pathing issues.
Check Java Version: Ensure that the compatible Java version (typically JDK 8 for newer versions) is at the beginning of your system PATH variable. If the Builder cannot find the correct Java runtime, it may fail to initialize subsystems like Help or the Debugger Oracle Forums.
Verify Help File Existence: Confirm that the help file itself (e.g., ohw.jar or similar resource files) is not missing or damaged. If the environment cannot find these resources, it triggers errors like FRM-10063 or FRM-18105 Scribd.
Are you using a specific version of Oracle Forms, like 10g or 12c, when encountering this error?
FRM-18105 Failed to Start the Help System: A Comprehensive Guide to Troubleshooting and Resolution
The FRM-18105 error is a common issue encountered by Oracle Forms users, which occurs when the help system fails to start. This error can be frustrating, especially when you need to access help documentation to resolve a critical issue or complete a task. In this article, we will explore the causes of the FRM-18105 error, provide step-by-step troubleshooting guides, and offer solutions to resolve the issue.
What is FRM-18105?
FRM-18105 is an error code that occurs in Oracle Forms when the help system fails to start. The error message typically displays as: The Oracle Forms error FRM-18105: Failed to start
"FRM-18105: Failed to start the help system"
This error can occur due to various reasons, including misconfigured settings, corrupted files, or issues with the Oracle Forms installation.
Causes of FRM-18105 Error
After analyzing various user reports and Oracle Forms documentation, we have identified the following common causes of the FRM-18105 error:
Troubleshooting Steps
To resolve the FRM-18105 error, follow these step-by-step troubleshooting guides:
The Oracle Forms error FRM-18105: Failed to start the help system is a configuration issue, not a code bug. It appears when the Forms runtime cannot locate or launch the designated help viewer. By methodically checking the registry (client‑server) or the virtual path and server files (web), you can resolve the error in under 15 minutes.
If you have followed this guide and still see the error, contact Oracle Support with a copy of your formsweb.cfg (web) or your registry export (client‑server) and the exact version of Forms you are using. In most real‑world cases, the problem is a missing help file or a disabled WinHelp component on a modern Windows OS.
Next step: After fixing, test every form that includes context‑sensitive help. Also inform your end‑users that F1 help is restored.
Last updated: March 2025. Compatible with Oracle Forms 6i through 12c.
Microsoft discontinued native support for WinHelp (.hlp) files after Windows 7. If you are still using old .hlp files:
.chm (HTML Help) and update the form property Help File Name accordingly.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WinHelp\AllowWinHelp
= 1 (DWORD)
For Forms 6i and earlier, ensure this registry key exists:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\FORMS6I\HELP_SYSTEM = winhelp32.exe
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 the world of Oracle Forms, FRM-18105: Failed to start the Help System is a classic "ghost in the machine" error. It typically happens when the Form Builder is ready to work, but the bridge to its documentation is broken. The Backstory: Why It Fails
This error is rarely about the help files being missing; it's almost always a communication breakdown between the Form Builder and the Java environment required to render the help viewer.
Permissions Blockade: The most common "deep" reason is that the Windows user doesn't have sufficient privileges to execute the Java components or access the specific Oracle Home folders where the help libraries live.
Java Identity Crisis: If multiple Java versions are installed (like a mix of JDK 1.8 and older versions), the Form Builder might be trying to "speak" to the wrong one.
Missing Bridges (Environment Variables): The Builder needs a specific map—defined by variables like FORMS_BUILDER_CLASSPATH—to find its help-related .jar files. How to Fix the "Story"
If you're stuck in this loop, here is the sequence of events to get the help system back online:
The "Admin" Shortcut: Many users find that simply right-clicking the Form Builder and selecting Run as Administrator bypasses the error entirely by granting the necessary file system permissions.
Define the Classpath: Ensure your system knows where the help libraries are. A common fix involves adding a FORMS_BUILDER_CLASSPATH variable to your Environment Variables:
Include paths like %ORACLE_HOME%\jlib\ohj.jar and %ORACLE_HOME%\jlib\help-share.jar.
Check Java Alignment: Make sure your PATH variable points to the correct Java version (usually JDK 1.8 for modern Forms versions) and that it appears before any other Java entries. Incorrect or missing HELP_PATH setting : The HELP_PATH
Folder Permissions: If you can't run as Admin, manually grant "Read & Execute" permissions to your specific Windows user for the C:\Oracle\Middleware\Oracle_Home folder.
For deeper technical troubleshooting, Oracle recommends checking the Java stack trace (found via the "Details" button if available) to see exactly which library is failing to load.
FRM-18105: Failed to start the Help System error in Oracle Forms Builder (commonly 12c)
occurs when the builder cannot locate or execute the necessary help files or the browser required to display them
. This is frequently due to installation issues, missing Java paths, or improper environment variables. Oracle Forums
Here are the most effective solutions based on Oracle forums and community troubleshooting: 1. Fix Environment Variables (FORMS_BUILDER_CLASSPATH) The most common cause is that the debugger.jar or help system jar files are not properly referenced. Add or update the FORMS_BUILDER_CLASSPATH in your system environment variables. It should point to the debugger.jar files in your Oracle Home (e.g., C:\Oracle\Middleware\Oracle_Home\forms\java\debugger.jar Stack Overflow 2. Verify Oracle Home Path Order
Ensure that your current Oracle Form Builder home is the first entry in your Windows system system variable and make sure the new 12c folder (e.g., C:\Oracle\Middleware\Oracle_Home\bin ) comes before any old Oracle or 32-bit Java references. Oracle Forums 3. Ensure Proper Installation Rights
If the installation was not done with sufficient privileges, files may be missing or locked. Perform a clean re-installation. Delete the entire tree in the registry, delete the existing ORACLE_HOME folder, and reinstall using "Run as Administrator" Oracle Forums 4. Correct Java Version
Forms Builder 12c requires a specific version of Java (usually 32-bit for the builder, even on 64-bit Windows) to run correctly.
Verify that you are using 32-bit Java 8 for the builder, even if your WebLogic server uses 64-bit. Oracle Forums 5. Alternative Solution: Use a Supported Browser
Sometimes, the built-in help viewer fails due to outdated embedded browser components.
Open a support ticket to verify the current browser compatibility. Older versions of Forms Builder often depend on Internet Explorer components that may no longer function. Oracle Forums Summary of Quick Checks Checkpoint FORMS_BUILDER_CLASSPATH debugger.jar of new installation is first in 32-bit Java is configured for Form Builder.
Remove old ORACLE entries (64-bit and 32-bit) before reinstalling. If this happens while attempting to debug, ensure your formsweb.cfg allow_debug=true debugger.jar is properly included in default.env
FRM-18105: Failed to start the Help System. Form Builder 12.
The error FRM-18105: Failed to start the help system is a known issue in Oracle Forms, often caused by incorrect file paths, missing registry entries, or lack of administrative privileges during installation. Recommended Solutions Relocate Help Files (Oracle 9i/10g):
Navigate to your fmhelp.jar file.
Move this file to the
Check the FORMS_BUILDER_CLASSPATH in your Windows Registry or System Environment Variables.
Ensure all paths are correct and that there are no typos, especially if you have added custom JAR references. Administrative Privileges:
If you recently installed the software, ensure you have successfully started the Node Manager, Admin Server, and WLS_FORMS at least once as an elevated Windows Administrator.
Failure to run these with administrative rights during the initial configuration can prevent the help system and debugger from initializing. Clean Reinstallation:
If configuration fails, some users recommend deleting the ORACLE tree from the Windows registry (32 and 64-bit), deleting the HOME directory, and performing a fresh installation using "Run as Administrator" for all steps. JVM Check:
Test if the Java Virtual Machine (JVM) used by the Builder has crashed by attempting to open the Java Importer. If the Importer opens, the JVM is likely stable, and the issue is specific to the help system's configuration.
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:
http://server:8889/forms/frmservlet).http://server/help/forms.chm).