SOA Provider Access resulted in exception
If you are on R12.1.1 and having issue when trying to Generate a WSDL Service, from the Integration Repository, for any of the listed Product family and you come across the following error
SOA Provider Access resulted in exception ‘oracle.apps.fnd.soa.util.SOAException: ServiceGenerationError
Here’s what we found.
- Remove the xmlparserv2.jar under $OA_JAVA directory
- Restart opmn and related j2ee processes:$ADMIN_SCRIPTS_HOME/adopmnctl.sh stopall$ADMIN_SCRIPTS_HOME/adopmnctl.sh startall
- If after removal and retest the following new error appears:SOA Provider Access resulted in exception’oracle.apps.fnd.soa.util.SOAException:ServiceGenerationError: ServiceGenerationError: Exception returned from JCA Service Generator.J2T-106, ERROR: Sorry, unable to continue due to java.io.IOException:Cannot run program “javac”: javac: not found’ when attempting to perform ‘GENERATE’. Please contact your System Administrator—-java.ioIOEception: error=2, no such file or directoryThen this is a known issue. Reference: Note 862034.1 – Generate WSDLThrows ServiceGenerationError javac:not foundSolution: Apply one-off Patch <8407693> R12.TXK.B ISG: Service GenerationFailure – Java Compiler Could Not be Found and retest the issue
If the ASADMIN user has not been setup properly, follow the steps below (From SOA Note 726414.1) that refer to the system-jazn-data.xml file. Your system-jazn-data.xml file is missing the password for the asadmin.
Use the following steps to ensure that the “ASADMIN” user has been activated and its password has been reset:
Log on to Oracle E-Business Suite with the username that has the User Management responsibility access privilege.Select the User Management responsibility from the Navigator.Click the Users link from the navigation menu to open the User Maintenance window.Locate ‘ASADMIN’ user by entering information in the search area to retrieve the ‘ASADMIN’ user.Click the Update icon next to the ASADMIN user to open the Update User window.Remove the Active To date field and click Apply.Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.Enter new password twice and click Submit.After activating the ASADMIN user, verify if the ASADMIN user has the ‘Apps Schema Connect Role’(UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.If the ‘Apps Schema Connect Role’ role is not present in the wf_user_roles for the ASADMIN user, then run the ‘Workflow Directory Services User/Role Validation’ concurrent program to grant the role.After “ASADMIN” user is enabled from the applications, update the file $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml as shown below:ASADMIN <display-name>Default Apps SOA User</display-name> Used by SOAProvider for DB connection!Note: The password should be preceded by a ‘!’ (Exclamation) so that when OAFM is started, it gets encrypted. For example, if the password is “ASADMIN”, then you have to change it to “!ASADMIN”. In addition, the password of ASADMIN should be synchronized between system-jazn-data.xml file and the database through the application user interfaces.Caution: Do not use the same password given in this example for “ASADMIN” user. Use different password instead to avoid some potential security risk in your system.Bounce the middle-tier and retry the generation process.
Even after all the above steps have been taken care of and you still have this issue persistent, as Per bug 8919471 the issue is fixed in 12.1.2.
Prior to this check that you do not have the fixed files:
Look in the following directories to see if your versions are >=:$JAVA_TOP/oracle/apps/fnd/soa/provider SOAProvider.java 120.13.12010000.11/provider SOARemove.java 120.0.12010000.2/provider/util DBConnection.java 120.5.12010000.6/provider/util IRepAccess.java 120.6.12010000.8/provider/wsdl WSDLGenerator.java 120.5.12010000.7/util SOAException.java 120.4.12010000.11