SLA Installer Fails on 64-Bit Systems When Using BOBJ 4.2 (32-Bit)

SLA Installer Fails on 64-Bit Systems When Using BOBJ 4.2 (32-Bit)

Symptoms

Issue

When installing the SLA (Semantic Layer Agent) on a 64-bit Windows system that has SAP BusinessObjects 4.2 (32-bit) installed, the SLA service may fail to start. This issue is due to an architecture mismatch: the SLA installer expects a 64-bit BI platform, but the system is running the 32-bit version of BOBJ.

This article explains how to resolve the issue by adjusting the SLA configuration manually.

Note: This issue is resolved in SLA version 2025.2 and later.

Environment

  • Product: 360Suite – SLA - Versions before 2025.2

  • Operating System: Windows 64-bit

  • SAP BOBJ Version: 4.2 (32-bit)


Cause

After installing SLA on a 64-bit Windows machine with BOBJ 4.2 (32-bit), the SLA service fails to start.
The error is typically related to an architecture mismatch, where the SLA is trying to launch in 64-bit mode, which is not compatible with the 32-bit BOBJ installation.


Resolution

Follow the steps below to manually adjust the SLA configuration to run in 32-bit mode.


Step 1: Check SLA Service Startup Parameters (If Applicable)

  1. Open the SLA Service Properties window.

  2. Go to the Startup tab.

  3. If present, remove any command-line argument that forces the SLA to run in 64-bit mode (such as a win64 flag).

    This argument forces the SLA to launch in 64-bit mode and should be removed for 32-bit BOBJ environments.

If no such argument is found, proceed to Step 2.


Step 2: Modify the Launcher.jar File

  1. Navigate to the SLA installation folder:

    C:\Program Files (x86)\360Suite\360_Semantic_Layer_Agent

  2. Make a backup of the existing Launcher.jar file.

  3. Open Launcher.jar using an archive tool like 7-Zip or WinRAR.

  4. Locate the file named architecture.properties inside the archive.

    • If it doesn’t exist, create a new file with that name inside the archive.

  5. Edit architecture.properties and ensure it contains:

    architecture=win32_x86

    If the file originally contained architecture=win64_x64, change it to win32_x86.

  6. Save the modified file and update it in the archive.


Step 3: Restart the SLA Service

After saving the changes:

  1. Restart the 360_Semantic_Layer_Agent service.

  2. Verify that the service starts successfully and that it is compatible with your 32-bit BOBJ environment.

    • Related Articles

    • 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 ...

    • Probe Service - "System cannot find the path specified" error prevents service from starting

      Symptom When launching the 360Probe service Installer.bat, some line shows the message : System cannot find the path specified. Environment Product : 360Live Environment : OS : Windows 360Probe is deployed Reproducing the issue (if applicable) There ...

    • Audit Snapshot Fails in 360Eyes — Unsupported DB URL (jdbc:sqlanywhere)

      Symptoms When running the 360Eyes – Audit job, the job fails during DO_SPECIFIC_JOB_ACTIONS and the log displays: Could not generate snapshot : Current DB URL (jdbc:sqlanywhere:DSN=BIA_Audit_PROD) is not supported. Cause The Audit data source is ...

    • 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 ...

    • Get SLA debug information

      Generalities The Semantic Layer Agent (SLA) is a component of 360Suite that bridges SAP SL SDK with our processes. It is brought by two artifacts: Laucher.jar and SemanticLayerAgent-{version}.jar. These two artifacts are mandatory to ensure you are ...