# Oracle EBS Forms Not Launching: Troubleshooting Checklist for 12.1 and 12.2

> Source: https://netray.co/tools/oracle-ebs-forms-not-launching-troubleshooting-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Work through client launch method, Java, server tier, profiles and post-patch steps to find why Oracle EBS Java forms will not open.

## Category

oracle

## Erp

Oracle E-Business Suite

## Audience

- EBS DBA
- Apps DBA
- Service desk
- ERP administrator

## Tool

**Kind:** checklist

**Groups:**

#### 1. Client launch method (Java Web Start or browser plug-in)

**Items:**

**Text:** Confirm which launch method this instance uses: Java Web Start (JWS, a .jnlp file, no browser plug-in) or the Java Plug-in applet inside a browser

**Critical:** true

**Text:** If JWS: confirm the JWS patches listed in My Oracle Support Doc ID 2188898.1 (Using Java Web Start with Oracle E-Business Suite) are applied for your release (12.2 or 12.1.3) before switching users to it

**Critical:** true

If the plug-in is still used on Microsoft Edge: the EBS URL must open in Edge IE mode (site list managed by group policy), because Chromium browsers do not run NPAPI Java applets

If JWS: check that the browser downloads the .jnlp file and that .jnlp is associated with javaws from the certified JRE, not an old or third-party Java

Test with a second user on a clean PC to separate a single-desktop problem from a server problem

#### 2. Java client on the desktop

**Items:**

**Text:** JRE version on the PC is a release certified for EBS forms (check the Java client certification note for your release)

**Critical:** true

