12.1 RUP3 - adforms-c4wsctl Fails

(Doc ID 1154863.1)

Last updated on OCTOBER 19, 2016

Applies to:

Oracle Applications Technology Stack - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Checked for relevance on 02-JUL-2013


One has upgraded an instance to 12.1.3 applying the following patches:

R12.AD.B.Delta.3 <patch 9239089>
R12.ATG_PF.B.Delta.3 <patch 8919491>
R12.TXK.B.Delta.3 <patch 8919489>

Now when trying to start or stop opmn services via adopmnctl.sh startall/stopall the following error is shown:

Starting FORMS-C4WS oc4j...
EXIT CODE is 150. Please check the log file for more details.

running adforms-c4wsctl.sh start on its own results in a similar message

You are running adforms-c4wsctl.sh version 120.0.12010000.3
Starting OPMN managed FORMS-C4WS OC4J instance ...

Calling txkChkFormsDeployment.pl to check whether latest FORMSAPP.EAR is deployed...

*** Log File = /u02/inst/apps/VIS_apcappsx7/logs/appl/rgf/TXK/txkChkFormsDeployment_Wed_Jul_14_09_52_20_2010/txkChkFormsDeployment_Wed_Jul_14_09_52_20_2010.log

Program : /u02/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChkFormsDeployment.pl started @ Wed Jul 14 09:25:30 2010

*** Log File = /u02/inst/apps/VIS_apcappsx7/logs/appl/rgf/TXK/txkChkFormsDeployment_Wed_Jul_14_09_25_29_2010/txkChkFormsDeployment_Wed_Jul_14_09_25_29_2010.log

File "/u02/apps/tech_st/10.1.3/j2ee/forms/applications/forms/formsweb/WEB-INF/lib/frmsrv.jar" exists. Proceeding to check the size...
*** Latest formsapp.ear has been deployed ***

Program : /u02/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkChkFormsDeployment.pl completed @ Wed Jul 14 09:25:30 2010
Perl script txkChkFormsDeployment.pl got executed successfully
adforms-c4wsctl.sh: exiting with status 150

The log file shows the following:

opmn id=apcappsx7.au.oracle.com:6221
no enabled components for this request
Response: not enabled: VIS_apcappsx7.apcappsx7.au.oracle.com~default_group~forms-c4ws

adforms-c4wsctl.sh: exiting with status 150


It is also possible that you may experience these error messages with the oafm and the oacore processes. This will happen if any of these services are disabled which is commonly achieved by setting the following autoconfig variables
s_oacorestatus = disabled
s_oafmstatus = disabled

Furthermore the problem can also manifest if you have the forms OC4J disabled because you are running forms in socket mode.
s_formsstatus = disabled


There was a code change in 12.1.3 which resulted in disabled OC4J processors throwing the mentioned error message. Furthemore, the FORMS-C4WS component process has been added to 12.1.3 to allow for integration with Oracle E-Business Suite Integrated SOA Gateway. See <Note 556540.1>


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms