SLA Unable to Connect to CMS (FWM 01009)
Overview
When using 360Suite Semantic Layer Agent (SLA), the task fails with a RemoteException indicating a communication error with the CMS. This issue typically occurs after installing SLA on a Windows host and configuring RMI settings, even when network connectivity appears functional.
Error message observed:
- Error at line 1 of sheet 'Relational':
- Unable to create the Connection:
- java.rmi.RemoteException: Communication error occurred when trying to connect to server SERVERNAME:6400 (FWM 01009)
Symptoms
- 360Suite Tasks using the SLA fail with FWM 01009.
- Telnet from SLA host to CMS on port 6400 succeeds.
- IDT on SLA host can open a session on the same CMS.
- There are no firewall issues or restrictions.
- SLA logs show RemoteException during CORBA communication.
Cause
By default, the SLA launcher expects SSL mode when the BI environment is configured for CORBA SSL. But in this case:
- The CMS was configured with CORBA SSL, but the SLA was launched with -Dbusinessobjects.orb.oci.protocol=mixed.
- SLA code does not handle mixed mode; it only enforces SSL when explicitly set to ssl.
As a result, the SLA attempted a non-SSL handshake on a CMS requiring SSL, causing the FWM 01009 error.
Resolution
Force the SLA to use SSL for CORBA communication by setting the correct JVM parameter.
- Open the SLA configuration (default path: <360Suite_installation_folder>/360_Semantic_Layer_Agent/360Suite_Semantic_Layer_Agent.exe).
- In the Java tab, add the following parameters:
-Dbusinessobjects.orb.oci.protocol=ssl
-DcertDir=<path/to/corba/certificate/folder>
-DtrustedCert=<comma-separated,corba,certificate,names>
(Adjust paths and filenames to match your environment.) - Restart the SLA service.
Related Articles
Configure 360Suite to communicate with SSL-enabled environments
Context Many 360Suite modules need to communication with the BOBJ RESTful API to process specific actions, often "Webi and UNX"-related actions. The features using this RESTful API are the following ones: 360Bind (opening and working with Webi ...Converting Oracle based MSU UNX to SSU fails with "driver could not be loaded error"
Symptom When you launch a MSU to SSU conversion on a universe based on an Oracle ODBC connection. On WebPatform 2023.1.1 : The task ends in success When you retrieve the - Converted universe, you have an empty Data foundation On WebPlatform 2023.2 ...Unable to create system preferences directory
Condition The Apache Tomcat server log returns the following error on start-up: Could not create system preferences directory. System preferences are unusable Solution Cause This error occurs if the server is started using a user or service account ...Unable to start 360Suite when tomcat uses slf4j
Symptom tomcat root page is available /360suite url returns 404 error in tomcat/logs/localhost-{date}.log an error appears on 360Suite startup 03-May-2021 07:51:22.858 SEVERE [localhost-startStop-1] ...Unable to change the password for the Administration Console (Windows)
Symptoms Install or update 360Suite with Tomcat running as a Windows service. Attempt to launch or interact with the 360Suite Administration Console. Notice that the console does not load properly or crashes silently. Cause The Windows user account ...