Java Control Panel > Security > Edit Site List includes the exact EBS URL with protocol and port (for example https://ebs.example.com:4443)

Clear the Java cache: Java Control Panel > General > Temporary Internet Files > Settings > Delete Files

Enable the Java console (Java Control Panel > Advanced > Java console > Show console) and read the trace for security blocks, certificate errors or class-load failures

Only one JRE is installed, or the launcher points at the intended one; remove stale 32-bit and 64-bit duplicates where possible

Certificate warning or blocked application: check that the signing certificate on the EBS JAR files is trusted and not expired

#### 3. Application tier (12.2)

**Items:**

**Text:** Forms managed server is running: admanagedsrvctl.sh status forms_server1 from $ADMIN_SCRIPTS_HOME on the run file system

**Critical:** true

Oracle HTTP Server is up (adapcctl.sh status) and the login page and OA Framework pages work, which isolates the problem to forms

frmweb processes appear on the forms node when a user opens a form (ps -ef | grep frmweb); none means the session never reached the server

Know your forms connect mode: servlet mode (default in 12.2) or socket mode; firewalls and load balancers must allow the mode in use

Forms managed server logs and OHS access logs reviewed for the failing user's timestamp

Multi-node or load balanced: the forms request reaches a node where forms_server1 (or forms_server2) is running

#### 4. Profiles and configuration

**Items:**

**Text:** ICX: Forms Launcher profile holds the correct forms servlet URL for the site, server or user level that applies (a stale user-level value overrides the site value)

**Critical:** true

Any profile used to enable Java Web Start is set per Doc ID 2188898.1 at the level you intend (site for everyone, user for a pilot group)

Context file changes (forms or web entry point variables) were followed by AutoConfig on every application tier node, and on 12.2 synchronised to the patch file system

Web entry URL, SSL terminator or reverse proxy changes are reflected in the context file and ICX: Forms Launcher

#### 5. Error codes and keyboard

**Items:**

**Text:** Record the exact FRM error: FRM-92050 (failed to connect to the server), FRM-92101 (connection failed, server or session start problem), FRM-92102 (network error, connection lost after retries)

**Critical:** true

FRM-92101 on all users points at the server tier (forms_server1, frmweb, environment); on one user it points at the client or network

FRM-92102 on long idle sessions: check firewall, VPN and load balancer idle timeouts between desktop and forms tier

Ctrl+F11 is Execute (Run) Query and F11 is Enter Query in EBS forms; check Help > Keyboard Help for the mapping actually loaded

Ctrl+F11 does nothing: check for laptop function-key (Fn lock) settings, remote desktop or VDI clients and screen-capture or hotkey software that intercept the keystroke

#### 6. After patching or cloning

**Items:**

**Text:** Product JAR files regenerated after the patch or clone (adadmin > Generate Applications Files menu > Generate product JAR files)

**Critical:** true

Users cleared the browser cache and Java cache after the JAR regeneration

On a clone: the target ICX: Forms Launcher, context file host names and certificates point at the target, not the source

Forms that fail with a specific FRM-40xxx or ORA error after a patch are compiled (.fmx regenerated) and their libraries are valid

**Scoring Note:** Work top to bottom. If a second user on a clean PC can open forms, focus on groups 1, 2 and 5; if nobody can, start with groups 3, 4 and 6.

## Content

**Intro:** This checklist isolates why Oracle E-Business Suite 12.1.3 or 12.2 Java forms will not open, from the desktop launch method through the forms managed server to post-patch JAR files. Tick each item, mark the ones that fail, and export the list to attach to your service desk ticket.

**Sections:**

#### How to use it

**Body:** Start by deciding whether the problem is one user or everyone. One user failing while a colleague on another PC succeeds almost always lives in the client: launch method, JRE version, the Java site exception list or a stale cache. Everyone failing points at the application tier: forms_server1 down, OHS issues, a bad ICX: Forms Launcher value or JAR files left inconsistent after a patch. Capture the exact message first. An FRM code, a Java console stack trace or a browser that just downloads a file and does nothing each lead to different groups in this list.

**Bullets:**

- One user: groups 1, 2 and 5
- All users: groups 3, 4 and 6
- Right after a patch or clone: group 6 first

#### Java Web Start versus the browser plug-in

**Body:** Historically EBS forms ran as a Java applet through the browser's Java plug-in. Modern Chromium browsers do not run NPAPI plug-ins, so Oracle added Java Web Start support for EBS 12.2 and 12.1.3 (Doc ID 2188898.1). With JWS the browser downloads a .jnlp file and javaws launches the forms client outside the browser, so browser choice largely stops mattering. Sites that have not applied the JWS patches still need Internet Explorer behaviour, which on Windows 10 and 11 means Microsoft Edge in IE mode. Confirm the patch level on the server before you change desktop settings, because switching users to JWS without the server patches simply moves the failure.

#### Reading the FRM errors

**Body:** FRM-92050 means the client could not connect to the forms server at all, commonly a wrong ICX: Forms Launcher URL, a port blocked by a firewall, or forms_server1 down. FRM-92101 means the connection attempt failed at session start; when every user sees it, look at the forms managed server, frmweb startup and the environment on the forms node. FRM-92102 is a network error after the session was established, typically idle timeouts on firewalls, VPNs or load balancers. Note the time, user and node, then match it to the forms managed server log and OHS access log so you are reading the right entries.

#### Gotchas after patches and clones

**Body:** Patches that touch Java or forms code can leave product JAR files out of step with the signed versions clients expect; regenerating JAR files through adadmin and clearing client caches fixes a large share of post-patch launch failures. On 12.2, remember that AutoConfig and context changes must apply to the run file system and be synchronised to the patch file system, or the next adop cycle brings the old value back. After a clone, ICX: Forms Launcher and certificates are frequent leftovers from the source instance.

**Cta:** If your service desk spends hours on forms tickets, we can put a private assistant on your own servers that reads EBS logs and profile values and suggests the next check.

**Faq:**

#### Why are Oracle EBS forms not opening in Microsoft Edge?

**Answer:** Edge is Chromium based and does not run the Java Plug-in applet, so the old launch method fails. Either open the EBS URL in Edge IE mode, configured through the enterprise site list, or move to Java Web Start after applying the patches listed in Doc ID 2188898.1, which launches forms from a .jnlp file outside the browser.

#### Is Java Web Start certified for EBS 12.2?

**Answer:** Yes. Oracle supports Java Web Start for EBS 12.2 and 12.1.3 once the required patches are applied, as described in Doc ID 2188898.1. Check the note for the exact patch list for your code level and the certified JRE releases before rolling it out, and pilot with a small user group first.

#### What does Ctrl+F11 do in Oracle EBS forms?

**Answer:** In EBS forms F11 puts the block into Enter Query mode and Ctrl+F11 executes (runs) the query. If Ctrl+F11 does nothing, check Help > Keyboard Help for the active mapping, laptop Fn lock settings, and any remote desktop, VDI or hotkey utility that captures the key before the forms client sees it.

#### How do I check that the forms server is running in 12.2?

**Answer:** Source the run file system environment and run admanagedsrvctl.sh status forms_server1 from $ADMIN_SCRIPTS_HOME. Also confirm OHS is up and watch for frmweb processes on the forms node while a user opens a form. No frmweb process means the request never reached the forms server.

## Search terms

oracle ebs forms not opening, oracle ebs not launching java forms, oracle ebs 12.2 forms not launching, oracle ebs forms not opening in edge, oracle java forms not opening, ctrl f11 not working in oracle forms, oracle ebs java web start, frm-92101 oracle ebs

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json