SOAP Web Service AFX test connector capabilities fail with 'Could not find service named' in RSA Identity Governance & Lifecycle
Originally Published: 2016-03-08
Last Modified: 2022-06-20
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.0.x
Issue
When testing SOAP Web Service AFX connector capabilities (AFX > Connectors > {connector-name} > Test Connector Capabilities) the following error message displays in the user interface:
Could not find service named
This error is reported in the connector log file, $AFX_HOME/esb/logs/esb.AFX_CONN_{connector-name}_test.log (7.x) or $AFX_HOME/mule/logs/mule.AFX_CONN_{connector-name}_test.log (6.x):
2019-12-21 14:27:04.067 [INFO] com.aveksa.AFX.server.runtime.mule.soap.mule.SoapDispatchComponent:197 - Issue encountered supported verb: CreateAccount, error is Could not find service named {http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull}RemoteProgramExitsService in wsdl http://test.testla.testfrd.xyz.com:XXXX/RemoteProgramExits.soap?WSDL 2019-12-21 14:27:04.069 [INFO] org.mule.api.processor.LoggerMessageProcessor:197 - Error on SOAP component handling, no post processing done
Cause
EXAMPLE:
In the below WSDL note the actual target namespace is:In the log file note the parsed target namespace is:
Resolution
- RSA Identity Governance & Lifecycle 6.9.1 P12
- RSA Identity Governance & Lifecycle 7.0.1
- RSA Identity Governance & Lifecycle 7.0.2
Workaround
- Login to the afx server as the afx user.
- cd $AFX_HOME/esb/apps/{connector-name} (7.x) or $AFX_HOME/mule/apps/{connector-name} (6.x)
- vi connector-flow.xml
- Locate the namespace seen in the error and replace the incorrectly parsed (truncated) namespace with the actual namespace defined in the WSDL definition. In this example,
Replace: namespace=http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits20Version2C3Dneutral20PublicKeyToken%3Dnull
With: namespace="http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits%2C%20Version%3D1.0.4671.27345%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull"
With: namespace="http://schemas.microsoft.com/clr/nsassem/RemoteProgramExits/RemoteProgramExits%2C%20Version%3D1.0.4671.27345%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull"
- Save the file after making changes.
- vi mule-config.xml
- Locate </mule> and add a new blank line after </mule>.
- Save the file. This performs a hot deployment of the connector.
- Check that the connector is in a Running state. In the user interface go to AFX > Connectors.
- If the connector is in a Running state, test the connector capability to verify the workaround.
Related Articles
MultiApp collector is failing at task 3 with ORA-01400 error in RSA Governance & Lifecycle 27Number of Views Multi-App Collector Circuit Breaker trips incorrectly in SecurID Governance & Lifecycle 229Number of Views The Template ({Connector Template Name}) has missing file content error when creating AFX Connectors in RSA Identity Gover… 83Number of Views 'Multi App Collector : 'Admin' privilege does not allow editing of the collector definition as expected in RSA Identity Go… 25Number of Views CSV Data Collectors of Data Source Type Database return incorrect result sets when joining multiple CSV files in RSA Ident… 63Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide Identity Sources for Cloud Access Service Root CA certificate is required for activation error when importing a custom certificate signed by a known CA into Operati…
Don't see what you're looking for?