Introduction
During a recent Oracle E-Business Suite (EBS) maintenance activity, we needed to re-enable a custom concurrent program that had been disabled for a long time. Although the concurrent program was successfully enabled, attempting to launch it resulted in an unexpected Oracle Forms startup error.
The application failed to open the custom form and displayed the following error:
FRM-92101: There was a failure in the Forms Server during startup.
This could happen due to invalid configuration.
Please look into the web server log for details.
At first glance, the error suggested a Forms Server or configuration issue. However, the root cause turned out to be something entirely different. In this blog, we’ll walk through the investigation, identify the actual cause, and explain the steps required to resolve the issue.
We attempted multiple steps to resolve the issue:
- Bounced the application services
- Cleared the functional cache
However, the error still persisted — indicating that the issue wasn’t related to cache or runtime environment settings.
Root Cause
After further analysis, the issue was identified as being related to the program parameters. When the custom concurrent program was disabled earlier, its parameter definitions became stale or out of sync with the runtime configuration. When we re-enabled the program, those parameters didn’t refresh correctly, leading to the FRM-92101 error.
Solution
The final fix was simple yet effective:
- Open the Concurrent Program Definitionin Oracle EBS.
- Go to the Parameters
- Select one of the parameters and temporarily modify its value (for example, change the default value).
- Then revert the parameter backto the original value.
- Save the definition and rerun the custom program.
After performing these steps, the program executed successfully, and the FRM-92101 error disappeared.
Conclusion
The root cause of the FRM-92101 error was identified through analysis of the Forms and web server logs. After correcting the underlying configuration/custom object issue and validating the application environment, the custom concurrent program launched successfully without any Forms startup errors.
